You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/12/05 12:38:58 UTC
[jira] [Commented] (IGNITE-4308) Make QueryEntity.keyFields
optional for caches having SQL types as keys
[ https://issues.apache.org/jira/browse/IGNITE-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15722157#comment-15722157 ]
ASF GitHub Bot commented on IGNITE-4308:
----------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1286
> 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: Vladimir Ozerov
> Fix For: 1.8
>
>
> 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)