[
https://issues.apache.org/jira/browse/HBASE-8593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664385#comment-13664385
]
Jonathan Hsieh commented on HBASE-8593:
---------------------------------------
Can your provide a toy input example and what you want in hbase for that row
after it is importtsv'ed?
Can you be specific with this feature request's scope? Do you just plan to
include int/long/float encodings? Is this in values, col names, or row-keys?
> Type support for ImportTSV
> --------------------------
>
> Key: HBASE-8593
> URL: https://issues.apache.org/jira/browse/HBASE-8593
> Project: HBase
> Issue Type: Sub-task
> Components: mapreduce
> Reporter: Anoop Sam John
> Fix For: 0.95.2
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
