[ https://issues.apache.org/jira/browse/PHOENIX-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342556#comment-14342556
]
Alicia Ying Shu commented on PHOENIX-1580:
------------------------------------------
[~maryannxue] Just to confim: "And as a result you will have to create a new RowProjector,
a single one for both side of the query." By this, you meant create a new RowProjector for
all the subSelects in the Union All query?
Just added TupleProjector alone would not work. As you later mentioned, you need to create
a temp table for it. It is exactly what I want to avoid since we do not need a temp table
for UNION ALL to eliminate duplicates. We can just stream the results. Not creating a temp
table have multiple advantages such as performance benefit and avoiding OutOfMemory issue.
But looks like with current architecture, it is easy to create a temp table before we project
the results in the client.
> 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: unionall-wipe.patch
>
>
> Select * from T1
> UNION ALL
> Select * from T2
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
|