[
https://issues.apache.org/jira/browse/HBASE-8593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791662#comment-13791662
]
Nick Dimiduk commented on HBASE-8593:
-------------------------------------
Hi Istvan,
Sound like very useful extensions. I like being able to specify compound rowkey
components; do you have a way to specify a separator between components, are
you assuming everything will be fixed width, something else?. Is your new type
parser backwards-compatible with the old one? Rather than defining your own
type dispatching enum, how about mapping to the DataType implementations
(RawInteger, RawDouble, etc)?
-n
> Type support in ImportTSV tool
> ------------------------------
>
> Key: HBASE-8593
> URL: https://issues.apache.org/jira/browse/HBASE-8593
> Project: HBase
> Issue Type: Sub-task
> Components: mapreduce
> Reporter: Anoop Sam John
> Assignee: rajeshbabu
> Fix For: 0.96.0
>
> Attachments: HBASE-8593.patch, HBASE-8593_v2.patch,
> HBASE-8593_v4.patch
>
>
> Now the ImportTSV tool treats all the table column to be of type String. It
> converts the input data into bytes considering its type to be String. Some
> times user will need a type of say int/float to get added to table by using
> this tool.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
