[jira] [Commented] (HBASE-6612) Hbase command line improvements

2012-09-14 Thread Michael Drzal (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-6612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455781#comment-13455781
 ] 

Michael Drzal commented on HBASE-6612:
--

[~ionignat] would HBASE-6592 address your issues?  If so, it might make sense 
to just make this a dupe of that jira.

 Hbase command line improvements
 ---

 Key: HBASE-6612
 URL: https://issues.apache.org/jira/browse/HBASE-6612
 Project: HBase
  Issue Type: New Feature
  Components: scripts, shell
Affects Versions: 0.94.1
Reporter: Ionut Ignatescu
Priority: Minor

 Currently, if the row key or any column value is something different than a 
 string, when a scan is performed via command line, the value extracted are 
 not decoded to a human-readable format.
 It would be nice to have support to some standard data 
 types(long,double,etc..) or to specify some custom decoders(this would be 
 extremely useful for tables having composed keys). 

--
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


[jira] [Commented] (HBASE-6612) Hbase command line improvements

2012-08-23 Thread Ionut Ignatescu (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-6612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13440673#comment-13440673
 ] 

Ionut Ignatescu commented on HBASE-6612:


I think it not about adding data types, it's more about adding SerDes support. 
Behind a common model(interface), it should be support for any standard data 
type: long, double, strings with different encoding, etc.
Also, in this way we could add support for any custom model(Ex: a table with a 
composed key, where firsts 4 bytes are an integer value, next eight are a long 
representing a date and the rest are a result of a hash function). In this way 
is much more easier to perform operations using shell. 

 Hbase command line improvements
 ---

 Key: HBASE-6612
 URL: https://issues.apache.org/jira/browse/HBASE-6612
 Project: HBase
  Issue Type: New Feature
  Components: scripts, shell
Affects Versions: 0.94.1
Reporter: Ionut Ignatescu
Priority: Minor

 Currently, if the row key or any column value is something different than a 
 string, when a scan is performed via command line, the value extracted are 
 not decoded to a human-readable format.
 It would be nice to have support to some standard data 
 types(long,double,etc..) or to specify some custom decoders(this would be 
 extremely useful for tables having composed keys). 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (HBASE-6612) Hbase command line improvements

2012-08-22 Thread Jonathan Hsieh (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-6612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13439848#comment-13439848
 ] 

Jonathan Hsieh commented on HBASE-6612:
---

Is this proposing to add types to hbase? (either by convention or internally?)

 Hbase command line improvements
 ---

 Key: HBASE-6612
 URL: https://issues.apache.org/jira/browse/HBASE-6612
 Project: HBase
  Issue Type: New Feature
  Components: scripts, shell
Affects Versions: 0.94.1
Reporter: Ionut Ignatescu
Priority: Minor

 Currently, if the row key or any column value is something different than a 
 string, when a scan is performed via command line, the value extracted are 
 not decoded to a human-readable format.
 It would be nice to have support to some standard data 
 types(long,double,etc..) or to specify some custom decoders(this would be 
 extremely useful for tables having composed keys). 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira