Jackie-Jiang commented on PR #8384: URL: https://github.com/apache/pinot/pull/8384#issuecomment-1088009720
> Here is the plan -- LIKE is going to start using text indices if available, thus providing support for LIKE on native indices + logical operators come free due to the ability to combine multiple LIKE predicates. This might not align with the SQL `LIKE` semantic which should match the whole document instead of the token matching. This is more like the `CONTAINS` described [here](https://docs.microsoft.com/en-us/sql/relational-databases/search/query-with-full-text-search?view=sql-server-ver15). I didn't find a standard SQL function for the token matching, not sure if there is one. > In the current PR, I will allow TEXT_MATCH to work on top of native text indices, but _any_ query passed in to the native text index through TEXT_MATCH will be treated as a regex query. Alternative is to disable TEXT_MATCH on native indices completely. I'd suggest coming up with a new function to support boolean operations on token regex matching. Something like `TEXT_LIKE(textCol, 'ab.*' AND '.cd')` Looking for inputs here @siddharthteotia @richardstartin @kishoreg -- 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-unsubscr...@pinot.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
