[
https://issues.apache.org/jira/browse/HBASE-20108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated HBASE-20108:
-------------------------------
Release Note: This issue fixes a runtime dependency issues where JLine is
not made available on the classpath which causes the ZooKeeper CLI to appear
non-interactive. JLine was being made available unintentionally via the JRuby
jar file on the classpath for the HBase shell. While the JRuby jar is not
always present, the fix made here was to selectively include the JLine
dependency on the zkcli command's classpath.
Added RN.
Users on previously release can workaround this by doing something like the
following:
{code:java}
$ HBASE_CLASSPATH="${HBASE_CLASSPATH}:${ZOOKEEPER_HOME}/lib/jline-0.9.94.jar"
hbase zkcli{code}
> `hbase zkcli` falls into a non-interactive prompt after HBASE-15199
> -------------------------------------------------------------------
>
> Key: HBASE-20108
> URL: https://issues.apache.org/jira/browse/HBASE-20108
> Project: HBase
> Issue Type: Bug
> Components: Usability
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: HBASE-20108.001.branch-2.patch,
> HBASE-20108.002.branch-2.patch, HBASE-20108.003.branch-2.patch
>
>
> HBASE-15199 pulls the jruby-complete jar out of the normal classpath for
> commands run in HBase. Jruby-complete bundles jline inside. ZK uses jline for
> its nice shell-like usage.
> The problem is that this uncovered a bug where we're not explicitly bundling
> a version of jline to make sure that {{hbase zkcli}} actually works. As long
> as we're expecting {{zkcli}} to be there, we should provide jline on the
> classpath to make sure the users get a real cli.
> Thanks to [~sergey.soldatov] for getting to the bottom of it quickly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
