[
https://issues.apache.org/jira/browse/HBASE-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974406#action_12974406
]
Karthik Ranganathan commented on HBASE-3375:
--------------------------------------------
Awesome discussion. I think the only way to make scripting for HBase take off
is to allow scripting in any language. Language lock-in for scripting takes
away the real advantage of scripting - all the time is spent in looking up the
syntax (unless the person writing is committed to learning the language). So in
that sense, REST + JSON is awesome.
On a tangential note, REST+JSON also allows us to easily write HBase clients
(that have ZK integration) in languages other than Java (aka C++). This would
allow efficiently interacting with HBase from non Java services.
If we are agreed on the REST+JSON approach - now its only a matter of how to
write the shell the fastest in any language. I am not familiar with where the
REST gateway stands today, and how much work it is to move all the structures
to JSON. If these are easy to get out the door, then we should only think about
the fastest way to write the shell.
> 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.
