-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Improve reported dataTypes on V1 when no rows returned #14836
Improve reported dataTypes on V1 when no rows returned #14836
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #14836 +/- ##
============================================
+ Coverage 61.75% 63.73% +1.98%
- Complexity 207 1610 +1403
============================================
Files 2436 2708 +272
Lines 133233 151277 +18044
Branches 20636 23357 +2721
============================================
+ Hits 82274 96412 +14138
- Misses 44911 47633 +2722
- Partials 6048 7232 +1184
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
...ion-tests/src/test/java/org/apache/pinot/integration/tests/EmptyResponseIntegrationTest.java
Show resolved
Hide resolved
cc @Jackie-Jiang you were involved in this discussion, so you may be interested in looking. |
V1 just uses STRING as default data type for all columns when no data has been returned by servers.
This is an attempt to improve that by different strategies, being the preferred one use the schema validation implemented on V2 and reuse the data types determined by it. As a failback and only suitable for non-transformed fields, the base table schema is used. Otherwise, the default STRING type is still returned.