Re: [DISCUSS] changes in shell behavior wrt returning values

FYI, HBASE-20276 has now been committed to all impacted branches. If folks have a chance to review the proposed release note, that'd be grand. On Fri, Apr 6, 2018 at 2:55 PM, Josh Elser wrote: > +1 ditto -- this one is better to revert and ask forgiveness on from users, >

Re: [DISCUSS] changes in shell behavior wrt returning values

lgtm. On Fri, Apr 6, 2018 at 1:24 PM, Sean Busbey wrote: > FYI, HBASE-20276 has now been committed to all impacted branches. > > If folks have a chance to review the proposed release note, that'd be > grand. > > On Fri, Apr 6, 2018 at 2:55 PM, Josh Elser

Re: [DISCUSS] Minimum Maven Version

No complaints requiring 3.0.5 instead of 3.0.4 (pretty ancient versions at this point). A table tracking minVers would be nice as Sean says. On 4/3/18 9:55 AM, Sean Busbey wrote: a table listing would be nice, if we end up using different versions of maven on different release lines.

Re: [DISCUSS] changes in shell behavior wrt returning values

+1 ditto -- this one is better to revert and ask forgiveness on from users, IMO. On 4/3/18 3:27 PM, Apekshit Sharma 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

Re: A quick note about next branch-1.4 release

Since that will be the first 1.4 release with HBASE-20276, is anyone opposed to making 1.4.4 the cut off point for the stable pointer moving to branch-1.4? (presuming we don't find some late breaking blocker during RCs or something.) On Fri, Apr 6, 2018 at 1:11 PM, Andrew Purtell

Re: A quick note about next branch-1.4 release

Although HBASE-20322 is rare this is additional motivation, so it's settled... a release this month, then the scheduled on at the end of Q2. On Fri, Apr 6, 2018 at 1:45 PM, Andrew Purtell wrote: > I can do a release this month for HBASE-20276. Anything else in the should >

Re: A quick note about next branch-1.4 release

I can do a release this month for HBASE-20276. Anything else in the should get out there now bucket? On Fri, Apr 6, 2018 at 1:27 PM, Sean Busbey wrote: > Since that will be the first 1.4 release with HBASE-20276, is anyone > opposed to making 1.4.4 the cut off point for the

Re: [DISCUSS] changing our project mission statement

On 4/3/18 10:38 AM, Sean Busbey wrote: Over in HBASE-15317 ("document release announcement template ") I had proposed a brief description of our project that sought to update things to avoid talking about other projects. at the time (a little over two years ago), stack mentioned that he liked

[jira] [Resolved] (HBASE-20351) Shell dumps netty properties on startup

[ https://issues.apache.org/jira/browse/HBASE-20351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-20351. --- Resolution: Invalid Thanks [~mdrob] Yes, I had an old log4j in place. Removing it got rid of this dumping

A quick note about next branch-1.4 release

Unless there are critical bugs found, the next branch-1.4 release, 1.4.4 will happen at the end of Q2 2018, toward the end of June. -- Best regards, Andrew

[jira] [Resolved] (HBASE-20203) [AMv2] CODE-BUG: Uncaught runtime exception for pid=...., state=SUCCESS; AssignProcedure

[ https://issues.apache.org/jira/browse/HBASE-20203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-20203. --- Resolution: Cannot Reproduce Resovling as 'cannot reproduce'. Have not seen it in a good while. Will open

[jira] [Reopened] (HBASE-14729) SplitLogManager does not clean files from WALs folder in case of master failover

[ https://issues.apache.org/jira/browse/HBASE-14729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell reopened HBASE-14729: > SplitLogManager does not clean files from WALs folder in case of master > failover >

[jira] [Created] (HBASE-20359) why Comparator extends comparable?

Nick.han created HBASE-20359: Summary: why Comparator extends comparable? Key: HBASE-20359 URL: https://issues.apache.org/jira/browse/HBASE-20359 Project: HBase Issue Type: Improvement

[jira] [Created] (HBASE-20357) AccessControlClient API Enhancement

Pankaj Kumar created HBASE-20357: Summary: AccessControlClient API Enhancement Key: HBASE-20357 URL: https://issues.apache.org/jira/browse/HBASE-20357 Project: HBase Issue Type: Improvement

[jira] [Created] (HBASE-20358) Fix bin/hbase thrift usage text

Balazs Meszaros created HBASE-20358: --- Summary: Fix bin/hbase thrift usage text Key: HBASE-20358 URL: https://issues.apache.org/jira/browse/HBASE-20358 Project: HBase Issue Type: Bug

[jira] [Resolved] (HBASE-20353) REST server startup fails

[ https://issues.apache.org/jira/browse/HBASE-20353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Somogyi resolved HBASE-20353. --- Resolution: Duplicate Duplicate of HBASE-20007 > REST server startup fails >

[jira] [Resolved] (HBASE-14175) Adopt releasedocmaker for better generated release notes

[ https://issues.apache.org/jira/browse/HBASE-14175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-14175. --- Resolution: Fixed Assignee: stack Release Note: We will use yetus releasedocmaker to make our