You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by "Denis A. Magda (Jira)" <ji...@apache.org> on 2019/11/18 21:04:00 UTC

[jira] [Created] (IGNITE-12382) Clarify "collocated" flag documentation

Denis A. Magda created IGNITE-12382:
---------------------------------------

             Summary: Clarify "collocated" flag documentation
                 Key: IGNITE-12382
                 URL: https://issues.apache.org/jira/browse/IGNITE-12382
             Project: Ignite
          Issue Type: Bug
          Components: documentation
    Affects Versions: 2.7.6
            Reporter: Denis A. Magda
            Assignee: Artem Budnikov
             Fix For: 2.8


Documentation of the JDBC and ODBC drivers doesn't explain when and why the "collocated" flag needs to be set. The docs are vague and not clear:
https://apacheignite-sql.readme.io/docs/jdbc-driver
https://apacheignite-sql.readme.io/docs/connection-string-and-dsn

In fact, the optimization is useful for queries with GROUP BY operand. The docs need to be improved with the content of the Javadoc and a summary shared in the dev list discussion:
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/query/SqlFieldsQuery.html#isCollocated--
http://apache-ignite-developers.2346864.n4.nabble.com/Collocated-replicatedOnly-flags-for-Thin-JDBC-driver-td44357.html



--
This message was sent by Atlassian Jira
(v8.3.4#803005)