[
https://issues.apache.org/jira/browse/IGNITE-16052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Korol updated IGNITE-16052:
--------------------------------
Attachment: SqlDistributedJoinExample.java
> Long running query may show confusing value for distributedJoins=?
> ------------------------------------------------------------------
>
> Key: IGNITE-16052
> URL: https://issues.apache.org/jira/browse/IGNITE-16052
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Affects Versions: 2.11
> Reporter: Ilya Korol
> Priority: Major
> Attachments: SqlDistributedJoinExample.java
>
>
> Depending on query execution context long running query message may print
> *distributedJoin=false* despite distributed jons were explicitly enabled via
> JDBC connection url. This happens when ignite realizes that given query
> doesn't need distributed join machinery, for example when we join with
> REPLICATED table.
> However this still can be quite confusing during log analysis, so what about
> to rework printing long running query messages, so it would show whether
> distributed joins enabled/disabled and whether they were actually applied or
> not for given query. E.g.:
> {code}
> ... Long running query is finished [duration=122ms, type=MAP,
> distributedJoinEnabled=true, distributedJoinApplied=false,
> enforceJoinOrder=false
> {code}
> Attached a reproducer
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
