-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Filtering on a boolean field with just the field name results in NullPointerException #8444
Comments
@Jackie-Jiang Should we go with re-writing the query |
@KKcorps Good solution! We can re-write the filter expression if the underlying predicate does not have |
@Jackie-Jiang / @KKcorps / @jadami10 are you planning to work on this ? If not, @vvivekiyer can help pick it up as he is familiarizing himself through the code |
@siddharthteotia I am working on BrokerResponse so @vvivekiyer can pick it up |
@vvivekiyer is working on the fix |
Fixes the bugs in apache#8444 and apache#8487. Added unit tests.
* Support filtering on bool/scalar fields without evaluator Fixes the bugs in #8444 and #8487. Added unit tests. * Address review comments and refactor code * Address review comments 2 * RequestContextUtil changes * Review comments in RequestContextUtils * Refactor RequestContextUtils * Refactor ComparisonPredicateRewriter Co-authored-by: Vivek Iyer Vaidyanathan <vvaidyan@vvaidyan-mn1.linkedin.biz>
Fixed with #8518 |
thanks for working on this! I didn't see a test example, but does |
Hi Johan, yes it should. I just tested it out locally for a use-case. I didn't add a test-case example because AND, OR, NOT are processed similarly. |
Running a query with just
select <fields> from <table> where <boolean_field>
results in a null point exception. This should be a supported query.Stack trace from pinot
user facing error
The text was updated successfully, but these errors were encountered: