Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
saigal
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
31.
▲
by
saigal
2y ago
We'll make the licensing more visible. Stay tuned in a few minutes.
32.
▲
by
saigal
2y ago
great question, and the one that we get the most :-) this is precisely why we created Dataherald. Off the shelf LLMs can handle a single table and simple questions. Dataherald's quest is to ultimately provide enterprise-grade text to S
33.
▲
by
saigal
2y ago
the target audience is developers who wish to embed text to SQL functionality into their own products. the target audience is less the 'internal use case' (i.e. a data analyst) and more about letting external users do things they
34.
▲
by
saigal
3y ago
this is on roadmap. which LLM are you focused on using? so far GPT 4 has performed best, head and shoulders above other LLMs, so as a result we are using this one now.
35.
▲
by
saigal
3y ago
can you tell me more?
36.
▲
by
saigal
3y ago
Thanks so much for the kind words. Getting NL-to-SQL to work at the enterprise grade takes work and a specialized engine / agent to do so (we use fine-tuning together with RAG). I don't believe this will be the objective of OpenAI
37.
▲
by
saigal
3y ago
Anuj[at]dataherald.com
38.
▲
by
saigal
3y ago
This is a good point and one that we’ve grappled with a lot. My point of view after working on 30+ company deployments is that it depends on the use case. Here’s an example: you have a very analytical BizOps lead at a mid market company. He
39.
▲
by
saigal
3y ago
Yes, absolutely. Every AI-generated SQL comes with a confidence score, so that you stay in control. We've had people who set a confidence threshold for returning answers to the users. If confidence threshold isn't met, then there&
40.
▲
by
saigal
3y ago
The API introduction announcement is here: https://www.dataherald.com/news/introducing-dhai
41.
▲
by
saigal
3y ago
i'll try to change it out the link
42.
▲
Show HN: Natural Language to SQL "Text-to-SQL" API
(dataherald.com)
62 points
by
saigal
3y ago
|
40 comments
43.
▲
by
saigal
3y ago
can you fine-tune the LLM?
44.
▲
by
saigal
3y ago
True. The goal would be write the complex SQL query once, then file it away as golden SQL so that in the future a similarly complex query could be done in natural language.
45.
▲
Fine-tuning GPT-3.5-turbo for natural language to SQL
(medium.com)
208 points
by
saigal
3y ago
|
75 comments
46.
▲
by
saigal
3y ago
A tutorial on how to fine-tune a GPT3.5 model for Natural Language to SQL tasks and a comparison of its performance vs Retrieval Augmented Generation. Based on the results, fine-tuning can match and outperform RAG (the approach matches the
47.
▲
by
saigal
3y ago
GPT4 is best right now for all the reasons you likely already know. We are working on self-hosted but for right now it is GPT4. We can let you know when we work on self-hosted, which will no doubt come in the future. feel free to email me a
48.
▲
by
saigal
3y ago
happy to connect and describe more to see whether we could collaborate. please feel free to email be at anuj at dataherald dot com or sign up here and we will get in touch https://www.dataherald.com/contact
49.
▲
by
saigal
3y ago
Do you mean that SQL will significantly fade away?
50.
▲
by
saigal
3y ago
Very cool! is this mostly for unstructured data search? Any interest in adding tabular / structured data NL search?
51.
▲
by
saigal
3y ago
Curious as to why you pivoted away from the previous NL-to-SQL startup?
52.
▲
by
saigal
3y ago
I want to double-down on what AAzo11 replied. There is a human in the loop via an admin dashboard that allows quick approval / editing in the event of incorrect queries. This significantly decreases time for a member of the data team t
53.
▲
by
saigal
3y ago
I agree that allowing a user, particularly a non-technical one, to see the auto-generated SQL (i.e. the SQL created from natural language) might actually encourage understanding of the data. It can create an easier on-ramp for non-tech folk
54.
▲
by
saigal
3y ago
At the risk of generalizing too much, there's always a chance that layering on a new technology can limit a user's understanding by creating an additional degree of separation. More specifically though, if a PM has been using a BI
55.
▲
by
saigal
3y ago
Thanks. Noted. We will fix.
56.
▲
by
saigal
3y ago
awesome, we'll check it out!
57.
▲
by
saigal
3y ago
yes, exactly. recent advancements in LLMs have changed the game entirely
58.
▲
by
saigal
3y ago
Very cool. I'm checking out veezoo.com now!
59.
▲
by
saigal
3y ago
the future indeed!
60.
▲
Show HN: Data content creation tool using OpenAI+LangChain(lessons learned)
(app.dataherald.ai)
3 points
by
saigal
3y ago
|
1 comments
More ›