[
https://issues.apache.org/jira/browse/IGNITE-18594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-18594:
-----------------------------------------
Labels: calcite (was: )
> SqlFieldQueries with partitions on Calcite
> ------------------------------------------
>
> Key: IGNITE-18594
> URL: https://issues.apache.org/jira/browse/IGNITE-18594
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.14
> Reporter: Benjamin Garaude
> Priority: Major
> Labels: calcite
>
> I tried to switch my existing code to Calcite on Ignite 2.14.0.
> We do use some SqlFieldQuery, and call .setPartitions(int...) on them to only
> return results from specific partitions. This works fine with the H2 engine.
> However, on calcite engine it seem to return all results for a query whatever
> we pass to .setPartitions(int...).
> The javadoc for .setPartitions(int...) says: "The query will be executed only
> on nodes which are primary for specified partitions.", which makes me thinks
> that the correct behavior is calcite, and that H2 is incorrect.
> In any case, it would be better to have the same behavior whatever the engine
> is. Additionally, is there a way to return results for a specific partition
> on calcite?
> Here is a simple test case reproducing this issue:
> [https://gist.github.com/bgaraude/873c40305ca0874f88f76f1ebe5dcf74]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
