[
https://issues.apache.org/jira/browse/HIVE-5871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14098025#comment-14098025
]
Rui Li commented on HIVE-5871:
------------------------------
Hi [~brocknoland], I made the change because MultiDelimitSerde won't base-64
encode or decode binary data, in case the encoded string should be the same
with the multiple-character delimiter. And this in turn is because I want to
reuse the LazySimpleSerde for most of the serialize and deserialize logic.
Please let me know if this change is unacceptable and we need a better way to
handle it.
> 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)
