You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Philip (flip) Kromer (Created) (JIRA)" <ji...@apache.org> on 2012/01/22 00:57:40 UTC
[jira] [Created] (HBASE-5245) HBase shell uses system JRuby if
JRUBY_HOME is set, respects JRUBY_OPTS
HBase shell uses system JRuby if JRUBY_HOME is set, respects JRUBY_OPTS
-----------------------------------------------------------------------
Key: HBASE-5245
URL: https://issues.apache.org/jira/browse/HBASE-5245
Project: HBase
Issue Type: Improvement
Components: shell
Reporter: Philip (flip) Kromer
Priority: Minor
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
[jira] [Commented] (HBASE-5245) HBase shell should use alternate
jruby if JRUBY_HOME is set, should pass along JRUBY_OPTS
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13191878#comment-13191878 ]
Hudson commented on HBASE-5245:
-------------------------------
Integrated in HBase-TRUNK #2645 (See [https://builds.apache.org/job/HBase-TRUNK/2645/])
HBASE-5245 HBase shell should use alternate jruby if JRUBY_HOME is set, should pass along JRUBY_OPTS
stack :
Files :
* /hbase/trunk/bin/hbase
> 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
[jira] [Commented] (HBASE-5245) HBase shell uses system JRuby if
JRUBY_HOME is set, respects JRUBY_OPTS
Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190563#comment-13190563 ]
Hadoop QA commented on HBASE-5245:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12511411/hbase-jruby_home-and-jruby_opts.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
-1 patch. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/828//console
This message is automatically generated.
> HBase shell uses system JRuby if JRUBY_HOME is set, respects 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: hbase-jruby_home-and-jruby_opts.patch
>
>
> 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
[jira] [Updated] (HBASE-5245) HBase shell should use alternate
jruby if JRUBY_HOME is set, should pass along JRUBY_OPTS
Posted by "Philip (flip) Kromer (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philip (flip) Kromer updated HBASE-5245:
----------------------------------------
Remaining Estimate: 0h
Original Estimate: 0h
Summary: HBase shell should use alternate jruby if JRUBY_HOME is set, should pass along JRUBY_OPTS (was: HBase shell uses system JRuby if JRUBY_HOME is set, respects JRUBY_OPTS)
> 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: 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
[jira] [Updated] (HBASE-5245) HBase shell uses system JRuby if
JRUBY_HOME is set, respects JRUBY_OPTS
Posted by "Philip (flip) Kromer (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philip (flip) Kromer updated HBASE-5245:
----------------------------------------
Attachment: hbase-jruby_home-and-jruby_opts.patch
Patch fixing HBASE-5245 (jruby_home and jruby_opts)
> HBase shell uses system JRuby if JRUBY_HOME is set, respects 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: hbase-jruby_home-and-jruby_opts.patch
>
>
> 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
[jira] [Updated] (HBASE-5245) HBase shell should use alternate
jruby if JRUBY_HOME is set, should pass along JRUBY_OPTS
Posted by "stack (Updated) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (HBASE-5245) HBase shell should use alternate
jruby if JRUBY_HOME is set, should pass along JRUBY_OPTS
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190884#comment-13190884 ]
Hudson commented on HBASE-5245:
-------------------------------
Integrated in HBase-TRUNK-security #85 (See [https://builds.apache.org/job/HBase-TRUNK-security/85/])
HBASE-5245 HBase shell should use alternate jruby if JRUBY_HOME is set, should pass along JRUBY_OPTS
stack :
Files :
* /hbase/trunk/bin/hbase
> 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
[jira] [Commented] (HBASE-5245) HBase shell should use alternate
jruby if JRUBY_HOME is set, should pass along JRUBY_OPTS
Posted by "stack (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190795#comment-13190795 ]
stack commented on HBASE-5245:
------------------------------
I tried apply to TRUNK and it fails. Mind fixing Philip? And I'm interested as to why you need this? Thanks.
> 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: 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
[jira] [Updated] (HBASE-5245) HBase shell uses system JRuby if
JRUBY_HOME is set, respects JRUBY_OPTS
Posted by "Philip (flip) Kromer (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philip (flip) Kromer updated HBASE-5245:
----------------------------------------
Affects Version/s: 0.90.4
Status: Patch Available (was: Open)
> HBase shell uses system JRuby if JRUBY_HOME is set, respects 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: hbase-jruby_home-and-jruby_opts.patch
>
>
> 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
[jira] [Commented] (HBASE-5245) HBase shell should use alternate
jruby if JRUBY_HOME is set, should pass along JRUBY_OPTS
Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190800#comment-13190800 ]
Hadoop QA commented on HBASE-5245:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12511450/5245-v2.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
-1 patch. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/834//console
This message is automatically generated.
> 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
[jira] [Commented] (HBASE-5245) HBase shell should use alternate
jruby if JRUBY_HOME is set, should pass along JRUBY_OPTS
Posted by "stack (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190797#comment-13190797 ]
stack commented on HBASE-5245:
------------------------------
Oh, nvm. I see you say why you need this above.
> 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: 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