Find answers from the community

Updated 2 months ago

I recently converted NLSQLTableQueryEngine to workflows but it's not showing up on Arize Pheonix properly.

At a glance

The community member has created a new class called NLSQLTableRowQueryEngine that inherits from NLSQLTableQueryEngine, and a NLSQLRowRetriever that inherits from NLSQLRetriever, to implement a technique for row retrieval mentioned in a notebook. They want to know the process for contributing these changes to the codebase. The comments indicate that the process involves forking the repository, making the changes in the fork, and proposing a pull request.

Useful resources

OOsama Adel

Hi, I recently asked a question regarding the NLSQLTableQueryEngine (https://docs.llamaindex.ai/en/stable/api_reference/query_engine/NL_SQL_table/) and how can I implement the row retrieval part in this notebook (https://docs.llamaindex.ai/en/stable/examples/pipeline/query_pipeline_sql/#2-advanced-capability-2-text-to-sql-with-query-time-row-retrieval-along-with-table-retrieval) but after converting it to workflows instead, and why it is not showing up on Arize Pheonix properly. Anyway, I have made a new class called NLSQLTableRowQueryEngine that inherits from NLSQLTableQueryEngine and a NLSQLRowRetriever that inherits from NLSQLRetriever with small changes to implement the up-mentioned technique in the notebook. I wanted to know what the process is if I wanted to contribute these changes to code base?

2 comments

LLogan M

contributing is just a matter of forking the repo, making the changes in your fork, and proposing a PR 👍

OOsama Adel

Perfect 🙏

Add a reply