[jira] [Resolved] (HBASE-28605) Add ErrorProne ban on Hadoop shaded thirdparty jars

[ https://issues.apache.org/jira/browse/HBASE-28605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk resolved HBASE-28605. -- Fix Version/s: 2.7.0 3.0.0-beta-2 2.6.1

[jira] [Created] (HBASE-28605) Add ErrorProne ban on Hadoop shaded thirdparty jars

Nick Dimiduk created HBASE-28605: Summary: Add ErrorProne ban on Hadoop shaded thirdparty jars Key: HBASE-28605 URL: https://issues.apache.org/jira/browse/HBASE-28605 Project: HBase Issue

[jira] [Created] (HBASE-28602) Incremental backup fails when WALs move

Nick Dimiduk created HBASE-28602: Summary: Incremental backup fails when WALs move Key: HBASE-28602 URL: https://issues.apache.org/jira/browse/HBASE-28602 Project: HBase Issue Type: Bug

[jira] [Created] (HBASE-28601) Enable setting memcache on-heap sizes in bytes

Nick Dimiduk created HBASE-28601: Summary: Enable setting memcache on-heap sizes in bytes Key: HBASE-28601 URL: https://issues.apache.org/jira/browse/HBASE-28601 Project: HBase Issue Type

[jira] [Created] (HBASE-28600) Enable setting blockcache on-heap sizes in bytes

Nick Dimiduk created HBASE-28600: Summary: Enable setting blockcache on-heap sizes in bytes Key: HBASE-28600 URL: https://issues.apache.org/jira/browse/HBASE-28600 Project: HBase Issue Type

[jira] [Created] (HBASE-28593) Update "Releasing Apache HBase" section in the book to document `do-release.sh`

Nick Dimiduk created HBASE-28593: Summary: Update "Releasing Apache HBase" section in the book to document `do-release.sh` Key: HBASE-28593 URL: https://issues.apache.org/jira/browse/H

[jira] [Created] (HBASE-28594) Add a new "Promoting Release Candidate"

Nick Dimiduk created HBASE-28594: Summary: Add a new "Promoting Release Candidate" Key: HBASE-28594 URL: https://issues.apache.org/jira/browse/HBASE-28594 Project: HBase Issue

Re: [VOTE] The third release candidate for 2.6.0, RC4, is available

+1 (binding) * Signature: ok * Checksum : ok * Rat check (1.8.0_412): ok - mvn clean apache-rat:check * Built from source (1.8.0_412): ok - mvn clean install -DskipTests * Built from source (11.0.23): ok - mvn clean install -D hadoop.profile=3.0 -DskipTests * Built from source (17.0.11): ok

Re: [VOTE] The third release candidate for 2.6.0, RC4, is available

The new backups system is one of the "flagship" features for the 2.6 release line so it's a shame that these issues with incremental manifest tracking remain. If I'm not mistaken, though, a full backup still works as expected, so these bugs do not prevent taking a backup entirely. I agree that

[jira] [Created] (HBASE-28573) Update compatibility report generator to ignore o.a.h.hbase.shaded packages

Nick Dimiduk created HBASE-28573: Summary: Update compatibility report generator to ignore o.a.h.hbase.shaded packages Key: HBASE-28573 URL: https://issues.apache.org/jira/browse/HBASE-28573 Project

Re: [DISCUSS] Dropping Java 8 support in HBase 3

I’m a fan of moving forward and accelerating our cadence of adoption, if that’s possible. Much of our performance-critical code relies on features deprecated after JDK8. We need to see if those use-cases are adequately supported by JDK17 or some later version. For the curious, we hide those use

[jira] [Created] (HBASE-28439) Remove ZooKeeper as a means of creating a client connection

Nick Dimiduk created HBASE-28439: Summary: Remove ZooKeeper as a means of creating a client connection Key: HBASE-28439 URL: https://issues.apache.org/jira/browse/HBASE-28439 Project: HBase

Archiving old/invalid versions (was Re: Unreleased hbase-thirdparty-3.5.2)

0.0-alpha-1 * HBASE-26067 -- "Change the way on how we track store file list", released in 2.6.0 * HBASE-26233 -- "The region replication framework should not be built upon the general replication framework", released in 3.0.0-alpha-1 I have deleted the following unreleased Jira v

Re: Unreleased hbase-thirdparty-3.5.2

Sounds right to me. > > > > On Fri, Feb 16, 2024 at 7:40 AM Nick Dimiduk > wrote: > > > > > Heya team, > > > > > > I noticed that we still have thirdparty-3.5.2 as an unreleased version > in > > > Jira. Looking at the release archiv

Re: [DISCUSS] Deprecating zookeeper-based client connectivity

R asap so it doesn’t block the release. I’m hoping to get the > RC0 out this week > > On Mon, Mar 4, 2024 at 4:41 AM Nick Dimiduk wrote: > > > On Fri, Mar 1, 2024 at 6:12 PM Andrew Purtell > wrote: > > > > > I disagree. We can keep the current defaults AND depreca

Re: [DISCUSS] Removing tests and/or Hadoop from the binary assemblies

This would be great cleanup, big +1 from me for all three of these adjustments, including the promotion of pe, ltt, and friends out of the test scope. I believe that we included hbase test jars because we used to freely mix classes needed for minicluster between runtime and test jars, which in

[jira] [Resolved] (HBASE-28379) Upgrade thirdparty dep to 4.1.6

[ https://issues.apache.org/jira/browse/HBASE-28379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk resolved HBASE-28379. -- Resolution: Fixed This is merged. FYI [~bbeaudreault]. > Upgrade thirdparty dep to 4.

Re: [DISCUSS] removing hbase-examples from the assembly

Should we remove hbase-examples from the main repository entirely? Should it be its own download? Should we even ship it in binary form at all? Anyway I’m fine with removing it from the assembly. Thanks, Nick On Mon, 4 Mar 2024 at 13:27, Istvan Toth wrote: > hbase assembly (and consequently

Re: [VOTE] The first release candidate for 2.5.8 (RC0) is available

+1 (binding) * Signature: ok * Checksum : ok * Rat check (1.8.0_392): ok - mvn clean apache-rat:check -D skipTests=true * Rat check (17.0.10): ok - mvn clean apache-rat:check -D hadoop.profile=3.0 -D skipTests=true * Built from source

[RESULT][VOTE] hbase-thirdparty 4.1.6 (RC0)

With 3 binding votes in the affirmative, 2 non-binding votes in the affirmative, and no dissenting votes cast, this motion passes. Thanks to everyone who took the time! Thanks, Nick On Mon, Mar 4, 2024 at 11:54 AM Nick Dimiduk wrote: > Here's my +1: > > * Sign

Re: [VOTE] hbase-thirdparty 4.1.6 (RC0)

runAllTests -Dsurefire.rerunFailingTestsCount=3 * Ran hbase branch-2.6 locally against the staged repo - ./bin/hbase master start - ./bin/hbase ltt -num_keys 500 -write 3:512 -read 100 -multiput On Tue, Feb 27, 2024 at 5:06 PM Nick Dimiduk wrote: > Please v

Re: [DISCUSS] Deprecating zookeeper-based client connectivity

ere is value in introducing the Deprecation warnings as early as possible, to give folks forewarning. So I suggest that we mark it deprecated in 2.6, it is no longer the default connection mechanism in 3.0, and it is removed in 4.0. On Fri, Mar 1, 2024 at 4:53 AM Nick Dimiduk wrote: > > > On Fri, M

Re: [DISCUSS] Deprecating zookeeper-based client connectivity

er. > > For me, I think a possible problem is that we expose the meta location > > in registry interface, since the splittable meta feature has been > > restarted, if later we support multiple meta regions in HBase, we will > > need extra works if we still want to keep the zk based

[jira] [Created] (HBASE-28414) create-release should spotless:apply after making any file changes

Nick Dimiduk created HBASE-28414: Summary: create-release should spotless:apply after making any file changes Key: HBASE-28414 URL: https://issues.apache.org/jira/browse/HBASE-28414 Project: HBase

Re: [DISCUSS] Deprecating zookeeper-based client connectivity

there’s nothing to motivate its complete removal, I guess there no reason to deprecate it. Thanks, Nick On Fri, Mar 1, 2024 at 12:15 AM Andrew Purtell wrote: > > > +1 for deprecating ZKConnectionRegistry beginning with/in 2.6.0. > > > > > > > > > > On

[jira] [Created] (HBASE-28413) Fix race condition in TestCleanerChore.retriesIOExceptionInStatus

Nick Dimiduk created HBASE-28413: Summary: Fix race condition in TestCleanerChore.retriesIOExceptionInStatus Key: HBASE-28413 URL: https://issues.apache.org/jira/browse/HBASE-28413 Project: HBase

[jira] [Resolved] (HBASE-28354) RegionSizeCalculator throws NPE when regions are in transition

[ https://issues.apache.org/jira/browse/HBASE-28354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk resolved HBASE-28354. -- Resolution: Fixed Committed to branches 2.5+. Thanks for the contribution [~aalhour

[jira] [Resolved] (HBASE-28342) Decommissioned hosts should be rejected by the HMaster

[ https://issues.apache.org/jira/browse/HBASE-28342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk resolved HBASE-28342. -- Resolution: Fixed > Decommissioned hosts should be rejected by the HMas

Re: [VOTE] hbase-thirdparty 4.1.6 (RC0)

For your reference, I have posted PRs vs. master [0] and branch-2.6 [1] that make use of this RC. [0]: https://github.com/apache/hbase/pull/5693 [1]: https://github.com/apache/hbase/pull/5710 On Tue, Feb 27, 2024 at 5:06 PM Nick Dimiduk wrote: > Please vote on this Apache hbase thirdpa

[DISCUSS] Deprecating zookeeper-based client connectivity

Heya, We have long had the ambition to get away from ZooKeeper as the means by which a client interfaces with an HBase cluster. The ConnectionRegistry was introduced in 2.0 as part of the asynchronous client implementation [0], then called the ClusterRegistry. The name changed and a new

[jira] [Reopened] (HBASE-28342) Decommissioned hosts should be rejected by the HMaster

[ https://issues.apache.org/jira/browse/HBASE-28342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk reopened HBASE-28342: -- Sorry, I missed something in review. Looking more closely at the other exceptions thrown, I

Re: [VOTE] hbase-thirdparty 4.1.6 (RC0)

to point out the absence of release notes for a given version, but I don't feel strongly about it. Anyway, I recall we discussed removing release notes and changes from the product artifacts but I don't have that thread handy. Thanks, Nick On Tue, 27 Feb 2024, 21:37 Nick Dimiduk, wrote: > >

[jira] [Created] (HBASE-28407) [thirdparty] Update release instructions

Nick Dimiduk created HBASE-28407: Summary: [thirdparty] Update release instructions Key: HBASE-28407 URL: https://issues.apache.org/jira/browse/HBASE-28407 Project: HBase Issue Type: Task

[VOTE] hbase-thirdparty 4.1.6 (RC0)

Please vote on this Apache hbase thirdparty release candidate, hbase-thirdparty-4.1.6RC0 The VOTE will remain open for at least 72 hours. [ ] +1 Release this package as Apache hbase thirdparty 4.1.6 [ ] -1 Do not release this package because ... The tag to be voted on is 4.1.6RC0:

[jira] [Resolved] (HBASE-28374) [hbase-thirdparty] bump deps for 4.1.6 release

[ https://issues.apache.org/jira/browse/HBASE-28374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk resolved HBASE-28374. -- Resolution: Fixed > [hbase-thirdparty] bump deps for 4.1.6 rele

[jira] [Created] (HBASE-28403) Improve debugging for failures in procedure tests

Nick Dimiduk created HBASE-28403: Summary: Improve debugging for failures in procedure tests Key: HBASE-28403 URL: https://issues.apache.org/jira/browse/HBASE-28403 Project: HBase Issue Type

Re: [DISCUSS] Enabling JDK17 build pipelines

+1 On Fri, Feb 23, 2024 at 4:34 AM 张铎(Duo Zhang) wrote: > Agree on Andrew's opinion. > > We could enable it for master and branch-3 first. > I will help with stablizing. > > Thanks. > > Andrew Purtell 于2024年2月23日周五 02:14写道： > > > > > Would like to gather opinion on which branches should we >

[jira] [Created] (HBASE-28387) Broken test TestHRegionWithInMemoryFlush

Nick Dimiduk created HBASE-28387: Summary: Broken test TestHRegionWithInMemoryFlush Key: HBASE-28387 URL: https://issues.apache.org/jira/browse/HBASE-28387 Project: HBase Issue Type: Task

[jira] [Created] (HBASE-28379) Upgrade thirdparty dep to 4.1.6

Nick Dimiduk created HBASE-28379: Summary: Upgrade thirdparty dep to 4.1.6 Key: HBASE-28379 URL: https://issues.apache.org/jira/browse/HBASE-28379 Project: HBase Issue Type: Task

[jira] [Resolved] (HBASE-28372) [hbase-thirdparty] Bump protobuf version to 3.25.2

[ https://issues.apache.org/jira/browse/HBASE-28372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk resolved HBASE-28372. -- Resolution: Duplicate > [hbase-thirdparty] Bump protobuf version to 3.2

[jira] [Resolved] (HBASE-28373) [hbase-thirdparty] upgrade Guava to 33.0.0-jre

[ https://issues.apache.org/jira/browse/HBASE-28373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk resolved HBASE-28373. -- Resolution: Duplicate > [hbase-thirdparty] upgrade Guava to 33.0.0-

Unreleased hbase-thirdparty-3.5.2

Heya team, I noticed that we still have thirdparty-3.5.2 as an unreleased version in Jira. Looking at the release archives [0], I don't see that release in our history -- it appears that the world has moved on. However, we have a couple tickets [1] assigned to this release. All 5 of these tickets

[jira] [Created] (HBASE-28374) [hbase-thirdparty] bump remaining deps for 4.1.6 release

Nick Dimiduk created HBASE-28374: Summary: [hbase-thirdparty] bump remaining deps for 4.1.6 release Key: HBASE-28374 URL: https://issues.apache.org/jira/browse/HBASE-28374 Project: HBase

[jira] [Resolved] (HBASE-28369) Add os-maven-plugin to hbase-thirdparty build

[ https://issues.apache.org/jira/browse/HBASE-28369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk resolved HBASE-28369. -- Resolution: Fixed > Add os-maven-plugin to hbase-thirdparty bu

[jira] [Created] (HBASE-28373) [hbase-thirdparty] upgrade Guava to 33.0.0-jre

Nick Dimiduk created HBASE-28373: Summary: [hbase-thirdparty] upgrade Guava to 33.0.0-jre Key: HBASE-28373 URL: https://issues.apache.org/jira/browse/HBASE-28373 Project: HBase Issue Type

[jira] [Created] (HBASE-28372) [third-party] Bump protobuf version to 3.25.2

Nick Dimiduk created HBASE-28372: Summary: [third-party] Bump protobuf version to 3.25.2 Key: HBASE-28372 URL: https://issues.apache.org/jira/browse/HBASE-28372 Project: HBase Issue Type

[jira] [Created] (HBASE-28369) Add os-maven-plugin to hbase-thirdparty build

Nick Dimiduk created HBASE-28369: Summary: Add os-maven-plugin to hbase-thirdparty build Key: HBASE-28369 URL: https://issues.apache.org/jira/browse/HBASE-28369 Project: HBase Issue Type

Releasing HBase Thirdparty (was Re: Quick update on 2.6.0)

. Thanks, Nick On Wed, Feb 14, 2024 at 1:36 PM Nick Dimiduk wrote: > I've never released from hbase-thirdparty but it looks > straightforward enough. Let me take it for a spin. > > Thanks, > Nick > > On Tue, Feb 13, 2024 at 5:56 PM Bryan Beaudreault > wrote: > >> Nett

Re: Quick update on 2.6.0

I've never released from hbase-thirdparty but it looks straightforward enough. Let me take it for a spin. Thanks, Nick On Tue, Feb 13, 2024 at 5:56 PM Bryan Beaudreault wrote: > Netty 4.1.107.Final has been released. I pushed > https://github.com/apache/hbase-thirdparty/pull/108 to upgrade.

Re: [DISCUSS] changing our notification settings

nk we could change the behavior to "link label", then we could > get the notification then. > > What do you guys think? Let's have a try? > > Thanks. > > Nick Dimiduk 于2024年1月25日周四 17:31写道： > > > > I reverted HBASE-28325 for now. > > > > On Thu,

Re: [DISCUSS] changing our notification settings

I reverted HBASE-28325 for now. On Thu, Jan 25, 2024 at 10:12 AM Nick Dimiduk wrote: > On Thu, Jan 25, 2024 at 3:51 AM 张铎(Duo Zhang) > wrote: > >> Was wondering if we could do something by our own, like jenkins job, >> use github api to scan all the PRs and change th

Re: [DISCUSS] changing our notification settings

port of your original intention > > if that were possible to have without the pre-commit noise. > > > > On Wed, Jan 24, 2024 at 12:55 PM Nick Dimiduk > wrote: > > > > > Hey team, > > > > > > I executed the below change in a unilateral manner that wa

[DISCUSS] changing our notification settings

initially desired? Or do folks here prefer the more verbose version that is enabled now? Thanks for your time, Nick On Tue, 23 Jan 2024 at 14:27, Nick Dimiduk wrote: > FYI, this was me via [0], [1]. It's not actually what I want... > > [0]: https://issues.apache.org/jira/browse/HBASE-2

Re: Handling of fixVersion for umbrella tasks

I’m late to the discussion, but you’ve concluded on what I believe is the correct approach. Another way to consider why this approach is correct is to think in terms of “git time” instead of chronological time. Consider the last common ancestor commit in the git histories. branch-2.6 was created

[jira] [Reopened] (HBASE-28325) Enable infra automation to comment on a Jira when a new PR is posted

[ https://issues.apache.org/jira/browse/HBASE-28325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk reopened HBASE-28325: -- I don't want a comment for every PR comment, only a comment when the PR is detected/linked

[jira] [Created] (HBASE-28325) Enable infra automation to comment on a Jira when a new PR is posted.

Nick Dimiduk created HBASE-28325: Summary: Enable infra automation to comment on a Jira when a new PR is posted. Key: HBASE-28325 URL: https://issues.apache.org/jira/browse/HBASE-28325 Project: HBase

[jira] [Reopened] (HBASE-27847) Introduce HBase image

[ https://issues.apache.org/jira/browse/HBASE-27847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk reopened HBASE-27847: -- > Introduce HBase image > - > > Key:

Re: [VOTE] The first release candidate for 2.5.7 (RC0) is available

+1 * Signature: ok * Checksum : ok * Rat check (17.0.9): ok - mvn clean apache-rat:check -D hadoop.profile=3.0 * Built from source (17.0.9): ok - mvn clean install -D hadoop.profile=3.0 -DskipTests * Unit tests pass (17.0.9): ok -

Re: Debugging slowness in Gets

tinue this journey and will report back with any issues and > will see if I can improve anything > > [1] < > https://github.com/stackabletech/docker-images/commit/ba957b37c8d4c679b918f3815e28d974b0bd008d > > > > On Wed, Dec 6, 2023 at 9:06 AM Nick Dimid

Re: Debugging slowness in Gets

For what it’s worth, we deployed async-profiler into the regionserver container image and it all worked as expected. But it’s not a sidecar container, it’s on the same image as the region server. If you can get the async profiler into your container image, installed where the RS can find it (as

Time for HBase Operator Tools release

Heya team, It’s been quite a while since we’ve had a release out of this repository. Can folks make some time for a new release, perhaps in the beginning of the new year? If you have fixes or improvements to land in hbck2, please post them. Thanks, Nick

[jira] [Created] (HBASE-28198) Fix broken link to replication documentation

Nick Dimiduk created HBASE-28198: Summary: Fix broken link to replication documentation Key: HBASE-28198 URL: https://issues.apache.org/jira/browse/HBASE-28198 Project: HBase Issue Type

[DISCUSS] Introduce HBase Connection URL

Heya, Over at my place of work, we've been adopting the RpcConnectionRegistry for specifying client connections. Currently we are looking at Replication, which doesn't support the feature and where assumptions about ZooKeeper abound. The details of a peer connection are fairly well encapsulated

Re: [DISCUSS] Introduce OWASP dependency-check-maven plugin?

Hi Duo, Generally, I think that this is a good idea. I have previously attempted to use the Jenkins OWASP stuff and found it was a non-trivial project to manage exclusions lists. We ended up abandoning the effort for lack of value-for-time reward. I think it's more important that we manage this

Re: [DISCUSS] releasing hbase-connector 1.1.0 ?

Thanks for making the release, Stephen. Folks, we need some more votes! On Fri, Oct 13, 2023 at 5:34 AM 张铎(Duo Zhang) wrote: > Just go ahead and make the release :) > > Tak Lon (Stephen) Wu 于2023年10月8日周日 01:48写道： > > > > we should have a new release.the last round I was asking and it was

Re: [VOTE] The first release candidate for hbase-connectors-1.0.1 (RC1) is available

+1 [WARNING] The requested profile "runAllTests" could not be activated because it does not exist. ~/tmp/hbase-connectors * Signature: ok * Checksum : ok * Rat check (11.0.21): ok - mvn clean apache-rat:check * Built from source (11.0.21): ok -

Re: [DISCUSS] Upgrade Zookeeper and Curator to latest version

This plan sounds good to me. >From the earlier message, we should be okay to upgrade branch-2.5 as well, though I wonder if we can ErrorProne the new API methods. Thanks, Nick On Thu, 19 Oct 2023 at 02:55, 张铎(Duo Zhang) wrote: > Filed https://issues.apache.org/jira/browse/HBASE-28153. > > If

Re: [VOTE] First release candidate for hbase-thirdparty 4.1.5 is available for download

+1 * Signature: ok * Checksum : ok * Rat check (1.8.0_382): ok - mvn clean apache-rat:check * Built from source (1.8.0_382): ok - mvn clean install -DskipTests * Unit tests pass (1.8.0_382): ok - mvn clean package hbase#5411

[jira] [Resolved] (HBASE-28068) Add hbase.normalizer.merge.merge_request_max_number_of_regions property to limit max number of regions in a merge request for merge normalization

[ https://issues.apache.org/jira/browse/HBASE-28068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk resolved HBASE-28068. -- Resolution: Fixed Addendums applied. >

[jira] [Reopened] (HBASE-28068) Add hbase.normalizer.merge.merge_request_max_number_of_regions property to limit max number of regions in a merge request for merge normalization

[ https://issues.apache.org/jira/browse/HBASE-28068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk reopened HBASE-28068: -- > Add hbase.normalizer.merge.merge_request_max_number_of_regions property to > limit max

[jira] [Resolved] (HBASE-28068) Add hbase.normalizer.merge.merge_request_max_number_of_regions property to limit max number of regions in a merge request for merge normalization

[ https://issues.apache.org/jira/browse/HBASE-28068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk resolved HBASE-28068. -- Resolution: Fixed > Add hbase.normalizer.merge.merge_request_max_number_of_regions prope

[jira] [Reopened] (HBASE-28068) Add hbase.normalizer.merge.merge_request_max_number_of_regions property to limit max number of regions in a merge request for merge normalization

[ https://issues.apache.org/jira/browse/HBASE-28068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk reopened HBASE-28068: -- Re-opening for branch-2.4 backport. >

Re: [ANNOUNCE] New HBase committer Hui Ruan(阮辉)

Congratulations Hui Ruan and thanks a lot for all your contributions ! On Fri, Sep 15, 2023 at 11:08 AM 张铎(Duo Zhang) wrote: > On behalf of the Apache HBase PMC, I am pleased to announce that Hui > Ruan(frostruan) > has accepted the PMC's invitation to become a committer on the > project. We

[jira] [Created] (HBASE-28077) Limit the maximum allocation when reading an HFileBlock

Nick Dimiduk created HBASE-28077: Summary: Limit the maximum allocation when reading an HFileBlock Key: HBASE-28077 URL: https://issues.apache.org/jira/browse/HBASE-28077 Project: HBase

[jira] [Resolved] (HBASE-27114) Upgrade scalatest maven plugin for thread-safety

[ https://issues.apache.org/jira/browse/HBASE-27114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk resolved HBASE-27114. -- Fix Version/s: hbase-connectors-1.0.1 Resolution: Fixed [~busbey] I think we need

[jira] [Created] (HBASE-28065) Corrupt HFile data is mishandled in several cases

Nick Dimiduk created HBASE-28065: Summary: Corrupt HFile data is mishandled in several cases Key: HBASE-28065 URL: https://issues.apache.org/jira/browse/HBASE-28065 Project: HBase Issue Type

Re: Access to Hbase Slack channel

Invitation sent. Thanks, Nick On Mon, 24 Jul 2023 at 12:02, Anwesha Banerjee wrote: > Hi Team, > I wish to begin my contribution to HBase as a developer. Request you to > kindly send me an invite to the Slack Channel > . > > Best Regards, > Anwesha Banerjee >

Re: Artifact signing via CI

Signing releases with Jenkins implies to me that we’re building releases with Jenkins, but perhaps that’s presumptuous. On Wed, 19 Jul 2023 at 16:18, 张铎(Duo Zhang) wrote: > +1 for releasing with jenkins job! > > Nick Dimiduk 于2023年7月19日周三 16:09写道： > > > > Heya, >

Artifact signing via CI

Heya, It has come to my attention that Infra is now willing to manage signing keys. This is a big step toward moving our release builds to CI, which would take a major burden off of our release managers. I thought that y’all might also be interested. Thanks, Nick

[jira] [Created] (HBASE-27946) Introduce HA hdfs+hbase colocated pod definition

Nick Dimiduk created HBASE-27946: Summary: Introduce HA hdfs+hbase colocated pod definition Key: HBASE-27946 URL: https://issues.apache.org/jira/browse/HBASE-27946 Project: HBase Issue Type

[jira] [Created] (HBASE-27945) Introduce hdfs+hbase colocated pod definition

Nick Dimiduk created HBASE-27945: Summary: Introduce hdfs+hbase colocated pod definition Key: HBASE-27945 URL: https://issues.apache.org/jira/browse/HBASE-27945 Project: HBase Issue Type

[jira] [Created] (HBASE-27943) Rework kuttl image as a yetus precommit base

Nick Dimiduk created HBASE-27943: Summary: Rework kuttl image as a yetus precommit base Key: HBASE-27943 URL: https://issues.apache.org/jira/browse/HBASE-27943 Project: HBase Issue Type: Sub

[jira] [Resolved] (HBASE-27935) Introduce Jenkins PR job for hbase-kustomize

[ https://issues.apache.org/jira/browse/HBASE-27935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk resolved HBASE-27935. -- Resolution: Fixed > Introduce Jenkins PR job for hbase-kustom

[jira] [Created] (HBASE-27935) Introduce Jenkins PR job for hbase-kustomize

Nick Dimiduk created HBASE-27935: Summary: Introduce Jenkins PR job for hbase-kustomize Key: HBASE-27935 URL: https://issues.apache.org/jira/browse/HBASE-27935 Project: HBase Issue Type

[DISCUSS] Release versioning scheme for new hbase-kustomize repo (was: Introduce new git repository for kustomize definitions)

repositories, by using "hbase-thirdparty-" as that repo's version prefix going forward.) What do you think? Thanks, Nick On Mon, Jun 12, 2023 at 7:18 PM Nick Dimiduk wrote: > I’ve created this repository. > > Unless there is an objection, I’ll push an initial commit with a LICE

[jira] [Resolved] (HBASE-27929) Add a LICENSE file to hbase-kustomize.git

[ https://issues.apache.org/jira/browse/HBASE-27929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk resolved HBASE-27929. -- Resolution: Fixed > Add a LICENSE file to hbase-kustomize.

[jira] [Created] (HBASE-27930) Add .asf.yaml to hbase-kustomize.git

Nick Dimiduk created HBASE-27930: Summary: Add .asf.yaml to hbase-kustomize.git Key: HBASE-27930 URL: https://issues.apache.org/jira/browse/HBASE-27930 Project: HBase Issue Type: Task

[jira] [Created] (HBASE-27929) Add a LICENSE file to hbase-kustomize.git

Nick Dimiduk created HBASE-27929: Summary: Add a LICENSE file to hbase-kustomize.git Key: HBASE-27929 URL: https://issues.apache.org/jira/browse/HBASE-27929 Project: HBase Issue Type: Task

Re: [DISCUSS] Introduce new git repository for kustomize definitions (was: Kubernetes Orchestration for ZK, HDFS, and HBase)

I’ve created this repository. Unless there is an objection, I’ll push an initial commit with a LICENSE file so that there’s a baseline to make PRs against. Thanks, Nick On Fri, 9 Jun 2023 at 18:30, Nick Dimiduk wrote: > Thanks everyone who has replied. > > If there are no further

Re: [DISCUSS] Introduce new git repository for kustomize definitions (was: Kubernetes Orchestration for ZK, HDFS, and HBase)

3 at 5:33 PM Viraj Jasani wrote: > > > +1 for hbase-kustomize > > > > On Mon, Jun 5, 2023 at 4:44 AM Nick Dimiduk wrote: > > > > > Hello, > > > > > > As I work through the integration of these kustomize definitions into > the >

[DISCUSS] Introduce new git repository for kustomize definitions (was: Kubernetes Orchestration for ZK, HDFS, and HBase)

that are not otherwise needed by operator-tools. What do you think? SHould we request a new repository for the kustomize files? I propose hbase-kustomize.git. Thanks, Nick On Mon, May 22, 2023 at 4:33 PM Nick Dimiduk wrote: > I went ahead and rebuilt the Hadoop image module in the same style

Re: [DISCUSS] Disable HDFS readahead for PREAD reads

Hi Bryan, Based on your observations, I'm in favor of changing the default for new minor releases going forward, and maybe some comments about this in the online book. I'm also in favor of exposing configurable readahead for STREAM reads, enabling easier experimentation for those keen to do so.

Re: [DISCUSS] Kubernetes Orchestration for ZK, HDFS, and HBase

en I come back I will review them) > > -Stephen > > On Mon, May 22, 2023 at 6:08 PM Nick Dimiduk wrote: > > > Heya team, > > > > I have rebuilt one of the early PRs so that the docker image build pieces > > are integrated with the maven build. If this is

Re: [DISCUSS] Kubernetes Orchestration for ZK, HDFS, and HBase

://github.com/apache/hbase-operator-tools/pull/118 On Fri, May 12, 2023 at 4:19 PM Nick Dimiduk wrote: > Heya team, > > I have created individual pull-requests for each of the major functional > pieces outlined in the initial branch. These await review. > > I've now started w

Re: [DISCUSS] Kubernetes Orchestration for ZK, HDFS, and HBase

integration via exec-maven-plugin. I'm also investigating how to pull the container image build up into maven as well. Thanks, Nic, On Thu, May 4, 2023 at 2:42 PM Nick Dimiduk wrote: > Heya team, > > I've created a feature ticket [0] from which this contribution can hang. >

[jira] [Created] (HBASE-27856) Add hadolint binary to operator-tools yetus environment

Nick Dimiduk created HBASE-27856: Summary: Add hadolint binary to operator-tools yetus environment Key: HBASE-27856 URL: https://issues.apache.org/jira/browse/HBASE-27856 Project: HBase

[jira] [Created] (HBASE-27847) Introduce HBase image

Nick Dimiduk created HBASE-27847: Summary: Introduce HBase image Key: HBASE-27847 URL: https://issues.apache.org/jira/browse/HBASE-27847 Project: HBase Issue Type: Sub-task

[jira] [Created] (HBASE-27846) Introduce hadoop image

Nick Dimiduk created HBASE-27846: Summary: Introduce hadoop image Key: HBASE-27846 URL: https://issues.apache.org/jira/browse/HBASE-27846 Project: HBase Issue Type: Sub-task

Re: [DISCUSS] Move stable pointer to 2.5.x

+1 On Fri, 5 May 2023 at 09:13, 张铎(Duo Zhang) wrote: > As discussed in the online meeting, and also other places, before EOL > 2.4.x, we should first move our stable pointer to 2.5.x. > > And there are also som2.5.x usages around the community on large clusters > which proves that the release

[jira] [Created] (HBASE-27837) CI integration for the integration test suite

Nick Dimiduk created HBASE-27837: Summary: CI integration for the integration test suite Key: HBASE-27837 URL: https://issues.apache.org/jira/browse/HBASE-27837 Project: HBase Issue Type

  1   2   3   4   5   6   7   8   9   10   >