You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Alicia Ying Shu (JIRA)" <ji...@apache.org> on 2016/05/26 19:57:12 UTC
[jira] [Assigned] (PHOENIX-2934) Checking a coerce expression at
top level should not be necessary for Union All query
[ https://issues.apache.org/jira/browse/PHOENIX-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alicia Ying Shu reassigned PHOENIX-2934:
----------------------------------------
Assignee: Alicia Ying Shu
> Checking a coerce expression at top level should not be necessary for Union All query
> -------------------------------------------------------------------------------------
>
> Key: PHOENIX-2934
> URL: https://issues.apache.org/jira/browse/PHOENIX-2934
> Project: Phoenix
> Issue Type: Bug
> Reporter: Alicia Ying Shu
> Assignee: Alicia Ying Shu
>
> When working on PHOENIX-2886, found that we need special handling of coerce expression. Otherwise the following query would fail.
> {code}
> create table person ( id bigint not null primary key, firstname char(10), lastname varchar(10) );
> select id, cast( 'foo' as char(10)) firstname, lastname from person union all select * from person;
> {code}
> Checking a coerce expression at top level should not be necessary. Need to find out root cause on coerceExpression.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)