Re: SetLoacl is not work for Calcite

2023-06-05 Thread Alex Plehanov
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 :
>
> 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> rs = 
> ignite.cache("bfaccounttitle2020").query(fieldsQuery).getAll();
>
>


SetLoacl is not work for Calcite

2023-06-05 Thread y
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> rs = 
ignite.cache("bfaccounttitle2020").query(fieldsQuery).getAll();