Zheng Wang created HBASE-24407:
--
Summary: Correct the comment of clusterRegionLocationMocks in
TestStochasticLoadBalancer
Key: HBASE-24407
URL: https://issues.apache.org/jira/browse/HBASE-24407
Project:
I like the idea of an old/ or eom/ prefix for old release lines.
I'm also fine with deleting old release lines.
For feature branches I think case by case unless the feature has merged.
Maybe a discuss for more complicated feature branches that are unlikely to
merge (0.89-fb hydrabase, etc). We
Set read-only for EOL branches? Similar to protected branch in gitlab.
Andrew Purtell 于2020年5月21日周四 上午9:23写道：
> What we do at $dayjob is rename old branches old/*.
> So we could rename EOL branches this way? E.g.
>
> for branch in branch-2.1 ... ; do
> git checkout $branch &&
> git
What we do at $dayjob is rename old branches old/*.
So we could rename EOL branches this way? E.g.
for branch in branch-2.1 ... ; do
git checkout $branch &&
git branch -m old/$branch &&
git push $origin old/$branch :$branch
done
On Wed, May 20, 2020 at 6:21 PM Nick Dimiduk wrote:
Why remove old/unused branches? To keep our garden tidy. They’re
distracting at best, confusing at worst. For old release line branches,
it’s not clear to a casual committer which branches need to receive a back
port. It’s clear if the EOL branches are gone.
On Wed, May 20, 2020 at 18:06 Guanghao
+1 for remove feature branches and start a case-by-case discussion for
"others".
And for branchs of old release line, what's the harm if keep them? I
thought we don't need to remove them.
Thanks.
张铎(Duo Zhang) 于2020年5月21日周四 上午8:14写道：
> What is the benefit?
>
> Nick Dimiduk 于2020年5月21日
What is the benefit?
Nick Dimiduk 于2020年5月21日 周四07:31写道：
> Heya,
>
> We have lots of branches hanging around in git. These appear to be
> 1. branches for old release lines (i.e., 0.90),
> 2. feature branches (that are potentially stale, i.e., HBASE-11288),
> 3. "other" (i.e., 0.89-fb,
Heya,
We have lots of branches hanging around in git. These appear to be
1. branches for old release lines (i.e., 0.90),
2. feature branches (that are potentially stale, i.e., HBASE-11288),
3. "other" (i.e., 0.89-fb, former_0.20, revert-1633-HBASE-24221).
Can we decide it's okay to delete some
we have not yet had consensus to delete old branches. you will see we still
have them going back quite a ways. please start a new DISCUSS thread if you
want to pursue it.
On Wed, May 20, 2020 at 2:39 PM Nick Dimiduk wrote:
> Can we delete the old branch as well?
>
> On Wed, May 20, 2020 at
Can we delete the old branch as well?
On Wed, May 20, 2020 at 07:57 Sean Busbey wrote:
> I updated the header. might take a bit for it to sync up.
>
> On Wed, May 20, 2020 at 9:55 AM Sean Busbey wrote:
>
> > hurm. looks like we missed some steps on cleaning up branch-2.1. the EOL
> > isn't
I updated the header. might take a bit for it to sync up.
On Wed, May 20, 2020 at 9:55 AM Sean Busbey wrote:
> hurm. looks like we missed some steps on cleaning up branch-2.1. the EOL
> isn't listed on our header for downloads.apache.org.
>
> we sent a notice to user@hbase in March when 2.1.10
[
https://issues.apache.org/jira/browse/HBASE-24063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-24063.
-
Resolution: Fixed
> Make branch-2.1 EOM
> ---
>
> Key:
[
https://issues.apache.org/jira/browse/HBASE-24406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-24406.
-
Resolution: Fixed
> add EOM date for 2.1.x to downloads.a.o header
>
[
https://issues.apache.org/jira/browse/HBASE-24063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey reopened HBASE-24063:
-
> Make branch-2.1 EOM
> ---
>
> Key: HBASE-24063
>
Sean Busbey created HBASE-24406:
---
Summary: add EOM date for 2.1.x to downloads.a.o header
Key: HBASE-24406
URL: https://issues.apache.org/jira/browse/HBASE-24406
Project: HBase
Issue Type:
hurm. looks like we missed some steps on cleaning up branch-2.1. the EOL
isn't listed on our header for downloads.apache.org.
we sent a notice to user@hbase in March when 2.1.10 was coming out:
https://s.apache.org/om9lb
On Wed, May 20, 2020 at 3:28 AM ramkrishna vasudevan <
The infra eam confirm that the machine is broken and offlined. It should be
fine now.
张铎(Duo Zhang) 于2020年5月18日周一 上午11:55写道：
> https://issues.apache.org/jira/browse/INFRA-20278
>
> 张铎(Duo Zhang) 于2020年5月18日周一 上午11:52写道：
>
>> Checked the two jobs you provide, all the failed taska are on H10.
>>
Invitation sent.
On Wed, May 20, 2020 at 1:17 PM Nand kishor Bansal
wrote:
> Hi,
>
> I would like to join slack channel for hbase. Can somebody please send me
> an invite.
>
> Thanks,
> Nand
>
Hi,
I would like to join slack channel for hbase. Can somebody please send me
an invite.
Thanks,
Nand
[
https://issues.apache.org/jira/browse/HBASE-24364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang resolved HBASE-24364.
Resolution: Fixed
> [Chaos Monkey] Invalid data block encoding in ChangeEncodingAction
>
Viraj Jasani created HBASE-24405:
Summary: Document hbase:slowlog in detail
Key: HBASE-24405
URL: https://issues.apache.org/jira/browse/HBASE-24405
Project: HBase
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/HBASE-24364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang reopened HBASE-24364:
[~meiyi] Need to push to branch-2, too.
> [Chaos Monkey] Invalid data block encoding in
[
https://issues.apache.org/jira/browse/HBASE-24399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang resolved HBASE-24399.
Resolution: Fixed
Pushed to branch-2.2, branch-2.3 and branch-2. Thanks [~Ddupg] for
Oh my bad. I did not realize that. Thanks for letting me know.
On Wed, May 20, 2020, 1:54 PM Peter Somogyi wrote:
> The branch-2.1 reached End of Life so the builds got disabled. The last
> release from branch-2.1 is 2.1.10.
>
> On Wed, May 20, 2020 at 9:48 AM ramkrishna vasudevan <
>
The branch-2.1 reached End of Life so the builds got disabled. The last
release from branch-2.1 is 2.1.10.
On Wed, May 20, 2020 at 9:48 AM ramkrishna vasudevan <
ramkrishna.s.vasude...@gmail.com> wrote:
> Hi All
>
> After we did some recent checkins for branch-2.1 and was waiting for the
>
[
https://issues.apache.org/jira/browse/HBASE-21996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Hentschel resolved HBASE-21996.
---
Resolution: Fixed
Going to close this again, as our pushed Javadoc looks as expected.
>
Hi All
After we did some recent checkins for branch-2.1 and was waiting for the
nightly builds observed that the builds have not been running for last 10
days.
https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/lastBuild/
Recently there was a compilation issue caused by HBASE-24186
Zheng Wang created HBASE-24404:
--
Summary: Support flush a single column family in shell mode
Key: HBASE-24404
URL: https://issues.apache.org/jira/browse/HBASE-24404
Project: HBase
Issue Type:
28 matches
Mail list logo
