phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-2934) Checking a coerce expression at top level should not be necessary for Union All query
Date Sun, 12 Jun 2016 18:15:21 GMT

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

James Taylor commented on PHOENIX-2934:
---------------------------------------

+1. Good job, [~ayingshu].

> 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
>         Attachments: PHOENIX-2934-v1.patch, PHOENIX-2934.patch
>
>
> 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)

Mime
View raw message