[
https://issues.apache.org/jira/browse/HBASE-25345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack resolved HBASE-25345.
---
Fix Version/s: 2.3.4
2.2.7
Resolution: Fixed
Reresolving after
[
https://issues.apache.org/jira/browse/HBASE-25345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack reopened HBASE-25345:
---
Reopen to bring back to 2.3 and 2.2... looks like needed there too.
> [Flakey Tests] branch-2
On Mon, Nov 30, 2020 at 9:30 PM mallik.v.ar...@gmail.com <
mallik.v.ar...@gmail.com> wrote:
> Inline
>
> On Tue, Dec 1, 2020, 10:10 AM Andrew Purtell
> wrote:
>
> > We are allowed to debate if this should be in the tree or not. Given the
> > lack of interest, as evidenced by incomplete state,
Inline
On Tue, Dec 1, 2020, 10:10 AM Andrew Purtell
wrote:
> We are allowed to debate if this should be in the tree or not. Given the
> lack of interest, as evidenced by incomplete state, lack of release, and
> lack of contribution, it is more than fair to discuss removal.
>
> Here is my take:
Inline
On Mon, Nov 30, 2020, 9:56 PM Andrew Purtell
wrote:
> If we have unmaintained and unreleased, and unreleasable, code sitting in
> the tree it should be moved out or deleted.
>
> > We could use replication to backup the WALs, and use Snapshot and
> ExportSnapshot to backup the HFiles.
>
>
[
https://issues.apache.org/jira/browse/HBASE-25345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack resolved HBASE-25345.
---
Fix Version/s: 3.0.0-alpha-1
Hadoop Flags: Reviewed
Assignee: Michael Stack
We are allowed to debate if this should be in the tree or not. Given the lack
of interest, as evidenced by incomplete state, lack of release, and lack of
contribution, it is more than fair to discuss removal.
Here is my take: First of all, it is not released. There is no implied roadmap
or
Unless there is an objection to the plan I described below, it will happen
tomorrow on branch-2 in prep for RC.
> On Nov 30, 2020, at 4:46 PM, Andrew Purtell wrote:
>
>
> I'm glad I checked email before beginning the RC.
>
> How about this:
>
> CHANGES.md file that ships in 2.4.0 will
On Mon, Nov 30, 2020 at 9:59 PM Stack wrote:
> On Mon, Nov 30, 2020 at 5:55 AM mallik.v.ar...@gmail.com <
> mallik.v.ar...@gmail.com> wrote:
>
> > Inline.
> >
> > On Sun, Nov 29, 2020, 9:18 AM 张铎(Duo Zhang)
> wrote:
> >
> > > I'm afraid it is not easy to be moved to hbase-operator-tools.
> > >
I'm glad I checked email before beginning the RC.
How about this:
CHANGES.md file that ships in 2.4.0 will contain URLs pointing to older
CHANGES.md for 1.0.0, 2.0.0, 2.1.0, 2.2.0, 2.3.0.
CHANGES.md file that ships with 2.4.0 will list all issues completed for
2.4.0
CHANGES.md file that ships
[
https://issues.apache.org/jira/browse/HBASE-25344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wei-Chiu Chuang resolved HBASE-25344.
-
Resolution: Duplicate
> Detector
>
>
> Key: HBASE-25344
>
Michael Stack created HBASE-25345:
-
Summary: [Flakey Tests] branch-2
TestReadReplicas#testVerifySecondaryAbilityToReadWithOnFiles
Key: HBASE-25345
URL: https://issues.apache.org/jira/browse/HBASE-25345
On Mon, Nov 30, 2020 at 12:34 PM Nick Dimiduk wrote:
> So concretely, the conclusion here is that the CHANGES.md file that ships
> in 2.4.0 should contain entries for 2.0.0, 2.1.0, 2.2.0, 2.3.0, and 2.4.0?
> The CHANGES.md file that ships in 2.4.1 will contain all of the above, plus
> entries
junwen yang created HBASE-25344:
---
Summary: Protobuf Mesage Incompatibility Detector
Key: HBASE-25344
URL: https://issues.apache.org/jira/browse/HBASE-25344
Project: HBase
Issue Type: Bug
So concretely, the conclusion here is that the CHANGES.md file that ships
in 2.4.0 should contain entries for 2.0.0, 2.1.0, 2.2.0, 2.3.0, and 2.4.0?
The CHANGES.md file that ships in 2.4.1 will contain all of the above, plus
entries for 2.4.1.
Are you sure that's what you want? That seems like
Huaxiang Sun created HBASE-25343:
Summary: Add HA support on top of Load Balance mode
Key: HBASE-25343
URL: https://issues.apache.org/jira/browse/HBASE-25343
Project: HBase
Issue Type:
Nice discussion here.
For my part, I am +1 for our community to define our meaning around this
aspect of metadata.
However, I don't like using both "signed-off-by" and "reviewed-by" as a
manual annotation on the part of the committer, because we as a community
don't care about the distinction
[
https://issues.apache.org/jira/browse/HBASE-25127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack reopened HBASE-25127:
---
Reopening. Reverted from branch-2 since it fails compile.
Mind fixing [~clarax98007]
Let me
[
https://issues.apache.org/jira/browse/HBASE-25127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack resolved HBASE-25127.
---
Hadoop Flags: Reviewed
Resolution: Fixed
Merged to master and branch-2.
> Enhance
On Mon, Nov 30, 2020 at 5:55 AM mallik.v.ar...@gmail.com <
mallik.v.ar...@gmail.com> wrote:
> Inline.
>
> On Sun, Nov 29, 2020, 9:18 AM 张铎(Duo Zhang) wrote:
>
> > I'm afraid it is not easy to be moved to hbase-operator-tools.
> >
> > You can see the code under the
If we have unmaintained and unreleased, and unreleasable, code sitting in the
tree it should be moved out or deleted.
> We could use replication to backup the WALs, and use Snapshot and
> ExportSnapshot to backup the HFiles.
This is essentially how we have implemented backup at the $dayjob.
[
https://issues.apache.org/jira/browse/HBASE-25331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wellington Chevreuil resolved HBASE-25331.
--
Resolution: Fixed
Thanks for reviewing it, [~psomogyi]!
> [HBOSS]
[
https://issues.apache.org/jira/browse/HBASE-24230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Balazs Meszaros resolved HBASE-24230.
-
Fix Version/s: connector-1.0.1
Resolution: Fixed
> Support user-defined version
mallik.v.ar...@gmail.com 于2020年11月30日周一 下午9:55写道：
> Inline.
>
> On Sun, Nov 29, 2020, 9:18 AM 张铎(Duo Zhang) wrote:
>
> > I'm afraid it is not easy to be moved to hbase-operator-tools.
> >
> > You can see the code under the org.apache.hadoop.hbase.backup.master
> > package, we need to set up log
[
https://issues.apache.org/jira/browse/HBASE-23592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Balazs Meszaros resolved HBASE-23592.
-
Fix Version/s: connector-1.0.1
Resolution: Fixed
> Refactor tests in
Duo Zhang created HBASE-25342:
-
Summary: Upgrade error prone to 2.4.0
Key: HBASE-25342
URL: https://issues.apache.org/jira/browse/HBASE-25342
Project: HBase
Issue Type: Task
Inline.
On Sun, Nov 29, 2020, 9:18 AM 张铎(Duo Zhang) wrote:
> I'm afraid it is not easy to be moved to hbase-operator-tools.
>
> You can see the code under the org.apache.hadoop.hbase.backup.master
> package, we need to set up log cleaner at master side, and also,
> the
[
https://issues.apache.org/jira/browse/HBASE-25236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Balazs Meszaros resolved HBASE-25236.
-
Fix Version/s: connector-1.0.1
Resolution: Fixed
> [hbase-connectors] Run
[
https://issues.apache.org/jira/browse/HBASE-25339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani resolved HBASE-25339.
--
Fix Version/s: 2.3.4
2.2.7
2.4.0
Hadoop Flags:
[
https://issues.apache.org/jira/browse/HBASE-25341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-25341.
---
Hadoop Flags: Reviewed
Resolution: Fixed
Pushed to master and branch-2.
Thanks [~zghao] for
30 matches
Mail list logo
