feat: New text-to-SQL pipe using LlamaIndex

[0xThresh]

No description provided.

[tjbck]

LGTM, Thanks!

[zchef2k]

What version of pipelines are you running/testing this against? It gets moved to 'failed' for me, ostensibly because of the following:

WARNING:root:No Pipeline class found in text_to_sql_pipeline

I've tried against main/latest and a cherry-picked previous version, git-76b8131.

[0xThresh]

@zchef2k how are you building your Pipelines server? Are you using the Docker image, or just installing from scratch? Mine is built from the Docker image.

You may need to make sure that llama_index, sqlalchemy, and psycopg2-binary packages are installed before this will work. If you already have those, I can check to see what version of the Pipelines server I'm running.

[zchef2k]

@0xThresh With regards to the pipelines server, two ways...

1. deploying to k3s with helm as part of open-webui
2. running locally with docker, using either 'main' and 'git-76b8131' (for comparison)

In either case, whether this pipeline is present in a volume mount to a locally running Docker container or uploaded via open-webui, I get the error. To double check dependencies in both scenarios, I submit the following:

• In the pod on k3s deployed via helm:

• Locally using the older of the two images:

[0xThresh]

Thanks for confirming @zchef2k.

As I'm looking at it again, I recall not defining the Valves in the best way I could have on this file. They try to load some of the database environment variables on startup, and the expectation is that those variables are set on the Pipelines server on startup. I would check to see if your Pipelines server has the environment variables referenced in these lines defined on startup. I think it would definitely be better to not load those from environment variables, or at least set a default value if those aren't present so that they can hopefully still be added in the Open WebUI Pipelines management interface.

Let me know if that gets you closer to solving it.

[zchef2k]

@0xThresh Thank you, declaring environment variables for the container did the trick. That probably should have been obvious to me from the start.

Thanks for providing this example. Keep up the great work.