[
https://issues.apache.org/jira/browse/HBASE-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899135#action_12899135
]
Aditya Acharya commented on HBASE-2921:
---------------------------------------
Yeah, good observation. It looks like lib/ruby/1.x/irb/init.rb has this line:
@CONF[:PROMPT_MODE] = (STDIN.tty? ? :DEFAULT : :NULL)
which is the source of this issue. I'll investigate using a pty with
subprocess for my use case.
> HBase shell prompt is not configured when used as a subprocess
> --------------------------------------------------------------
>
> Key: HBASE-2921
> URL: https://issues.apache.org/jira/browse/HBASE-2921
> Project: HBase
> Issue Type: Bug
> Components: shell
> Affects Versions: 0.89.20100621
> Reporter: Aditya Acharya
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> When you start the HBase shell from bash, you see the following prompt:
> hbase(main):001:0>
> And typing in "conf" as the command yields the following prompt-related
> information:
> conf.prompt_c="%N(%m):%03n:%i* "
> conf.prompt_i="%N(%m):%03n:%i> "
> conf.prompt_mode=:DEFAULT
> conf.prompt_n="%N(%m):%03n:%i> "
> conf.prompt_s="%N(%m):%03n:%i%l "
> On the other hand, opening the HBase shell as python subprocess yields an
> empty string as the prompt string. Furthermore, sending it the "conf" command
> through a pipe yields the following output:
> conf.prompt_c=nil
> conf.prompt_i=nil
> conf.prompt_mode=:NULL
> conf.prompt_n=nil
> conf.prompt_s=nil
> I think this is a bug in the HBase shell. I'm not sure where it occurs, but I
> have found that it can be easily patched up by hard-coding the prompt
> information into bin/hirb.rb. This seems like the most appropriate fix, as
> bin/hirb.rb already modifies the conf for the interpreter.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
