phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maryann Xue (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-1580) Support UNION ALL
Date Wed, 01 Apr 2015 14:47:53 GMT

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

Maryann Xue commented on PHOENIX-1580:
--------------------------------------

[~ayingshu] Having an outer select has NOTHING to do with the TupleProjectionPlan and is more
logically and conceptually reasonable than using the first query as the outer select and keep
the rest in a list. This is about how you would represent the query structure and is independent
of how you would implement it.
And I do believe that with a little debugging and understanding ability, adding a special
or null node as the FROM node of the outer query would not be a problem at all. 

> Support UNION ALL
> -----------------
>
>                 Key: PHOENIX-1580
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1580
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Alicia Ying Shu
>            Assignee: Alicia Ying Shu
>         Attachments: PHOENIX-1580-grammar.patch, Phoenix-1580-v1.patch, phoenix-1580-v1-wipe.patch,
phoenix-1580.patch, unionall-wipe.patch
>
>
> Select * from T1
> UNION ALL
> Select * from T2



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

Mime
View raw message