ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilya Kasnacheev (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-7556) Docs should feature specifying SQL key more prominently
Date Mon, 29 Jan 2018 10:18:00 GMT
Ilya Kasnacheev created IGNITE-7556:
---------------------------------------

             Summary: 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


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)

Mime
View raw message