[jira] [Commented] (HIVE-4485) beeline prints null as empty strings

["Thejas M Nair (JIRA)" <ji...@apache.org>]

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

Thejas M Nair commented on HIVE-4485:
-------------------------------------

bq. Hive 0.11.0 was released with the current behavior (nulls printed as "NULL")
[~cwsteinbach] I want to clarify that this is about beeline and beeline currently prints nulls as emtpy strings. I agree that switching this would be a backward incompatible change. But I think it is important to distinguish between empty strings and null for obvious reasons.

I think this is a general problem - Hive has undesirable defaults in some cases and changing those would break backward compatibility. I think we should give the users (specially new users), the option of using the more sensible but backward incompatible configuration defaults. I will open a new jira for that.


> beeline prints null as empty strings
> ------------------------------------
>
>                 Key: HIVE-4485
>                 URL: https://issues.apache.org/jira/browse/HIVE-4485
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>            Reporter: Thejas M Nair
>            Assignee: Thejas M Nair
>         Attachments: HIVE-4485.1.patch, HIVE-4485.2.patch
>
>
>  beeline is printing nulls as emtpy strings. 
> This is inconsistent with hive cli and other databases, they print null as "NULL" string.



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