[
https://issues.apache.org/jira/browse/HADOOP-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548855
]
Bryan Duxbury commented on HADOOP-2329:
---------------------------------------
I don't think there should be a type field. That's up to the application to
deal with. It would add a ton of overhead to everything in HBase and require a
huge overhaul of how stuff works. It would also take away a good deal of
flexibility.
The fact that the shell cannot understand user-supplied key/value based data
types is not a good motivation for adding it. The shell should really only be a
administrative utility anyway, just enough to be able create and drop tables
and to peek at a row here or there. I doubt that people who write their
applications to use HBase are going to be limited by the lack of built-in data
types.
> [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing
> and stroing data
> --------------------------------------------------------------------------------------------
>
> Key: HADOOP-2329
> URL: https://issues.apache.org/jira/browse/HADOOP-2329
> Project: Hadoop
> Issue Type: New Feature
> Components: contrib/hbase
> Affects Versions: 0.16.0
> Reporter: Edward Yoon
> Assignee: Edward Yoon
> Fix For: 0.16.0
>
>
> A built-in data type is a fundamental data type that the hbase shell defines.
> (character strings, scalars, ranges, arrays, ... , etc)
> If you need a specialized data type that is not currently provided as a
> built-in type,
> you are encouraged to write your own user-defined data type using UDC(not yet
> implemented).
> (or contribute it for distribution in a future release of hbase shell)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
