ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Kalashnikov (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (IGNITE-4631) Node starts with incorrect QueryEntity configuration
Date Wed, 01 Feb 2017 09:13:52 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sergey Kalashnikov resolved IGNITE-4631.
----------------------------------------
    Resolution: Fixed
      Assignee: Vladimir Ozerov  (was: Sergey Kalashnikov)

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: Vladimir Ozerov
>            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)

Mime
View raw message