[
https://issues.apache.org/jira/browse/IGNITE-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930394#comment-15930394
]
ASF GitHub Bot commented on IGNITE-3487:
----------------------------------------
GitHub user skalashnikov opened a pull request:
https://github.com/apache/ignite/pull/1638
IGNITE-3487: Made _key and _val columns hidden
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-3487
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1638.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 #1638
----
commit 8946b312670b0721c3dc271c12933c80c41668ed
Author: skalashnikov <[email protected]>
Date: 2017-03-17T17:57:19Z
IGNITE-3487: Made _key and _val columns hidden
----
> _key and _val fields should be excluded from 'select * from' queries
> --------------------------------------------------------------------
>
> Key: IGNITE-3487
> URL: https://issues.apache.org/jira/browse/IGNITE-3487
> Project: Ignite
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 1.6
> Reporter: Valentin Kulichenko
> Assignee: Sergey Kalashnikov
> Labels: important
> Fix For: 2.0
>
>
> We have a pretty serious usability issue - predefined {{_key}} and {{_val}}
> fields are returned when query like {{select * from}} is executed. First of
> all, this is counterintuitive because user never defines or configures these
> fields. Second of all, they actually duplicate all other fields. And finally,
> they cause serialization exceptions because classes for key and value are not
> always available.
> We should exclude these fields from {{select * from}} queries, but this is a
> compatibility breaking change. It should be done in 2.0.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
