[jira] [Updated] (IGNITE-5571) Make sure that cache-less execution works as good as cache-based
[
https://issues.apache.org/jira/browse/IGNITE-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-5571:
Fix Version/s: (was: 2ю4)
2.4
> Make sure that cache-less execution works as good as cache-based
>
>
> Key: IGNITE-5571
> URL: https://issues.apache.org/jira/browse/IGNITE-5571
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>Priority: Critical
> Fix For: 2.4
>
>
> Compare the following two methods:
> 1) {{GridQueryProcessor.querySqlFields}} - old good entry point for query
> execution;
> 2) {{GridQueryProcessor.querySqlFieldsNoCache}} - new method for "cache-less"
> execution.
> Note how cache context is used in the first method:
> 1) First, it helps determine whether query can be converted to "local"
> 2) Second, it gets query parallelism of current cache, and if it differs from
> {{1}}, then it turns on {{distributedJoins}}.
> Neither of this happens in the second implementation. Moreover, I had to
> throw an exception for local queries, as I didn't know how to handle them
> properly.
> We need to investigate and fix these two deficiencies somehow. Probably some
> inputs from [~sergi.vladykin] would be required, to understand what is going
> on.
> Our ultimate goal is to make "cache-less" execution as good as the old one.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5571) Make sure that cache-less execution works as good as cache-based
[
https://issues.apache.org/jira/browse/IGNITE-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-5571:
Fix Version/s: (was: 2.3)
2ю4
> Make sure that cache-less execution works as good as cache-based
>
>
> Key: IGNITE-5571
> URL: https://issues.apache.org/jira/browse/IGNITE-5571
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>Priority: Critical
> Fix For: 2.4
>
>
> Compare the following two methods:
> 1) {{GridQueryProcessor.querySqlFields}} - old good entry point for query
> execution;
> 2) {{GridQueryProcessor.querySqlFieldsNoCache}} - new method for "cache-less"
> execution.
> Note how cache context is used in the first method:
> 1) First, it helps determine whether query can be converted to "local"
> 2) Second, it gets query parallelism of current cache, and if it differs from
> {{1}}, then it turns on {{distributedJoins}}.
> Neither of this happens in the second implementation. Moreover, I had to
> throw an exception for local queries, as I didn't know how to handle them
> properly.
> We need to investigate and fix these two deficiencies somehow. Probably some
> inputs from [~sergi.vladykin] would be required, to understand what is going
> on.
> Our ultimate goal is to make "cache-less" execution as good as the old one.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5571) Make sure that cache-less execution works as good as cache-based
[
https://issues.apache.org/jira/browse/IGNITE-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-5571:
Fix Version/s: (was: 2.1)
2.2
> Make sure that cache-less execution works as good as cache-based
>
>
> Key: IGNITE-5571
> URL: https://issues.apache.org/jira/browse/IGNITE-5571
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>Priority: Critical
> Fix For: 2.2
>
>
> Compare the following two methods:
> 1) {{GridQueryProcessor.querySqlFields}} - old good entry point for query
> execution;
> 2) {{GridQueryProcessor.querySqlFieldsNoCache}} - new method for "cache-less"
> execution.
> Note how cache context is used in the first method:
> 1) First, it helps determine whether query can be converted to "local"
> 2) Second, it gets query parallelism of current cache, and if it differs from
> {{1}}, then it turns on {{distributedJoins}}.
> Neither of this happens in the second implementation. Moreover, I had to
> throw an exception for local queries, as I didn't know how to handle them
> properly.
> We need to investigate and fix these two deficiencies somehow. Probably some
> inputs from [~sergi.vladykin] would be required, to understand what is going
> on.
> Our ultimate goal is to make "cache-less" execution as good as the old one.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
