Jacob Isaac created PHOENIX-6751:
------------------------------------
Summary: Force using range scan vs skip scan when using the IN
operator and large number of RVC elements
Key: PHOENIX-6751
URL: https://issues.apache.org/jira/browse/PHOENIX-6751
Project: Phoenix
Issue Type: Bug
Affects Versions: 4.16.0, 5.1.1, 4.15.0, 5.2.0
Reporter: Jacob Isaac
SQL queries using the IN operator using PKs of different SortOrder were failing
during the WHERE clause compilation phase and causing OOM issues on the servers
when a large number (~50k) of RVC elements were used in the IN operator.
SQL queries were failing specifically during the skip scan filter generation.
The skip scan filter is generated using a list of point key
ranges.[ScanRanges.create|https://git.soma.salesforce.com/bigdata-packaging/phoenix/blob/e0737e0ea7ba7501e78fe23c16e7abca27bfd944/phoenix-core/src/main/java/org/apache/phoenix/compile/ScanRanges.java#L80]
The following getPointKeys
[code|https://git.soma.salesforce.com/bigdata-packaging/phoenix/blob/e0737e0ea7ba7501e78fe23c16e7abca27bfd944/phoenix-core/src/main/java/org/apache/phoenix/compile/ScanRanges.java#L541]
uses the KeyRange sets to create a new list of point-keys. When there are a
large number of RVC elements the above
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
