[
https://issues.apache.org/jira/browse/PHOENIX-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14391008#comment-14391008
]
Devaraj Das commented on PHOENIX-1580:
--------------------------------------
[~aliciashu], the question is what's the right way of designing/implementing it
long term that would also address longer term maintainability needs,
scalability needs, and also extensibility (if in the future, we add more
sophisticated queries can the current implementation be able to address it
without a lot of rework). From the commentary so far on this ticket, I think we
need to step back and take a look once at the current patch where it is lacking
addressability of feedback and such.
> 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-v2.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)
