You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apple M4 Max 128GB
macOS 15.2
Launch service from source
Actual behavior
QA knowledge, the csv file is uploaded for parsing. The QA content of text2sql is question and sql. In sql, there is often text similar to "select a, b, c", and the usual csv is separated by commas. The current ragflow will cause the parsing result to not meet the expectations because of "select a, b, c", because the parsing code completely uses ',' as the separator, and does not recognize the closed character "" on the periphery of sql.
Expected behavior
No response
Steps to reproduce
1. Upload the QA.csv file of text2sql to a QA knowledge
2. Turn on the parsing task
3. Check the results
Fix some bugs in text2sql.(#4279)(#4281)
### What problem does this PR solve?
- The incorrect results in parsing CSV files of the QA knowledge base in
the text2sql scenario. Process CSV files using the csv library. Decouple
CSV parsing from TXT parsing
- Most llm return results in markdown format ```sql query ```, Fix
execution error caused by LLM output SQLmarkdown format.### Type of
change
- [x] Bug Fix (non-breaking change which fixes an issue)
Is there an existing issue for the same bug?
RAGFlow workspace code commit ID
8cdf101
RAGFlow image version
v0.15.1-20-g7773afa5 full
Other environment information
Actual behavior
QA knowledge, the csv file is uploaded for parsing. The QA content of text2sql is question and sql. In sql, there is often text similar to "select a, b, c", and the usual csv is separated by commas. The current ragflow will cause the parsing result to not meet the expectations because of "select a, b, c", because the parsing code completely uses ',' as the separator, and does not recognize the closed character "" on the periphery of sql.
Expected behavior
No response
Steps to reproduce
Additional information
QA.csv
The text was updated successfully, but these errors were encountered: