4paradigm / 4paradigm/OpenMLDB
Partial parameter binding in request mode
- Dominant language
- C++
- Stars
- 1.7k
- Forks
- 331
- Avg merge
- 12d 12h
- Merged PRs (30d)
- 1
Description
**Is your feature request related to a problem? Please describe.**
According to https://docs.openmldb.ai/quickstart/python_sdk#3.6-zhi-hang-sql-qing-qiu-shi-cha-xun
to perform query in request mode, we have to assign values to all columns of the table. This is very inconvenient when we only care about some of the columns, because we need to know all column names of the table in advance.
**Describe the solution you'd like**
In request mode, we only need to assign values to columns we care about.
**Describe alternatives you've considered**
Give values to all columns of the table. Assign null or 0 for irrelevant columns
**Additional context**
Add any other context or screenshots about the feature request here.
Contributor guide
Research direction
The issue relates to the request mode SQL query execution in the Python SDK. Start by examining the Python SDK code for request mode handling, likely in the openmldb Python package. Look at how parameter binding currently works and where column validation occurs. Understand the table schema handling and how partial binding could be allowed. Check existing tests for request mode to see the expected behavior and add tests for the new feature.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sql
- Domain
- backend-api-design, database, machine-learning
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100