HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
georgia-tech-db
evadb
Python2023–2023
georgia-tech-db / evadb · Archived

evadb

Database system for AI-powered apps

3Distinct people
23Mentions
0Explicit recommenders
2.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Database system for AI-powered apps

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week23 dated mentions

Observed mentions: 2023-04-30 16:52:01 UTC to 2023-10-28 16:56:46 UTC. Weeks start Monday, UTC.

0123452023-04-24 00:00:00 UTC to 2023-05-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 commentsApr 242023-05-01 00:00:00 UTC to 2023-05-08 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2023-05-08 00:00:00 UTC to 2023-05-15 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2023-05-15 00:00:00 UTC to 2023-05-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-22 00:00:00 UTC to 2023-05-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-29 00:00:00 UTC to 2023-06-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-05 00:00:00 UTC to 2023-06-12 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023-06-12 00:00:00 UTC to 2023-06-19 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-06-19 00:00:00 UTC to 2023-06-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-26 00:00:00 UTC to 2023-07-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-07-03 00:00:00 UTC to 2023-07-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-07-10 00:00:00 UTC to 2023-07-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-07-17 00:00:00 UTC to 2023-07-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-07-24 00:00:00 UTC to 2023-07-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 242023-07-31 00:00:00 UTC to 2023-08-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-08-07 00:00:00 UTC to 2023-08-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-08-14 00:00:00 UTC to 2023-08-21 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-08-21 00:00:00 UTC to 2023-08-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-08-28 00:00:00 UTC to 2023-09-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-04 00:00:00 UTC to 2023-09-11 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-09-11 00:00:00 UTC to 2023-09-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-18 00:00:00 UTC to 2023-09-25 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-09-25 00:00:00 UTC to 2023-10-02 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023-10-02 00:00:00 UTC to 2023-10-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-09 00:00:00 UTC to 2023-10-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-16 00:00:00 UTC to 2023-10-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-23 00:00:00 UTC to 2023-10-30 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 commentsOct 23

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Apr 242023-04-24 00:00:00 UTC2023-05-01 00:00:00 UTC312
May 12023-05-01 00:00:00 UTC2023-05-08 00:00:00 UTC404
May 82023-05-08 00:00:00 UTC2023-05-15 00:00:00 UTC505
May 152023-05-15 00:00:00 UTC2023-05-22 00:00:00 UTC000
May 222023-05-22 00:00:00 UTC2023-05-29 00:00:00 UTC000
May 292023-05-29 00:00:00 UTC2023-06-05 00:00:00 UTC000
Jun 52023-06-05 00:00:00 UTC2023-06-12 00:00:00 UTC110
Jun 122023-06-12 00:00:00 UTC2023-06-19 00:00:00 UTC101
Jun 192023-06-19 00:00:00 UTC2023-06-26 00:00:00 UTC000
Jun 262023-06-26 00:00:00 UTC2023-07-03 00:00:00 UTC000
Jul 32023-07-03 00:00:00 UTC2023-07-10 00:00:00 UTC000
Jul 102023-07-10 00:00:00 UTC2023-07-17 00:00:00 UTC000
Jul 172023-07-17 00:00:00 UTC2023-07-24 00:00:00 UTC000
Jul 242023-07-24 00:00:00 UTC2023-07-31 00:00:00 UTC000
Jul 312023-07-31 00:00:00 UTC2023-08-07 00:00:00 UTC000
Aug 72023-08-07 00:00:00 UTC2023-08-14 00:00:00 UTC000
Aug 142023-08-14 00:00:00 UTC2023-08-21 00:00:00 UTC101
Aug 212023-08-21 00:00:00 UTC2023-08-28 00:00:00 UTC000
Aug 282023-08-28 00:00:00 UTC2023-09-04 00:00:00 UTC000
Sep 42023-09-04 00:00:00 UTC2023-09-11 00:00:00 UTC202
Sep 112023-09-11 00:00:00 UTC2023-09-18 00:00:00 UTC000
Sep 182023-09-18 00:00:00 UTC2023-09-25 00:00:00 UTC202
Sep 252023-09-25 00:00:00 UTC2023-10-02 00:00:00 UTC110
Oct 22023-10-02 00:00:00 UTC2023-10-09 00:00:00 UTC000
Oct 92023-10-09 00:00:00 UTC2023-10-16 00:00:00 UTC000
Oct 162023-10-16 00:00:00 UTC2023-10-23 00:00:00 UTC000
Oct 232023-10-23 00:00:00 UTC2023-10-30 00:00:00 UTC303

What Hacker News says

23 sources
jarulraj·Sep 30, 2023Submission

Show HN: Stargazers Reloaded – LLM-Powered Analyses of Your GitHub Community

