No problem. I'll can keep up the 2.1 branch and squeeze some more releases
out of it.
Can do the branch-2.0 if we need one there too.
S
On Thu, May 16, 2019 at 8:13 PM 张铎(Duo Zhang) wrote:
> Usually at least we will keep two minor release lines? I could also take
> the release work of
Usually at least we will keep two minor release lines? I could also take
the release work of branch-2.1, until 2.3.0 is out.
Allan Yang 于2019年5月17日周五 上午10:45写道：
> Why so soon... branch-2.2 is not stable yet. branch-2.1 is the only stable
> branch in 2.x since branch-2.0 is already EOL’d.
> Best
Why so soon... branch-2.2 is not stable yet. branch-2.1 is the only stable
branch in 2.x since branch-2.0 is already EOL’d.
Best Regards
Allan Yang
张铎(Duo Zhang) 于2019年5月17日周五 上午10:23写道：
> The next RC for 2.2.0 will be available soon...
>
> Sean Busbey 于2019年5月17日周五 上午10:13写道：
>
> > Too early
The next RC for 2.2.0 will be available soon...
Sean Busbey 于2019年5月17日周五 上午10:13写道：
> Too early to EOL 2.1.
>
> Also we didn't EOL 2.0 at 2.0.5 because folks wanted a post 2.2.0 release.
>
> On Thu, May 16, 2019, 18:26 Zach York
> wrote:
>
> > I like the proactive approach to EOLing branches,
Duo Zhang created HBASE-22438:
-
Summary: Backport 'HBASE-20970 Update hadoop check versions for
hadoop3 in hbase-personality' to branch-2.1/branch-2.0
Key: HBASE-22438
URL:
Too early to EOL 2.1.
Also we didn't EOL 2.0 at 2.0.5 because folks wanted a post 2.2.0 release.
On Thu, May 16, 2019, 18:26 Zach York wrote:
> I like the proactive approach to EOLing branches, but I don't think we can
> quite EOL a branch when there is no newer branch (2.2.0) out. If that's
>
[
https://issues.apache.org/jira/browse/HBASE-22420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang resolved HBASE-22420.
Resolution: Duplicate
Duplicate with HBASE-22424
> TestRSGroupsBalacne.testGroupBalance
[
https://issues.apache.org/jira/browse/HBASE-22404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang resolved HBASE-22404.
Resolution: Fixed
> Open/Close region request may be executed twice when master restart
>
[
https://issues.apache.org/jira/browse/HBASE-22429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell resolved HBASE-22429.
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 1.3.5
Sean Mackrory created HBASE-22437:
-
Summary: HBOSS: Add Hadoop 2 / 3 profiles
Key: HBASE-22437
URL: https://issues.apache.org/jira/browse/HBASE-22437
Project: HBase
Issue Type: Improvement
I like the proactive approach to EOLing branches, but I don't think we can
quite EOL a branch when there is no newer branch (2.2.0) out. If that's
2.1.6, that's fine.
On Thu, May 16, 2019 at 3:18 PM Stack wrote:
> Was going to put up an RC for 2.1.5 in next day or so after a review of
>
Was going to put up an RC for 2.1.5 in next day or so after a review of
unresolved JIRAs that have 2.1.5 as fix version. It is coming up on two
months since 2.1.4 and by the time we're done, there'll be 90+ changes.
Branch-2.1 nightlies have started to stabilize again.
Was also thinking of
Thank you. Will use them.
On Thu, May 16, 2019 at 2:07 PM Josh Elser wrote:
> Sorry, not "hbase-filesystem" but "Filesystem Integration"
>
> On 5/16/19 2:04 PM, Josh Elser wrote:
> > Thanks, Biju.
> >
> > I've created "Quotas" and "Scheduler" components. There is also an
> > "hbase-filesystem"
Sorry, not "hbase-filesystem" but "Filesystem Integration"
On 5/16/19 2:04 PM, Josh Elser wrote:
Thanks, Biju.
I've created "Quotas" and "Scheduler" components. There is also an
"hbase-filesystem" component which can be used for the HBOSS project
(saw you added a label for that this
Thanks, Biju.
I've created "Quotas" and "Scheduler" components. There is also an
"hbase-filesystem" component which can be used for the HBOSS project
(saw you added a label for that this morning).
We'll probably have to beg, but hopefully folks can self-police and use
components a bit more
Hi Josh,
JIRA items related to "quota" is the one which I was going through
recently which was not in the component list. It would help if all
supported quota features gets added to the component list.
The next one which is good to add is "scheduler". To give some context
why this will help
[
https://issues.apache.org/jira/browse/HBASE-22436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-22436.
---
Resolution: Duplicate
Oh, the github PR has already modified AsyncAdmin... Resolved as duplicated.
Duo Zhang created HBASE-22436:
-
Summary: Implement listNamespaces method for AsyncAdmin
Key: HBASE-22436
URL: https://issues.apache.org/jira/browse/HBASE-22436
Project: HBase
Issue Type:
[
https://issues.apache.org/jira/browse/HBASE-22416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved HBASE-22416.
Resolution: Fixed
Hadoop Flags: Reviewed
Thanks for the review, Sean!
> HBOSS: unit tests
Biju -- we have the ability to define components.
It sounds like the consensus is that folks prefer components over
free-form labels.
What are the components that you hoped to find that aren't there?
On 5/13/19 6:31 PM, Biju N wrote:
FYI. There are instances where we don't have "components"
20 matches
Mail list logo
