[
https://issues.apache.org/jira/browse/IGNITE-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15858028#comment-15858028
]
Vladimir Ozerov edited comment on IGNITE-4631 at 2/8/17 2:13 PM:
-----------------------------------------------------------------
[~skalashnikov],
Fix looks good. I performed several minor changes:
- Added field name to exception message
- Simplified test.
Please review these changes in {{master}}, commit {{46ff66e}}.
was (Author: vozerov):
[~skalashnikov],
Fix looks good. I performed several minor changes:
- Added field name to exception message
- Simplified test.
Please review this changes in {{master}}, commit {{46ff66e}}.
> 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
> Fix For: 1.9
>
> 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)
