asterixdb-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Taewoo Kim (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ASTERIXDB-1359) IntroduceProjectsRule should be the *only rule that adds projects to the pipeline
Date Mon, 21 Mar 2016 17:56:25 GMT

    [ https://issues.apache.org/jira/browse/ASTERIXDB-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15204746#comment-15204746
] 

Taewoo Kim commented on ASTERIXDB-1359:
---------------------------------------

I think it is required sometimes. For example, in my index-only plan branch, before applying
UNION, I need to unify the schema from the both side in the plan. Without adding a manual
project, it's impossible to unify the two different schema. 

> IntroduceProjectsRule should be the *only rule that adds projects to the pipeline
> ---------------------------------------------------------------------------------
>
>                 Key: ASTERIXDB-1359
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1359
>             Project: Apache AsterixDB
>          Issue Type: Improvement
>            Reporter: Steven Jacobs
>            Assignee: Steven Jacobs
>
> We have a rule, IntroduceProjectsRule, which does full analysis of the pipeline to determine
where projects should be added. It seems that with such a rule in place, other places shouldn't
need to insert any projects (One clear example is IntroduceSecondary....Rule). It would be
useful to examine where projects are being inserted and whether they actually need to be.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message