[
https://issues.apache.org/jira/browse/IGNITE-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847165#comment-15847165
]
ASF GitHub Bot commented on IGNITE-4631:
----------------------------------------
GitHub user skalashnikov opened a pull request:
https://github.com/apache/ignite/pull/1484
IGNITE-4631 Added check to ensure QueryEntity 'keyFields' is subset o…
…f 'fields'
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4631
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1484.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 #1484
----
commit 81fa92dc8846cf6f9a031bb5d8a7255b02ab266e
Author: skalashnikov <[email protected]>
Date: 2017-01-31T17:26:44Z
IGNITE-4631 Added check to ensure QueryEntity 'keyFields' is subset of
'fields'
----
> Node starts with incorrect QueryEntity configuration
> ----------------------------------------------------
>
> Key: IGNITE-4631
> URL: https://issues.apache.org/jira/browse/IGNITE-4631
> Project: Ignite
> Issue Type: Bug
> Components: SQL
> Reporter: Sergey Kalashnikov
> Assignee: Sergey Kalashnikov
> Priority: Minor
> Attachments: QueryEntityCaseMismatchTest.java
>
>
> When QueryEntity.keyFields property is used to specify compound key fields,
> it is possible to set the field names in wrong register.
> The node would start normally, but for SQL queries requesting key fields the
> resultset contains nulls in corresponding columns.
> The query processor internally fails to tell the key field from value field
> in this case.
> Note that for optimized marshaller, the keyFields aren't taken into account
> and queries return valid data.
> I believe the node shall not start with such configuration at all.
> See the attached test that reproduces the case.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
