[
https://issues.apache.org/jira/browse/HBASE-16196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15367934#comment-15367934
]
Sean Busbey commented on HBASE-16196:
-------------------------------------
{quote}
bq. we run in "Ruby 1.8" mode by default.
We've made no promises around the shell, that I know of. This would be an
operational compatibility change which is explicitly called out as only be on
patch releases.
{quote}
I'd be thrilled with getting to throw away Ruby 1.8 in branch-1, but I've held
off on it post-1.0 solely because the shell is practically the only means we
give folks to build tooling on top of us. We also expressly sell "build with
ruby scripts!" as a part of that, and going from Ruby 1.8 to 2.2 is several
breaking versions. Why wouldn't this fall under "Dependency Compatibility" (as
e.g. the JRE version does)?
> Update jruby to a newer version.
> --------------------------------
>
> Key: HBASE-16196
> URL: https://issues.apache.org/jira/browse/HBASE-16196
> Project: HBase
> Issue Type: Bug
> Components: dependencies, shell
> Reporter: Elliott Clark
> Assignee: Matt Mullins
> Attachments: 0001-Update-to-JRuby-9.1.2.0-and-JLine-2.12.patch,
> hbase-16196.branch-1.patch
>
>
> Ruby 1.8.7 is no longer maintained.
> The TTY library in the old jruby is bad. The newer one is less bad.
> Since this is only a dependency on the hbase-shell module and not on
> hbase-client or hbase-server this should be a pretty simple thing that
> doesn't have any backwards compat issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
