[
https://issues.apache.org/jira/browse/HBASE-5548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13227975#comment-13227975
]
Jesse Yates commented on HBASE-5548:
------------------------------------
bq. get 'tablename', 'yadda', 'yadda'....
Yeah, nothing changes there. In fact, scan (which is the only change that patch
introduces) still will work exactly the same way. Same deal for doing something
like t.scan
bq. On get_table, should it just be table? 'status' dumps out status,
'version', dumps out 'version'. Maybe it should stay get_table, because it
returns something you can catch into a variable?
I was thinking it should stay get_table since table will be clutter the overall
naming a little (Table is also the name of the ::Hbase::Table class) and yeah,
it implies holding a reference, which _all_ the other commands don't give you.
I would imagine doing
{code}
t = table 't1'
{code}
as actually creating the table if it doesn't exist, or just getting a reference
to it (similar to how 'create' works in the latest patch). A follow-on patch
would be nice there.
I want to think about the 'right' way to do the extension of ::Hbase::Table,
rather than this piecemeal, method-by-method, decentralized increase. Also,
adding the same type of system for put, get, delete, etc would be nice. But,
yeah, close!
> Add ability to get a table in the shell
> ---------------------------------------
>
> Key: HBASE-5548
> URL: https://issues.apache.org/jira/browse/HBASE-5548
> Project: HBase
> Issue Type: Improvement
> Components: shell
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Fix For: 0.96.0
>
> Attachments: ruby_HBASE-5528-v0.patch, ruby_HBASE-5548-v1.patch
>
>
> Currently, all the commands that operate on a table in the shell first have
> to take the table as name as input.
> There are two main considerations:
> * It is annoying to have to write the table name every time, when you should
> just be able to get a reference to a table
> * the current implementation is very wasteful - it creates a new HTable for
> each call (but reuses the connection since it uses the same configuration)
> We should be able to get a handle to a single HTable and then operate on that.
--
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
