[
https://issues.apache.org/jira/browse/HIVE-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095669#comment-13095669
]
John Sichi commented on HIVE-2380:
----------------------------------
Ashutosh, maybe we can discuss this one at the contributor meetup next week
(and then record the conclusions here).
A few questions that I've heard so far:
* Is there a design doc somewhere?
* Since Hive already has an array type, but this feature is independent, we
probably want a different type name than bytearray.
* For conversions, is going through string for all types a good default
behavior? An alternative would be to prevent implicit conversions altogether,
and force users to pick the UDF with the desired behavior. E.g. for
string/binary conversion, it's a good idea to be able to specify an encoding
rather than always using the JVM default.
* How does the new type work with TRANSFORM scripts, UDF's, saving to textfile,
etc?
* Don't we need more accessor functions (e.g. making the existing string
functions such as LENGTH work)?
> Add ByteArray Datatype
> ----------------------
>
> Key: HIVE-2380
> URL: https://issues.apache.org/jira/browse/HIVE-2380
> Project: Hive
> Issue Type: New Feature
> Components: Serializers/Deserializers
> Reporter: Ashutosh Chauhan
> Assignee: Ashutosh Chauhan
> Attachments: hive-2380.patch
>
>
> Add bytearray as a primitive data type.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
