[jira] [Resolved] (HBASE-26985) SecureBulkLoadManager will set wrong permission if umask too strict

[ https://issues.apache.org/jira/browse/HBASE-26985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viraj Jasani resolved HBASE-26985. -- Fix Version/s: 2.6.0 3.0.0-alpha-3 2.4.13

Re: Become a contributor

I've added your user id to the contributor group. Let me know if you have any questions. On Thu, Jun 2, 2022 at 2:23 PM Hernan Gelaf-Romer wrote: > Hello, > > I’m a new developer on the HBase team at HubSpot and would like to be > added as a contributor. My Jira username is hgromer. > > Thank

Become a contributor

Hello, I’m a new developer on the HBase team at HubSpot and would like to be added as a contributor. My Jira username is hgromer. Thank you! Hernan

[jira] [Reopened] (HBASE-26962) Add mob info in web UI

[ https://issues.apache.org/jira/browse/HBASE-26962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huaxiang Sun reopened HBASE-26962: -- The commit caused branch-2 build failure. Can you fix the build error and resubmit a patch?

Re: [DISCUSS] First release candidate for 2.5.0 (RC0) is available for evaluation

+1 to make the change everywhere. Sometimes, there is a need to update the release field after jira is released (in theory, it should not happen). Thanks Huaxiang On Thu, Jun 2, 2022 at 10:56 AM Andrew Purtell wrote: > Even for branch-2.4, we can start placing links into the file, at the top,

Re: [DISCUSS] First release candidate for 2.5.0 (RC0) is available for evaluation

Even for branch-2.4, we can start placing links into the file, at the top, leaving the output of the prior process in place below. I think it is fine to make this change everywhere. Curious what others think. On Thu, Jun 2, 2022 at 10:54 AM Andrew Purtell wrote: > I see, that would be totally

Re: [DISCUSS] First release candidate for 2.5.0 (RC0) is available for evaluation

I see, that would be totally fine with me if we just do the link instead of generating the files every time. On Thu, Jun 2, 2022 at 9:31 AM 张铎(Duo Zhang) wrote: > Oh, wait a minute. IIRC we have a consensus to use the jira page as release > note instead of committing a file to the repo? The

Re: [DISCUSS] First release candidate for 2.5.0 (RC0) is available for evaluation

Oh, wait a minute. IIRC we have a consensus to use the jira page as release note instead of committing a file to the repo? The problem is that, sometimes we just missed something in CHANGES.md or RELEASENOTES.md, no actually code change, but since we have committed these files to our git repo, we

[jira] [Created] (HBASE-27085) Create REPLICATION_SINK_TRACKER table to persist sentinel rows coming from source cluster.

Rushabh Shah created HBASE-27085: Summary: Create REPLICATION_SINK_TRACKER table to persist sentinel rows coming from source cluster. Key: HBASE-27085 URL: https://issues.apache.org/jira/browse/HBASE-27085

[jira] [Resolved] (HBASE-26962) Add mob info in web UI

[ https://issues.apache.org/jira/browse/HBASE-26962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-26962. --- Fix Version/s: 2.6.0 3.0.0-alpha-3 Hadoop Flags: Reviewed Resolution:

Re: [DISCUSS] First release candidate for 2.5.0 (RC0) is available for evaluation

I just noticed the release notes issue on the branch last evening. Let’s add the spotless application to the release note generation step in create-release at least or it will keep happening. The RM does not get a chance to intervene. The script uses the RM credentials to commit immediately

[jira] [Resolved] (HBASE-27039) Some methods of MasterRegion should be annotated for testing only

[ https://issues.apache.org/jira/browse/HBASE-27039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-27039. --- Fix Version/s: 2.6.0 3.0.0-alpha-3 2.4.13

[jira] [Resolved] (HBASE-27037) Display the region server state on the Web UI

[ https://issues.apache.org/jira/browse/HBASE-27037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-27037. --- Fix Version/s: 2.5.0 3.0.0-alpha-3 Hadoop Flags: Reviewed Resolution:

[jira] [Created] (HBASE-27084) Add spotless:check in mvn verify stage

Duo Zhang created HBASE-27084: - Summary: Add spotless:check in mvn verify stage Key: HBASE-27084 URL: https://issues.apache.org/jira/browse/HBASE-27084 Project: HBase Issue Type: Improvement

[jira] [Created] (HBASE-27083) Run spotless:apply in release scripts when we want to commit something

Duo Zhang created HBASE-27083: - Summary: Run spotless:apply in release scripts when we want to commit something Key: HBASE-27083 URL: https://issues.apache.org/jira/browse/HBASE-27083 Project: HBase

Re: [DISCUSS] First release candidate for 2.5.0 (RC0) is available for evaluation

Oh, I think we should include HBASE-27023, it fixes the license issue after we apply the spotless formatter where it will add the license header automatically. And also, it seems that the generated RELEASENOTE.md will introduce some lines ending with whitespace, then it will cause pre commit

[jira] [Resolved] (HBASE-27023) Add protobuf to NOTICE file

[ https://issues.apache.org/jira/browse/HBASE-27023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-27023. --- Fix Version/s: 3.0.0-alpha-3 2.4.13 2.5.1 Hadoop Flags:

[jira] [Resolved] (HBASE-26292) Update jetty version to fix CVE-2021-34429

[ https://issues.apache.org/jira/browse/HBASE-26292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nihal Jain resolved HBASE-26292. Resolution: Duplicate > Update jetty version to fix CVE-2021-34429 >