[
https://issues.apache.org/jira/browse/IGNITE-5437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042560#comment-16042560
]
ASF GitHub Bot commented on IGNITE-5437:
----------------------------------------
GitHub user skalashnikov opened a pull request:
https://github.com/apache/ignite/pull/2107
IGNITE-5437: Handling query argument type for query derived partitions
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5437
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2107.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2107
----
commit db1e8b69f6bbd0a28aee638d63032ac0c3307d9e
Author: skalashnikov <[email protected]>
Date: 2017-06-07T16:53:53Z
IGNITE-5437: Fixed query argument type handling for query derived
partitions.
----
> SQL: Incorrect partition is derived from query when argument type differs
> from column type
> ------------------------------------------------------------------------------------------
>
> Key: IGNITE-5437
> URL: https://issues.apache.org/jira/browse/IGNITE-5437
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 2.1
> Reporter: Sergey Kalashnikov
> Assignee: Sergey Kalashnikov
> Fix For: 2.1
>
> Attachments: BugReproducer5437.java
>
>
> Ignite SQL attempts to derive partition from the query in certain cases and
> sends the map queries only to nodes which have those calculated partitions.
> Such queries are limited to contain equality conditions over key or affinity
> key columns at the left and constant or parameter at the right.
> When the type of argument does not match the column type, the calculation
> leads to wrong result.
> For example, the following query produces incomplete results when _key column
> is INTEGER and the argument is CHAR.
> select * from test where _key = ?
> However, this is valid and resultive query for H2, which does implicit
> conversion in such cases.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
