[jira] [Comment Edited] (HBASE-20276) [shell] Revert shell REPL change and document

["stack (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-20276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16445296#comment-16445296 ] 

stack edited comment on HBASE-20276 at 4/20/18 4:58 AM:
--------------------------------------------------------

Opening HBASE-20463 for branch-1 fix. Resolving this so it makes it into the RC1 of 2.0.0 release notes. Hope you don't mind lads ([~busbey] and [~apurtell])


was (Author: stack):
Opening subissue for branch-1 fix. Resolving this so it makes it into the RC1 of 2.0.0 release notes.

> [shell] Revert shell REPL change and document
> ---------------------------------------------
>
>                 Key: HBASE-20276
>                 URL: https://issues.apache.org/jira/browse/HBASE-20276
>             Project: HBase
>          Issue Type: Sub-task
>          Components: documentation, shell
>    Affects Versions: 1.4.0, 2.0.0
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Blocker
>             Fix For: 2.0.0
>
>         Attachments: HBASE-20276-branch-1.v4.patch, HBASE-20276.0.patch, HBASE-20276.1.patch, HBASE-20276.2.patch, HBASE-20276.3.patch
>
>
> Feedback from [~mdrob] on HBASE-19158:
> {quote}
> Shell:
> HBASE-19770. There was another issue opened where this was identified as a problem so maybe the shape will change further, but I can't find it now.
> {quote}
> New commentary from [~busbey]:
> This was a follow on to HBASE-15965. That change effectively makes it so none of our ruby wrappers can be used to build expressions in an interactive REPL. This is a pretty severe change (most of my tips on HBASE-15611 will break, I think).
> I think we should
> a) Have a DISCUSS thread, spanning dev@ and user@
> b) based on the outcome of that thread, either default to the new behavior or the old behavior
> c) if we keep the HBASE-15965 behavior as  the default, flag it as incompatible, call it out in the hbase 2.0 upgrade section, and update docs (two examples: the output in the shell_exercises sections would be wrong, and the _table_variables section won't work)
> d) In either case document the new flag in the ref guide



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)