[
https://issues.apache.org/jira/browse/PHOENIX-7610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated PHOENIX-7610:
----------------------------------
Fix Version/s: 5.3.0
5.2.2
> Using CAST() on pk columns always result in full table scan
> -----------------------------------------------------------
>
> Key: PHOENIX-7610
> URL: https://issues.apache.org/jira/browse/PHOENIX-7610
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.1.3, 5.2.1
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
> Fix For: 5.3.0, 5.2.2
>
>
> For the range scan or point lookup on the single row, it is required to
> provide either full pk columns with equal comparison (point lookup) or prefix
> pk columns with equal comparison operator (range scan).
> However, when we use SQL CAST() function on pk columns to convert the type of
> the given column into another data type, the plan generated by where
> optimizer always performs full table scan instead of range scan or point
> lookup.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
