Andrey Novikov created IGNITE-21416:
---------------------------------------
Summary: Add documentation for FORCE_INDEX/NO_INDEX hints
Key: IGNITE-21416
URL: https://issues.apache.org/jira/browse/IGNITE-21416
Project: Ignite
Issue Type: Improvement
Components: documentation
Reporter: Andrey Novikov
Globally it works the same way as in
[https://ignite.apache.org/docs/latest/SQL/sql-calcite#force_index-no_index],
but has some difference when FORCE_INDEX and NO_INDEX used together in the same
query. When both hints reference to the same index {{SELECT /*+
FORCE_INDEX('idx'), NOINDEX */, {{SELECT /*+ NO_INDEX(TBL1_IDX2),
FORCE_INDEX(TBL2_IDX2) */, ...}} -}} it is invalid case. SQL is declarative
language and we shouldn't expect {{hints}} collection is ordered.
We need to fix example section and rewrite "Hint Scope" section.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
