[
https://issues.apache.org/jira/browse/IGNITE-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15695884#comment-15695884
]
ASF GitHub Bot commented on IGNITE-4308:
----------------------------------------
GitHub user alexpaschenko opened a pull request:
https://github.com/apache/ignite/pull/1286
IGNITE-4308 Ignore QueryEntity.keyFields when key is an SQL type
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4308
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1286.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 #1286
----
commit 8a522ec9457363b107fe4a6df0742e5c629689ca
Author: Alexander Paschenko <alexander.a.pasche...@gmail.com>
Date: 2016-11-25T13:33:46Z
IGNITE-4308 Ignore QueryEntity.keyFields when key is an SQL type
----
> Make QueryEntity.keyFields optional for caches having SQL types as keys
> -----------------------------------------------------------------------
>
> Key: IGNITE-4308
> URL: https://issues.apache.org/jira/browse/IGNITE-4308
> Project: Ignite
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 1.8
> Reporter: Alexander Paschenko
> Assignee: Alexander Paschenko
>
> Initial implementation of DML requires the user to specify keyFields in
> configuration explicitly, even if it's empty, in cases when DML is used and
> binary marshaller is used. As [~vozerov] noted, it could affect usability, if
> even a little, so this should be fixed - when a primitive/simple SQL type is
> used as a key, it's obvious that there's no key fields and hence it's not
> necessary to specify empty keyFields in this case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
