[
https://issues.apache.org/jira/browse/HBASE-8593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664818#comment-13664818
]
Anoop Sam John commented on HBASE-8593:
---------------------------------------
[~jmhsieh] This was a need arised with my previous employer.
The scope is within ImportTSV tool only. Right now when the tool gets the data
lines read by MR, it converts every column value into a byte[] considering the
type to be String. But for us some column data of type int will be there in the
file. And later we will be having Filter based Scan with range condition on
this column. I thought while adding type support at client layer , it might be
good to add type support in this client side tool as well.
So HBase has nothing to do after data is importtsv'ed. I will change the issue
title a bit to make it very clear.
Yes I had some offline communication with Nick.
Hope folks at Huawei will give a patch for this.
> 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
