hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-3375) Move away from jruby; build our shell elsewise either on another foundation or build up our own
Date Wed, 22 Dec 2010 23:25:01 GMT

    [ https://issues.apache.org/jira/browse/HBASE-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974435#action_12974435
] 

Andrew Purtell commented on HBASE-3375:
---------------------------------------

Regarding the REST gateway today, use Content-Type: application/json for PUT or POST and Accept:
application/json for GET. We model data representation using JAXB bindings and leverage Jersey's
support for wiring JAXB to JSON. 

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


Mime
View raw message