[
https://issues.apache.org/jira/browse/IGNITE-7556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16344288#comment-16344288
]
Denis Magda commented on IGNITE-7556:
-------------------------------------
[~ilyak] , thanks for bringing this to our attention. Technically, this issue
arises only when the annotations or QueryEntities are used for SQL level
configuration. If a table is created with CREATE TABLE command then the INSERT
doc is 100% correct. I'll think over on how to add information on "_key" to
cover QueryEntity use cases.
> Docs should feature specifying SQL key more prominently
> -------------------------------------------------------
>
> Key: IGNITE-7556
> URL: https://issues.apache.org/jira/browse/IGNITE-7556
> Project: Ignite
> Issue Type: Bug
> Components: documentation
> Reporter: Ilya Kasnacheev
> Priority: Minor
> Fix For: 2.5
>
>
> Descriptions on [https://apacheignite-sql.readme.io/docs/schema-and-indexes]
> are not DML-friendly
> After reading this page and [https://apacheignite-sql.readme.io/docs/insert],
> one would likely still unable to write working INSERT because there won't be
> primary key in it.
> Their only chance is to spot _key reference in infoblock, or infer usability
> of setKeyFields() with single key type. Both are unlikely, leading to
> questions such as
> [https://stackoverflow.com/questions/48460214/how-do-i-read-data-from-ignite-kv-storage-using-jdbc]
> see {{Key is missing from query}}
> Such problems are hard to debug. They can be avoided if all examples of
> QueryEntities in docs will contain setKeyFields, and INSERT docs page will
> refer to _key field.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
