Hello.
I'm sorry for it took so long time to reply to the message duing to I missed
some messages. For example, I have multiple nodes performing the same
computational tasks. The cache mode is partition and the data is cached by
affinity_key. So the different nodes have different data and node only
query/calculate data from itself. If there is no setLocal, the node will query
data from other nodes, which is inefficient. That's why i need setLocal. What
should I do if without setLocal?
Yours,
Hu Tiany
2023/6/30
At 2023-06-05 19:21:13, "Alex Plehanov" <plehanov.a...@gmail.com> wrote:
>Hello,
>
>The Calcite-based SQL engine currently doesn't analyze any properties
>of SqlFieldsQuery except "Sql", "Schema", "Args" and
>"QueryInitiatorId". Some of the rest properties are useless for the
>Calcite-based engine at all (for example, "DistributedJoins", since
>all joins in the Calcite-based engine are distributed by default if
>needed). But, perhaps, others can be useful. If you are really sure
>that the "Local" property is necessary for the new SQL engine, feel
>free to create a ticket and describe the reason why we need it.
>
>пн, 5 июн. 2023 г. в 12:05, y <hty1994...@163.com>:
>>
>> Hello igniters,
>> Just like the title, setLocal seems invalid for Calcite 2.15. When I set
>> ‘setLocal = true’ and query data from one node, the result sets is returned
>> from all data nodes. This problem is not present in version 2.13 ，which not
>> use Calcite. I'd like to know is this an error? If yes it is, When will it
>> be fixed?
>>
>> SqlFieldsQuery fieldsQuery = new SqlFieldsQuery(query);
>> fieldsQuery.setLocal(true); // uneffective for this line
>> List<List<?>> rs =
>> ignite.cache("bfaccounttitle2020").query(fieldsQuery).getAll();
>>
>>
