[
https://issues.apache.org/jira/browse/HBASE-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985427#action_12985427
]
Jim R. Wilson commented on HBASE-3375:
--------------------------------------
Why not use Rhino, and have a JavaScript shell? The syntax for most commands
already has near perfect JavaScript analogs.
Consider this in today's shell:
{code}
get "table", "row", {COLUMN => "column:qualifier", TIMESTAMP => 12345, VERSIONS
=> 4}
{code}
Could be this in JS:
{code:javascript}
get( "table", "row", { COLUMN: "column:qualifier", TIMESTAMP: 12345, VERSIONS:
4} );
{code}
No parsing required, full scripting language power.
> Move away from jruby; build our shell elsewise either on another foundation
> or build up our own
> -----------------------------------------------------------------------------------------------
>
> Key: HBASE-3375
> URL: https://issues.apache.org/jira/browse/HBASE-3375
> Project: HBase
> Issue Type: Task
> Components: shell
> Reporter: stack
> Fix For: 0.92.0
>
>
> JRuby has been sullied; its been shipping *GPL jars with a while now. A hack
> up to remove these jars is being done elsewhere (HBASE-3374). This issue is
> about casting our shell anew atop a foundation that is other than JRuby or
> writing a shell of our own from scratch.
> JRuby has gotten us this far. It provides a shell and it also was used
> scripting HBase. It would be nice if we could get scripting and shell in the
> redo.
> Apart from the licensing issue above and that the fix will be reverting our
> JRuby to a version that is no longer supported and that is old, other reasons
> to move off JRuby are that while its nice having ruby to hand when scripting,
> the JRuby complete jar is 10 or more MB in size. Its bloated at least from
> our small shell perspective.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