Hey friends! We have built an app for getting insights about your favorite GitHub community using large language models. The app uses LLMs to analyze the GitHub profiles of users who have starred the repository, capturing key details like the topics they are interested in. It takes screenshots of the stargazer's GitHub webpage, extracts text using an OCR model, and extracts insights embedded in the extracted text using LLMs. This app is inspired by the “original” Stargazers app written by Spencer Kimball (CEO of CockroachDB). While the original app exclusively used the GitHub API, this LLM-powered app built using EvaDB additionally extracts insights from unstructured data obtained from the stargazers’ webpages. Our analysis of the fast-growing GPT4All community showed that the majority of the stargazers are proficient in Python and JavaSc
Read the rest
ript, and 43% of them are interested in Web Development. Web developers love open-source LLMs! We found that directly using GPT-4 to generate the “golden” table is super expensive — costing $60 to process the information of 1000 stargazers. To maintain accuracy while also reducing cost, we set up an LLM model cascade in a SQL query, running GPT-3.5 before GPT-4, that lowers the cost to $5.5 for analyzing 1000 GitHub stargazers. We’ve been working on this app for a month now and are excited to open source it today :) Some useful links: * Blog Post - https://medium.com/evadb-blog/stargazers-reloaded-llm-powere... * GitHub Repository - https://github.com/pchunduri6/stargazers-reloaded/ * EvaDB - https://github.com/georgia-tech-db/evadb Please let us know what you think!
20 points · Open discussion
The discord link seems to be not working. Just a heads up. The YOLO example on your Github page is super interesting. We are finding it easier to get LLMs to write functions with a more constrained function interface in EvaDB. Here is an example of an YOLO function in EvaDB: https://github.com/georgia-tech-db/evadb/blob/staging/evadb/.... Once the function is loaded, it can be used in queries in this way: SELECT id, Yolo(data) FROM ObjectDetectionVideos WHERE id < 20 LIMIT 5; SELECT id FROM ObjectDetectionVideos WHERE ['pedestrian', 'car'] <@ Yolo(data).label; Would love to hear your thoughts on ChatCraft and a more constrained function interface.
In What will LLM-powered software look like in the medium-term future?
Nice writeup! Here is another example of using LLMs is to augmenting existing software that we are exploring -- specifically SQL database systems. We are using LLMs inside a SQL query to power a "soft join" between SQL tables for when a correspondence is only implied (e.g. different address formats, etc.). --- Create a reference table that maps neighborhoods to zipcodes using ChatGPT CREATE TABLE reference_table AS SELECT parkname, parktype, ChatGPT( "Return the San Francisco neighborhood name when provided with a zipcode. The possible neighborhoods are: {neighbourhoods_str}. The response should an item from the provided list. Do not add any more words.", zipcode) FROM postgres_db.recreational_park_dataset; --- Map Airbnb listings to park SELECT airbnb_listing.neighbourhood FROM
Read the rest
postgres_db.airbnb_listing JOIN reference_table ON airbnb_listing.neighbourhood = reference_table.response; More details on LLM-powered joins and EvaDB: https://medium.com/evadb-blog/augmenting-postgresql-with-ai-..., https://github.com/georgia-tech-db/evadb
In What will LLM-powered software look like in the medium-term future?
Thanks for sharing that observation on customer chatbots. 1. Will that query look like this: SELECT LLM("{user_question}", order_info) FROM postgres_data.order_table WHERE user_id = “101”; 2. How will a feature store, like Hopsworks, help in this app? Shameless self-plug: We are building EvaDB [1], a query engine for shipping fast AI-powered apps with SQL. Would love to exchange notes on such apps if you're up for it! [1] https://github.com/georgia-tech-db/evadb
In LLMs, RAG, and the missing storage layer for AI
Congrats on the launch, @ukuina! Neat idea. Would love to learn more about how you are querying the summaries/comments database and how you are planning to extend the queries in this app. Shameless self-plug: We are building EvaDB [1], a query engine for shipping fast AI-powered apps with SQL. Here is an illustrative query for analyzing food reviews stored in Postgres and generating responses for negative reviews: SELECT ChatGPT("Respond to the review with a solution to address the reviewer's concern", review) FROM postgres_data.review_table WHERE ChatGPT("Is the review positive or negative? Only reply 'positive' or 'negative'.", review) = "negative" AND location = “waffle house”; It would be interesting to learn about the queries needed for supporting HackYourNews application. Would love to exchange notes on this if you'
Read the rest
In Show HN: HackYourNews – AI summaries of the top HN stories
Highly recommend Lark for Python projects -- it's easy to use :) Their IDE was super useful for debugging the grammar: https://www.lark-parser.org/ide/ We use Lark for a SQL-like language tailored for using AI models in EvaDB: https://github.com/georgia-tech-db/evadb/blob/master/evadb/p... https://github.com/georgia-tech-db/evadb/ If you like Lark, please consider sponsoring them: https://github.com/sponsors/lark-parser
In Show HN: I wrote a RDBMS (SQLite clone) from scratch in pure Python
We also love SQL, @potatoman22 :) BTW, EVA itself is designed for analyzing sports games -- like touchdowns in a football game. This notebook shows how an action recognition model can be run on an American Sign Language video to identify the correct word [1]. Similarly, a model for identifying touchdowns and players can be used to run interesting queries over a football game. SELECT FIRST(id), ASLActionRecognition(SEGMENT(data)) FROM ASL_ACTIONS SAMPLE 5 GROUP BY '16f'; [1] https://github.com/georgia-tech-db/eva/blob/master/tutorials...
In EVA: AI-Relational Database System
Great question! We have a built-in integration test for 1 million images [1] and have benchmarked EVA on large unstructured datasets for our ACM SIGMOD paper [2]. Coming up with an open benchmark for AI-Relational database systems is essential [3]. Please share your thoughts on any ideas for benchmarking :) [1] https://github.com/georgia-tech-db/eva/blob/e123820c79b902d5... [2] https://dl.acm.org/doi/abs/10.1145/3514221.3526142 [3] https://dl.acm.org/doi/10.1145/3299869.3324955
In EVA: AI-Relational Database System

Showing the 15 most recent of 23 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.