hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-5245) HBase shell should use alternate jruby if JRUBY_HOME is set, should pass along JRUBY_OPTS
Date Sun, 22 Jan 2012 21:58:40 GMT

     [ https://issues.apache.org/jira/browse/HBASE-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack updated HBASE-5245:
-------------------------

    Attachment: 5245-v2.txt

Fix up so applies to TRUNK
                
> HBase shell should use alternate jruby if JRUBY_HOME is set, should pass along JRUBY_OPTS
> -----------------------------------------------------------------------------------------
>
>                 Key: HBASE-5245
>                 URL: https://issues.apache.org/jira/browse/HBASE-5245
>             Project: HBase
>          Issue Type: Improvement
>          Components: shell
>    Affects Versions: 0.90.4
>            Reporter: Philip (flip) Kromer
>            Priority: Minor
>         Attachments: 5245-v2.txt, hbase-jruby_home-and-jruby_opts.patch
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> Invoking {{hbase shell}}, the hbase runner launches the jruby jar directly, and so behaves
differently than the traditional jruby runner. Specifically, it
> * does not respect the {{JRUBY_OPTS}} environment variable (among other things, I cannot
launch the shell to use ruby-1.9 mode)
> * does not respect the {{JRUBY_HOME}} environment variable (placing things in an inconsistent
state if my classpath holds the system jruby).
> This patch allows you to use an alternative jruby and to specify options to the jruby
jar.
> * When the command is 'shell', adds {{$JRUBY_OPTS}} to the CLASS
> * When the command is 'shell' and {{$JRUBY_HOME}} is set, adds {{"$JRUBY_HOME/lib/jruby.jar"}}
to the classpath, and sets {{-Djruby.home}} and {{-Djruby.job}} config variables.

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

        

Mime
View raw message