[
https://issues.apache.org/jira/browse/CALCITE-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde resolved CALCITE-5824.
----------------------------------
Fix Version/s: 1.35.0
Resolution: Fixed
Fixed in
[2ac9028ec|https://github.com/apache/calcite/commit/2ac9028ecccb42707f39950d5a2aa8dc6b7bcba3].
> Innodb IndexCondition should safely deal with null pointQueryKey
> ----------------------------------------------------------------
>
> Key: CALCITE-5824
> URL: https://issues.apache.org/jira/browse/CALCITE-5824
> Project: Calcite
> Issue Type: Improvement
> Components: innodb-adapter
> Affects Versions: 1.34.0
> Reporter: Ran Tao
> Assignee: Ran Tao
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.35.0
>
> Attachments: image-2023-07-09-22-20-50-230.png
>
>
> Innodb IndexCondition constructor safely deal with every null member
> variables except \{pointQueryKey}. It will lead many of referenced methods
> must check this null. For consistently, we need deal with \{pointQueryKey}
> when it's null (e.g. ImmutableList.of() when it's null).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
