[
https://issues.apache.org/jira/browse/HBASE-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973988#action_12973988
]
Andrew Purtell commented on HBASE-3375:
---------------------------------------
Discussed this on IRC a bit today:
[15:08] <apurtell> anybody particularly itching to do 3375?
[15:10] <jgray> karthik wants to do some ANTLR + JSON... and maybe at the same
time we could finish the move stack started a while ago to schemas in ZK as JSON
[15:10] <jgray> apurtell: what were you thinking?
[15:11] <apurtell> use antlr, maintain current command set, keep enough
ruby syntax so current scripts execute (and allow scripting), everything json,
optional mode for running against REST interface instead of Java API
[15:13] <apurtell> i'm neutral as to ruby syntax but everyone talking
about this issue would like to keep some kind of scripting capability
[15:15] <St^Ack> Scripting hasn't really taken off.
[15:16] <St^Ack> I think scripting only really makes sense if 'real'
language underpinning shell
[15:16] <St^Ack> else, ANTLR'ing up those loops -- whiles, fors, etc. --
is going to be time consuming
[15:17] <apurtell> i don't think it would be too bad, i'm talking about
flow control, variable assignment/substitution, and expressions
[15:18] <apurtell> it can be "real" enough... or not... depends if there's
value in doing it
[15:19] <apurtell> (not talking about classes or anything not fitting an
informal definition of "basic")
[15:20] <jgray> i also like idea of JSON + REST allowing shells written in
anything
[15:20] <St^Ack> apurtell: I just see it as wasted effort if already a
grammer/parser written -- e.g. pre-existing shell
[15:25] <jgray> well i personally hate the shell
[15:25] <apurtell> what would make it better?
[15:25] <jgray> and would like to move to json instead of the horrid ruby syntax
[15:25] <jgray> and work on REST or something that would allow other shells /
utils to be written atop it
[15:25] <larsgeorge> +1
[15:25] <apurtell> i'm not fond of the current shell either
[15:26] <jgray> no jruby deps, no jruby startup, no jruby syntax. move to json
to go inline with other changes we'd like to make (schema as json in zk, etc).
[15:26] <jgray> well idea would be you could easily write other utils in any
language
[15:27] <jgray> so with roll-your-own, shell is implemented in java
[15:27] <jgray> trivial to tie into REST
[15:28] <jgray> let's not let this block us
[15:28] <jgray> but if someone wants to build something i think it would be good
[15:30] <St^Ack> low priority though
[15:30] <jgray> shell to json would make sense tho
[15:36] <gario> ok, so if the idea is JSON throughout, why not a javascript
repl?
[15:40] <St^Ack> gario: jscript fine by me... shell was bad last I
looked but maybe there's a plugin or something... rhino engine is part of jvm
[15:41] <apurtell> any reasonable js repls?
[16:04] <gario> looks like you can use jline with the rhino shell, fwiw:
http://blog.norrisboyd.com/2008/03/better-line-editing-for-rhino-shell.html
> 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.
