[
https://issues.apache.org/jira/browse/PHOENIX-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15282070#comment-15282070
]
Alicia Ying Shu commented on PHOENIX-2886:
------------------------------------------
[~maryannxue] With current architecture, we compile each query in Union All
separately. An option can be:
Set up data type conversion rules.
After compiling each query in Union All, exam the RowProjectors again against
the conversion rules.
For each query if needed change the projection data types, estimated sizes and
ValueSchema, etc.
serializeSchemaIntoScan(scan, schema)
Not as clean as I want, but given Phoenix's current compilation implementation
it is a way.
> Union ALL with Char column not present in the table in Query 1 but in Query
> 2 throw exception
> ----------------------------------------------------------------------------------------------
>
> Key: PHOENIX-2886
> URL: https://issues.apache.org/jira/browse/PHOENIX-2886
> Project: Phoenix
> Issue Type: Bug
> Reporter: Alicia Ying Shu
> Assignee: Alicia Ying Shu
>
> To reproduce:
> create table person ( id bigint not null primary key, firstname char(10),
> lastname varchar(10) );
> upsert into person values( 1, 'john', 'doe');
> upsert into person values( 2, 'jane', 'doe');
> -- fixed value for char(10)
> select id, 'foo' firstname, lastname from person union all select * from
> person;
> java.lang.RuntimeException: java.sql.SQLException: ERROR 201 (22000): Illegal
> data. Expected length of at least 106 bytes, but had 13
> -- fixed value for bigint
> select cast( 10 AS bigint) id, 'foo' firstname, lastname from person union
> all select * from person;
> java.lang.RuntimeException: java.sql.SQLException: ERROR 201 (22000): Illegal
> data. Expected length of at least 106 bytes, but had 13
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
