evadb-slack-bot's Introduction

EvaDB Slack Bot

This bot 🤖 allows users to ask questions about PDFs 📄 using EvaDB.

EvaDB: https://github.com/georgia-tech-db/evadb.

EvaDB enables software developers to build AI apps in a few lines of code. Its powerful SQL API simplifies AI app development for both structured and unstructured data. EvaDB's benefits include:

🔮 Easy to connect EvaDB with your SQL database system and build AI-powered apps with SQL queries
🤝 Query your data with a pre-trained AI model from Hugging Face, OpenAI, YOLO, PyTorch, and other AI frameworks
⚡️ Faster queries thanks to AI-centric query optimization
💰 Save money spent on running models by efficient CPU/GPU use
🔧 Fine-tune your AI models to achieve better results

👋 Hey! If you're excited about our vision of bringing AI inside database systems, show some ❤️ by:

🐙 giving a ⭐ on our EvaDB repo on Github
📟 joining our Slack Community
🐦 following us on Twitter
📝 following us on Medium

Example Conversation

evadb-bot.pdf

Installation

Local Host

Note: requries ngrok

1) Export your Slack Bot Token and Signing Key to the environment

export SLACK_BOT_TOKEN=<your-slack-token>
export SLACK_SIGNING_SECRET=<you-slack-siging-secret>

2) Load the PDF datasets into EvaDB

Refer EvaDB Docs

3) Start Flask server

FLASK_APP=slack_client.py FLASK_ENV=development flask run -p <port-number>

4) (Optional) Expose your Public IP

ngrok http <port-number>

Privacy Notice

We're here to make sure you get the best answers possible. Rest easy – your questions are collected anonymously, all in the spirit of providing you with top-notch responses. Your privacy matters to us!

evadb-slack-bot's People

Contributors

Stargazers

Watchers

evadb-slack-bot's Issues

Should EvaDB support build_rag_query?

Open to discussion. Do we think it is better to support build_rag_query in EvaDB's SQL query? Or leave it outside EvaDB. I personally think we should support within EvaDB to have a more seemless user experience. We can create an issue in the EvaDB repo as a feature request for supporting build_rag_query in SQL.

utils/sentence_feature_extractor.py and `sentence_feature_extractor.py` in evadb repo

Evadb comes with sentence_feature_extractor.py. Is there a particular reason we need to copy the file instead of directly using the one comes with the evadb? If we can not CREATE FUNCTION using functions in evadb repo, that is an issue we need to fix. Thanks.

Recommend Projects

georgia-tech-db / evadb-slack-bot Goto Github PK