Oh right, also branch-1 currently has HBASE-19858. so we might be a
bit from a 1.5 release.
On Tue, Apr 3, 2018 at 7:25 PM, Sean Busbey <bus...@apache.org> wrote:
> I dunno. I'd defer to others on the release suitability of branch-1
> code. I look at nightly and all I see is red.
>
>
>
> On Tue, Apr 3, 2018 at 2:27 PM, Apekshit Sharma <a...@cloudera.com> wrote:
>> +1 on going back to old behavior, i.e. returning values, in branch-1 and
>> 2.0 release.
>>
>> bq. Open question: should we also revert this change in branch-1.4, even
>> though
>> it means the shell will behave very differently between maintenance
>> releases?
>> Earlier, i was inclining towards reverting the behavior in next 1.4.x too,
>> but not so much now. Probably a sooner 1.5 is better idea?
>>
>> On Tue, Apr 3, 2018 at 6:50 AM, Sean Busbey <bus...@apache.org> wrote:
>>
>>> Hi folks!
>>>
>>> Wanted to bring your attention to HBASE-20276 "[shell] confirm shell
>>> REPL change and document".
>>>
>>> tl;dr: there's a change currently in 1.4.{0..3} and 2.0.0-* that makes
>>> us not return values from any shell commands. current consensus is
>>> that this fundamentally breaks the shell and we should revert it. At
>>> least one person (me) believes that we should not treat releases with
>>> this behavior as our stable / recommend release line.
>>>
>>> Patch shortly going in for branch-1 and newer that reverts the behavior.
>>>
>>> Open question: should we also revert this change in branch-1.4, even
>>> though it means the shell will behave very differently between
>>> maintenance releases?
>>>
>>
>>
>>
>> --
>>
>> -- Appy
