[jira] [Resolved] (HBASE-28698) Add hadoop 3.4.0 in hadoop check

[Duo Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-28698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duo Zhang resolved HBASE-28698.
---
Fix Version/s: 2.7.0
   3.0.0-beta-2
   2.6.1
   2.5.9
 Hadoop Flags: Reviewed
 Assignee: Duo Zhang
   Resolution: Fixed

Pushed to all active branches.

Thanks [~pankajkumar] for reviewing!

> Add hadoop 3.4.0 in hadoop check
> 
>
> Key: HBASE-28698
> URL: https://issues.apache.org/jira/browse/HBASE-28698
> Project: HBase
>  Issue Type: Task
>  Components: jenkins, scripts
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.9
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (HBASE-28714) Exclude org.bouncycastle:bcprov-jdk15on from hadoop

[Duo Zhang (Jira)]

Duo Zhang created HBASE-28714:
-

 Summary: Exclude org.bouncycastle:bcprov-jdk15on from hadoop
 Key: HBASE-28714
 URL: https://issues.apache.org/jira/browse/HBASE-28714
 Project: HBase
  Issue Type: Bug
  Components: dependencies, hadoop3
Reporter: Duo Zhang


In hadoop 3.4.0, hadoop common depends on org.bouncycastle:bcprov-jdk15on, 
where we an enforcer rule to force depending on org.bouncycastle:*-jdk18on.

We should exlude org.bouncycastle:bcprov-jdk15on from hadoop.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (HBASE-28715) Backup delete incorrectly handles bulk loaded entries

[Dieter De Paepe (Jira)]

Dieter De Paepe created HBASE-28715:
---

 Summary: Backup delete incorrectly handles bulk loaded entries
 Key: HBASE-28715
 URL: https://issues.apache.org/jira/browse/HBASE-28715
 Project: HBase
  Issue Type: Bug
  Components: backup&restore
Affects Versions: 2.6.0, 3.0.0, 4.0.0-alpha-1
Reporter: Dieter De Paepe


To delete a backup, `BackupAdminImpl#deleteBackup` calls 
`BackupSystemTable#deleteBulkLoadedRows` on all rows returned by 
`BackupSystemTable#readBulkLoadedFiles(backupId)`.

This last method comes down to a scan over the bulk load table for all rows 
matching "bulk:BACKUPID:".

However, current code never writes rows of that format. The only methods that 
do so are `BackupSystemTable#writeBulkLoadedFiles` and 
`BackupSystemTable#createPutForBulkLoadedFile`, which are only used in test 
code.

Note that the bulkload rows that do get written (see `BackupObserver`) only get 
deleted when creating incremental backups, but suffer from HBASE-28706.

Consequences: I suspect that if you do some bulk loads, create a full backup, 
and delete that backup before doing any incremental backup, those entries in 
the bulk load table will never get deleted, meaning those HFiles can never get 
deleted (because `BackupLogCleaner` blocks their deletion).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [DISCUSS] Move our official slack channel to the one in the-asf.slack.com

[Istvan Toth]

+1

On Sun, Jul 7, 2024 at 8:55 PM Pankaj Kumar  wrote:

> +1
>
> On Sun, Jul 7, 2024 at 9:24 PM Bryan Beaudreault 
> wrote:
>
> > +1 sounds good to me
> >
> > On Sun, Jul 7, 2024 at 11:07 AM Duo Zhang  wrote:
> >
> > > As I mentioned in another thread, now slack will hide the comments
> > > before 90 days in the current apache-hbase.slack.com, which is really
> > > not good for finding useful discussions.
> > >
> > > According to the documentation here
> > >
> > > https://infra.apache.org/slack.html
> > >
> > > We could invite people which do not have at apache dot org email
> > > address as a guest to the slack channel, so there is no concerns about
> > > only committers can join the channel.
> > >
> > > Thoughts?
> > >
> > > Thanks.
> > >
> >
>


-- 
*István Tóth* | Sr. Staff Software Engineer
*Email*: st...@cloudera.com
cloudera.com 
[image: Cloudera] 
[image: Cloudera on Twitter]  [image:
Cloudera on Facebook]  [image: Cloudera
on LinkedIn] 
--
--

[jira] [Created] (HBASE-28716) HBaseAdmin#getQuota() should not open a new connection

[Charles Connell (Jira)]

Charles Connell created HBASE-28716:
---

 Summary: HBaseAdmin#getQuota() should not open a new connection
 Key: HBASE-28716
 URL: https://issues.apache.org/jira/browse/HBASE-28716
 Project: HBase
  Issue Type: Bug
  Components: Admin
Affects Versions: 2.6.0
Reporter: Charles Connell
Assignee: Charles Connell


Every call to HBaseAdmin#getQuota() opens a new Connection, and then closes it. 
As far as I can tell, this is pointless, since it could use the existing 
Connection object held by the HBaseAdmin. If you have a custom RpcClient (like 
we do at Hubspot), new connections have an expense that we'd rather not pay 
unnecessarily. I'll submit a PR.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (HBASE-28717) Support FuzzyRowFilter in REST interface

[Istvan Toth (Jira)]

Istvan Toth created HBASE-28717:
---

 Summary: Support FuzzyRowFilter in REST interface
 Key: HBASE-28717
 URL: https://issues.apache.org/jira/browse/HBASE-28717
 Project: HBase
  Issue Type: Improvement
  Components: REST
Reporter: Istvan Toth
Assignee: Istvan Toth


This is similar to MultiRowRangeFilter, but needs a new DTO to represent the 
keys with masks.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (HBASE-28718) Should support the license name 'Apache-2.0'

[Duo Zhang (Jira)]

Duo Zhang created HBASE-28718:
-

 Summary: Should support the license name 'Apache-2.0'
 Key: HBASE-28718
 URL: https://issues.apache.org/jira/browse/HBASE-28718
 Project: HBase
  Issue Type: Improvement
Reporter: Duo Zhang
Assignee: Duo Zhang


Starting from v29 of apache parent pom, the license name was changed from 
'Apache License, Version 2.0' to 'Apache-2.0'.

We should support it so we do not need to set lots of exceptions in 
supplemental-models.xml.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [DISCUSS] Move our official slack channel to the one in the-asf.slack.com

[Wei-Chiu Chuang]

+1

On Sun, Jul 7, 2024 at 8:07 AM Duo Zhang  wrote:

> As I mentioned in another thread, now slack will hide the comments
> before 90 days in the current apache-hbase.slack.com, which is really
> not good for finding useful discussions.
>
> According to the documentation here
>
> https://infra.apache.org/slack.html
>
> We could invite people which do not have at apache dot org email
> address as a guest to the slack channel, so there is no concerns about
> only committers can join the channel.
>
> Thoughts?
>
> Thanks.
>

Re: [DISCUSS] Move our official slack channel to the one in the-asf.slack.com

[Clay B.]

(Nonbinding) +1!
 Original message From: Wei-Chiu Chuang  
Date: 7/8/24  11:44 AM  (GMT-07:00) To: dev@hbase.apache.org Cc: hbase-user 
 Subject: Re: [DISCUSS] Move our official slack channel 
to the one in the-asf.slack.com +1On Sun, Jul 7, 2024 at 8:07 AM Duo Zhang 
 wrote:> As I mentioned in another thread, now slack will 
hide the comments> before 90 days in the current apache-hbase.slack.com, which 
is really> not good for finding useful discussions.>> According to the 
documentation here>> https://infra.apache.org/slack.html>> We could invite 
people which do not have at apache dot org email> address as a guest to the 
slack channel, so there is no concerns about> only committers can join the 
channel.>> Thoughts?>> Thanks.>

[VOTE] The first release candidate for 2.5.9 (RC0) is available

[Andrew Purtell]

Please vote on this Apache HBase release candidate, HBase 2.5.9 RC0.

The VOTE will remain open for at least 72 hours.

[ ] +1 Release this package as Apache HBase 2.5.9
[ ] -1 Do not release this package because ...

The tag to be voted on is 2.5.9RC0:

  https://github.com/apache/hbase/tree/2.5.9RC0

This tag currently points to git reference

  2b4959069b9285e0a6a1075a88d9f0d4a315ea56

The release files, including signatures, digests, as well as CHANGES.md
and RELEASENOTES.md included in this RC can be found at:

  https://dist.apache.org/repos/dist/dev/hbase/2.5.9RC0/

The API compatibility report comparing this RC to the previous release
can be found at:


https://dist.apache.org/repos/dist/dev/hbase/2.5.9RC0/api_compare_2.5.8_to_2.5.9RC0.html

There are no binary or source compatibility problems.

Maven artifacts are available in a staging repository at:

  https://repository.apache.org/content/repositories/orgapachehbase-1548/

Maven artifacts for hadoop3 are available in a staging repository at:

  https://repository.apache.org/content/repositories/orgapachehbase-1549/

Artifacts were signed with the 0xD5365CCD key which can be found in:

  https://downloads.apache.org/hbase/KEYS

To learn more about Apache hbase, please see

  http://hbase.apache.org/

Thanks,
Your HBase Release Manager