-
Notifications
You must be signed in to change notification settings - Fork 162
fix: Stable StarRocks Driver and Add test code #8619
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
fix: Stable StarRocks Driver and Add test code #8619
Conversation
…ontainer & fix VARCHAR binary return Signed-off-by: Edward Kim <kjjs1996@gmail.com>
Signed-off-by: Edward Kim <kjjs1996@gmail.com>
|
These test failures are due to missing environment variables (S3, GCS, Druid, MotherDuck credentials) |
- Change BINARY/VARBINARY/BLOB from CODE_BYTES to CODE_STRING
for consistency with MySQL driver behavior
- Expand type mapping unit tests to cover all StarRocks types:
- Boolean, Integer, Float, String, Binary, DateTime
- Semi-structured types (JSON, ARRAY, MAP, STRUCT)
- Aggregate-only types (HLL, BITMAP, PERCENTILE) as unsupported
- Update integration test expectations for VARBINARY type
Signed-off-by: Edward Kim <kjjs1996@gmail.com>
|
Hi, @k-anshul |
|
Hey @EdwardArchive Thank you for your contribution. |
|
Hi @k-anshul, |
- Add metricsview aggregation, toplist, and comparison tests for StarRocks - Implement Stream Load API for test data loading with FE→BE redirect handling - Add NULLS LAST for consistent NULL ordering in StarRocks - Fix TIMESTAMP handling to use sql.NullTime with parseTime=true - Add CONVERT_TZ for timezone support in DateTruncExpr - Fix schema resolution using InformationSchema lookup - Cast percent_of_total result to DOUBLE for consistent numeric handling - Update StarRocks documentation to match driver implementation Signed-off-by: EdwardKim <kjjs1996@gmail.com>
|
Hey @k-anshul, |
Related PR : #8454
Problem:
driver behavior when scanning into
anytypeSolution:
Testing:
Type mapping (MySQL protocol):
Checklist: