[GitHub] [pinot] walterddr opened a new issue, #9976: [multistage][backward-incompat][feature] index not being used for some filter

[GitBox <gi...@apache.org>]

walterddr opened a new issue, #9976:
URL: https://github.com/apache/pinot/issues/9976

   query like 
   ```
   SELECT * FROM tbl WHERE strCol = 123 
   ```
   - this can apply inverted index on `strCol` just fine in V1 b/c V1 engine is not type-aware; thus the filter clause gets converted into `=(strCol, '123')`
   - this will be translated to `CAST(strCol AS INT) = 123` in V2 b/c it is type-aware and b/c of this function application, it doesn't apply index properly.
   
   There's 2 solutions
   1. do not allow these type of implicit type casting at all (e.g. query must explicitly ask for CAST or failed type mismatch) this will avoid the potential performance degradation but will make some V1 query backward-incompatible
   2. do the smart rewrite rule to convert this to a left-cast not a right-cast; this will potentially have many corner cases to handle.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org