[
https://issues.apache.org/jira/browse/HIVE-5871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14110871#comment-14110871
]
Brock Noland commented on HIVE-5871:
------------------------------------
Hi Rui,
Yes, I agree that it makes sense to write it like that from the outset. The
case I was thinking of is where you have a non-base64 string, junk, which
"appears" to be in base64 and thus decode is called. Today that would return
either null or empty byte array but after this change it will appear as-is.
Thinking about this more, perhaps we can commit the change as-is. [~szehon] do
you have thoughts on this?
> Use multiple-characters as field delimiter
> ------------------------------------------
>
> Key: HIVE-5871
> URL: https://issues.apache.org/jira/browse/HIVE-5871
> Project: Hive
> Issue Type: Improvement
> Components: Contrib
> Affects Versions: 0.12.0
> Reporter: Rui Li
> Assignee: Rui Li
> Attachments: HIVE-5871.2.patch, HIVE-5871.3.patch, HIVE-5871.4.patch,
> HIVE-5871.5.patch, HIVE-5871.6.patch, HIVE-5871.patch
>
>
> By default, hive only allows user to use single character as field delimiter.
> Although there's RegexSerDe to specify multiple-character delimiter, it can
> be daunting to use, especially for amateurs.
> In the patch, I add a new SerDe named MultiDelimitSerDe. With
> MultiDelimitSerDe, users can specify a multiple-character field delimiter
> when creating tables, in a way most similar to typical table creations.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
