[jira] [Commented] (IGNITE-6112) Review and update C++ documentation according to new features.

["Denis Magda (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16144086#comment-16144086 ] 

Denis Magda commented on IGNITE-6112:
-------------------------------------

[~isapego], if {{QueryEntity}} is used for the schema configuration that a custom key and value name can be set via {{QueryEntity.setKeyFieldName}} and {{QueryEntity.setValueFieldName}}. Thus, the configuration should be updated first in your sample before the {{_key}} and {{_val}} can be removed. Does it answer your question?

> Review and update C++ documentation according to new features.
> --------------------------------------------------------------
>
>                 Key: IGNITE-6112
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6112
>             Project: Ignite
>          Issue Type: Task
>          Components: documentation
>    Affects Versions: 2.1
>            Reporter: Igor Sapego
>            Assignee: Igor Sapego
>
> It is needed to spend some time walking through the doc and updating it considering the latest features and changes https://apacheignite.readme.io/docs/quering-data 
> For instance:
> 1. The configuration section can be switched to the usage of DDL statements for tables creation and indexes definition.
> 2. Information about "_key" and "_value" should be wiped out because presently there is a way to set unique names for the whole key and value.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)