hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-20276) [shell] Revert shell REPL change and document
Date Thu, 05 Apr 2018 19:15:00 GMT

     [ https://issues.apache.org/jira/browse/HBASE-20276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Sean Busbey updated HBASE-20276:
    Status: In Progress  (was: Patch Available)

taking out of PA. on second thought I'd rather not alter so much of table.rb

> [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: 1.4.4, 2.0.0
>         Attachments: HBASE-20276.0.patch, HBASE-20276.1.patch, HBASE-20276.2.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
> 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

View raw message