You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Sanjeet Malhotra (Jira)" <ji...@apache.org> on 2026/01/23 05:47:00 UTC
[jira] [Assigned] (PHOENIX-7754) Improve test coverage for using =ANY(?) instead of IN list
[ https://issues.apache.org/jira/browse/PHOENIX-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sanjeet Malhotra reassigned PHOENIX-7754:
-----------------------------------------
Assignee: Sanjeet Malhotra
> Improve test coverage for using =ANY(?) instead of IN list
> ----------------------------------------------------------
>
> Key: PHOENIX-7754
> URL: https://issues.apache.org/jira/browse/PHOENIX-7754
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Sanjeet Malhotra
> Assignee: Sanjeet Malhotra
> Priority: Major
>
> PHOENIX-7659 added optimization to generate point lookups when =ANY(?) is used instead of IN List. This was to optimize on query parsing time. In our internal perf testing we have seen great improvements in parsing time i.e. at least 50% for queries doing 1000/8000 lookups in a single query.
> Before wider adoption we can improve the test coverage to cover following cases:
> * Use in Upsert/Deletes in their query phase.
> * When array has duplicate elements or out of order elements i.e. elements not in sorted order. Skip Scan filter expects non overlapping sorted key ranges.
> * While we have an IT for skip scan but we can add one more for range scan.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)