[ https://issues.apache.org/jira/browse/HBASE-20276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16424068#comment-16424068 ]
Sean Busbey commented on HBASE-20276: ------------------------------------- [I put up a DISCUSS thread pointing folks over here|https://lists.apache.org/thread.html/23cf8f132b0b87d34f14c5c7dee2a8458ce89af69e3bf0e9fda9e61a@%3Cdev.hbase.apache.org%3E]. I think we already have enough consensus to get a patch up for 1.5+ I'm happy to either get the patch together or review. I'll do the former after I wrap up some other stuff, or the latter if someone else has time to do it sooner. FWIW, I think we should keep the --return-values flag because it's been in a release. we should just have it print a message about how the change to not return values has been removed. > [shell] confirm 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 > Priority: Blocker > Fix For: 1.4.4, 2.0.0 > > > 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)