[
https://issues.apache.org/jira/browse/IGNITE-11210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16781507#comment-16781507
]
Ignite TC Bot commented on IGNITE-11210:
----------------------------------------
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Scala (Examples){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=3199660]]
* ScalarSelfTestSuite: ScalarProjectionSpec.ScalarProjectionPimp class should
return shown nodes - 0,0% fails in last 440 master runs.
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3199740&buildTypeId=IgniteTests24Java8_RunAll]
> SQL: Introduce common logical execution plan for all query types
> ----------------------------------------------------------------
>
> Key: IGNITE-11210
> URL: https://issues.apache.org/jira/browse/IGNITE-11210
> Project: Ignite
> Issue Type: Task
> Components: sql
> Reporter: Vladimir Ozerov
> Assignee: Vladimir Ozerov
> Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> At the moment we have a lot of various cached stuff used for different SQL
> types (prepared statements for local queries, two-step queries for
> distributed queries, update plan for DML).
> What we need instead of having multiple caches is to create common execution
> plan for every query, which will hold both DML and SELECT stuff. Approximate
> content of such a plan:
> # Two-step plan
> # DML plan
> # Partition pruning stuff
> # May be even cached physical node distribution (for reduce queries) for the
> given {{AffinityTopologyVersion}}
> # Probably {{AffinityTopologyVersion}}
> Then we will perform a single plan lookup/build per every query execution. In
> future we will probably display these plans in SQL views.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
