[jira] [Commented] (HIVE-13733) CTE + "IS NULL" predicate + column aliasing as existing column leads to wrong results

2016-05-11 Thread Mahens (JIRA)

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

Mahens commented on HIVE-13733:
---

let me check If hive.cbo.enable = true will resolve this issue.

> CTE + "IS NULL" predicate + column aliasing as existing column leads to wrong 
> results 
> --
>
> Key: HIVE-13733
> URL: https://issues.apache.org/jira/browse/HIVE-13733
> Project: Hive
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Dudu Markovitz
>Assignee: Jesus Camacho Rodriguez
>
> hive> create table t (i int,a string,b string);
> hive> insert into t values (1,'hello','world'),(2,'bye',null);
> hive> select * from t where t.b is null;
> 2 bye NULL
> This is wrong, all 3 columns should return the same value - t.a.
> hive> with cte as (select t.a as a,t.a as b,t.a as c from t where t.b is 
> null) select * from cte;
> bye   NULLbye
> However, these are right:
> hive> select t.a as a,t.a as b,t.a as c from t where t.b is null;
> bye   bye bye
> hive> with cte as (select t.a as a,t.a as b,t.a as c from t where t.b is not 
> null) select * from cte;OK
> hello hello   hello



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-13733) CTE + "IS NULL" predicate + column aliasing as existing column leads to wrong results

2016-05-11 Thread Mahens (JIRA)

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

Mahens commented on HIVE-13733:
---

Yes, Whenever we are using select statement, it works perfect. Within CTE with 
NULL Check is causing issue

> CTE + "IS NULL" predicate + column aliasing as existing column leads to wrong 
> results 
> --
>
> Key: HIVE-13733
> URL: https://issues.apache.org/jira/browse/HIVE-13733
> Project: Hive
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Dudu Markovitz
>Assignee: Jesus Camacho Rodriguez
>
> hive> create table t (i int,a string,b string);
> hive> insert into t values (1,'hello','world'),(2,'bye',null);
> hive> select * from t where t.b is null;
> 2 bye NULL
> This is wrong, all 3 columns should return the same value - t.a.
> hive> with cte as (select t.a as a,t.a as b,t.a as c from t where t.b is 
> null) select * from cte;
> bye   NULLbye
> However, these are right:
> hive> select t.a as a,t.a as b,t.a as c from t where t.b is null;
> bye   bye bye
> hive> with cte as (select t.a as a,t.a as b,t.a as c from t where t.b is not 
> null) select * from cte;OK
> hello hello   hello



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-7142) Hive multi serialization encoding support

2016-02-01 Thread Mahens (JIRA)

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

Mahens commented on HIVE-7142:
--

Does in  Hive 1.2 support UTF-16 or UTF-32 by adding 
"serialization.encoding"='GBK'

> Hive multi serialization encoding support
> -
>
> Key: HIVE-7142
> URL: https://issues.apache.org/jira/browse/HIVE-7142
> Project: Hive
>  Issue Type: Improvement
>  Components: Serializers/Deserializers
>Reporter: Chengxiang Li
>Assignee: Chengxiang Li
> Fix For: 0.14.0
>
> Attachments: HIVE-7142.1.patch.txt, HIVE-7142.2.patch, 
> HIVE-7142.3.patch, HIVE-7142.4.patch
>
>
> Currently Hive only support serialize data into UTF-8 charset bytes or 
> deserialize from UTF-8 bytes, real world users may want to load different 
> kinds of encoded data into hive directly. This jira is dedicated to support 
> serialize/deserialize all kinds of encoded data in SerDe layer. 
> For user, only need to configure serialization encoding on table level by set 
> serialization encoding through serde parameter, for example:
> {code:sql}
> CREATE TABLE person(id INT, name STRING, desc STRING)ROW FORMAT SERDE 
> 'org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe' WITH 
> SERDEPROPERTIES("serialization.encoding"='GBK');
> {code}
> or
> {code:sql}
> ALTER TABLE person SET SERDEPROPERTIES ('serialization.encoding'='GBK'); 
> {code}
> LIMITATIONS: Only LazySimpleSerDe support "serialization.encoding" property 
> in this patch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)