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

Ashutosh Chauhan commented on HIVE-5221:
----------------------------------------

[~brocknoland] I think you have a valid point. I think we should do same on 
write side as we are now doing on read side, ie if user wants to store binary 
data in text file (which is weird, but anyways) he need to use an udf to encode 
it before passing it to serde. Than, we are consistent on both read and write 
side, asking user to use appropriate udfs for encoding/decoding and setting 
serde free from any assumptions.
[~kamrul] Can you make changes in LazyUtils.writePrimitiveUtf8 so that it 
doesn't do any encoding?

> Issue in column type with data type as BINARY
> ---------------------------------------------
>
>                 Key: HIVE-5221
>                 URL: https://issues.apache.org/jira/browse/HIVE-5221
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Arun Vasu
>            Assignee: Mohammad Kamrul Islam
>            Priority: Critical
>         Attachments: HIVE-5221.1.patch, HIVE-5221.2.patch
>
>
> Hi,
> I am using Hive 10. When I create an external table with column type as 
> Binary, the query result on the table is showing some junk values for the 
> column with binary datatype.
> Please find below the query I have used to create the table:
> CREATE EXTERNAL TABLE BOOL1(NB BOOLEAN,email STRING, bitfld BINARY)
>  ROW FORMAT DELIMITED
>    FIELDS TERMINATED BY '^'
>    LINES TERMINATED BY '\n'
> STORED AS TEXTFILE
> LOCATION '/user/hivetables/testbinary';
> The query I have used is : select * from bool1
> The sample data in the hdfs file is:
> 0^a...@abc.com^001
> 1^a...@abc.com^010
>  ^a...@abc.com^011
>  ^a...@abc.com^100
> t^a...@abc.com^101
> f^a...@abc.com^110
> true^a...@abc.com^111
> false^a...@abc.com^001
> 123^    ^01100010
> 12344^    ^01100001
> Please share your inputs if it is possible.
> Thanks,
> Arun



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to