zhuobin zheng created HBASE-25512:
-
Summary: May throw StringIndexOutOfBoundsException when construct
illegal tablename error
Key: HBASE-25512
URL: https://issues.apache.org/jira/browse/HBASE-25512
[
https://issues.apache.org/jira/browse/HBASE-25475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani resolved HBASE-25475.
--
Hadoop Flags: Reviewed
Resolution: Fixed
Thanks for the contribution [~dasanjan1296]
[
https://issues.apache.org/jira/browse/HBASE-25431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack resolved HBASE-25431.
---
Fix Version/s: 2.5.0
3.0.0-alpha-1
Hadoop Flags: Reviewed
[
https://issues.apache.org/jira/browse/HBASE-25439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack resolved HBASE-25439.
---
Fix Version/s: 2.5.0
Resolution: Fixed
Appled #2841 addendum and then #2840 to
[
https://issues.apache.org/jira/browse/HBASE-25439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack reopened HBASE-25439:
---
Reopened to apply addendum and backport.
> Add BYTE unit in PrettyPrinter.Unit
>
Sean Busbey created HBASE-25511:
---
Summary: After hbase-thirdparty 3.4.1 release, set next dev version
Key: HBASE-25511
URL: https://issues.apache.org/jira/browse/HBASE-25511
Project: HBase
zhuobin zheng created HBASE-25510:
-
Summary: Optimize TableName.valueOf from O(n) to O(1). We can get
benefits when the number of tables in the cluster is greater than dozens
Key: HBASE-25510
URL:
Please vote on this Apache hbase release candidate,
hbase-2.3.4RC4
The VOTE will remain open for at least 72 hours.
[ ] +1 Release this package as Apache hbase 2.3.4
[ ] -1 Do not release this package because ...
The tag to be voted on is 2.3.4RC4:
Duo Zhang created HBASE-25509:
-
Summary: ChoreService.cancelChore will not call
ScheduledChore.cleanup which may lead to resource leak
Key: HBASE-25509
URL: https://issues.apache.org/jira/browse/HBASE-25509
Note the Maven temporary repository is hbase-1432 (not hbase-1430 as
cut-and-pasted)
https://repository.apache.org/content/repositories/orgapachehbase-1432/
On Thu, Jan 14, 2021 at 3:09 PM Andrew Purtell wrote:
> Please vote on this Apache hbase release candidate, hbase-2.4.1RC1.
>
> The
Please vote on this Apache hbase release candidate, hbase-2.4.1RC1.
The VOTE will remain open for at least 72 hours.
[ ] +1 Release this package as Apache hbase 2.4.1
[ ] -1 Do not release this package because ...
The tag to be voted on is 2.4.1RC1:
[
https://issues.apache.org/jira/browse/HBASE-25371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Huaxiang Sun reopened HBASE-25371:
--
I just found that this Jira has not been merged to branch-2,
branch-2.3,branch-2.4 yet.
Can you
[
https://issues.apache.org/jira/browse/HBASE-25375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-25375.
--
Release Note:
Adds a Vagrant project for running releases under `dev-support/release-vm`.
Thanks Andrew for cross checking this!
On Fri, 15 Jan 2021 at 12:15 AM, Andrew Purtell wrote:
> Viraj,
>
> HBASE-25425 is resolved with a fix version including 2.4.1.
>
> HBASE-25356 is resolved with a fix version including 2.4.1.
>
> HBASE-25277 is resolved with a fix version including 2.4.0.
I found and fixed an error.
It also appears someone or someones else fixed a few more fix versions. My
thanks to whomever that was.
On Thu, Jan 14, 2021 at 10:33 AM Andrew Purtell wrote:
> Viraj found some issues with fixversions so the changelog is incorrect.
>
> -1
>
> On Wed, Jan 13, 2021
[
https://issues.apache.org/jira/browse/HBASE-25249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Kyle Purtell resolved HBASE-25249.
-
Resolution: Fixed
> Adding StoreContext
> ---
>
>
Viraj,
HBASE-25425 is resolved with a fix version including 2.4.1.
HBASE-25356 is resolved with a fix version including 2.4.1.
HBASE-25277 is resolved with a fix version including 2.4.0.
That said, I withdrew the candidate and am now walking the git log of
branch-2.4 back to 2.4.0 and will
>I just have a PR with script (Phoenix):
https://github.com/apache/phoenix/pull/1088
>in case you would like to use anytime soon. I just used it
>for both 2.3.4 and 2.4.1 RCs. It takes project name as input.
That is great! Let me try it out.
On Thu, Jan 14, 2021 at 10:24 AM Huaxiang Sun wrote:
I fixed a few I found but missed these.
I will have to sink this RC.
Please help avoid this problem by only committing when patches or PRs are
ready for all the branches where the change is going to be committed, and
take care when resolving an issue to set fix versions correctly at that
time.
The RC2 failed due to the jira log issue found by Viraj, please do not
spend time on this Vote.
On Tue, Jan 12, 2021 at 9:13 PM Huaxiang Sun wrote:
> Please vote on this Apache hbase release candidate,
>
> hbase-2.3.4RC2
>
>
> The VOTE will remain open for at least 72 hours.
>
>
> [ ] +1
> I think we usually do sink RC for change log discrepancies
> but if there is a way to fix it without sinking RC that I am not
> aware of, let's wait to hear opinions.
Oh, I just checked the CHANGES.md, it does not include HBASE-25356,
HBASE-25425 and HBASE-25083.
I need to spin another RC.
On
I fixed all versions for HBASE-25425, HBASE-25356 and HBASE-25083, thanks
Viraj to look into these issues.
Yeah, I have not found a better way to check the case that commits in the
branch, but not in fixVersion of the jira.
On Thu, Jan 14, 2021 at 9:53 AM Huaxiang Sun wrote:
> Thanks Viraj! My
No worries, sure any script that can make our life easy is welcome.
I just have a PR with script (Phoenix):
https://github.com/apache/phoenix/pull/1088
in case you would like to use anytime soon. I just used it
for both 2.3.4 and 2.4.1 RCs. It takes project name as input.
If approved for HBase,
[
https://issues.apache.org/jira/browse/HBASE-25083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Huaxiang Sun resolved HBASE-25083.
--
Resolution: Fixed
> make sure the next hbase 1.y release has Hadoop 2.10 as a minimum version
Some discrepancies b/ commits landed with incorrect Jira fixVersion:
(2 of them are similar to ones that apply to current 2.3.4 RC)
HBASE-25425 => fixVersion doesn't have 2.4.1
HBASE-25356 => In progress without fixVersions
HBASE-25277 => fixVersion doesn't have 2.4.1
On 2021/01/14 03:08:28,
Thanks Viraj! My bad for HBASE-25356, I have fixed it correctly. Let me fix
HBASE-25425 and HBASE-25083.
A script will be great, can we work on Nick's git check script instead of a
new one (maybe)?
This will not sink the release candidate, right?
On Thu, Jan 14, 2021 at 9:29 AM Viraj Jasani
[
https://issues.apache.org/jira/browse/HBASE-25356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Huaxiang Sun resolved HBASE-25356.
--
Fix Version/s: 2.4.1
2.5.0
2.3.4
Resolution:
Sorry Huaxiang, there seems few more fixVersion discrepancies:
HBASE-25425 => fixVersion doesn't have 2.3.4
HBASE-25356 => In progress without fixVersions
HBASE-25083 => In progress with fixVersion 1.7.0 only
I am planning to create a Jira for a utility script that can
find these differences
Sean Busbey created HBASE-25508:
---
Summary: Add an example of using the thrift proxy in
thrift-over-http mode
Key: HBASE-25508
URL: https://issues.apache.org/jira/browse/HBASE-25508
Project: HBase
Xiaolin Ha created HBASE-25507:
--
Summary: Leak of ESTABLISHED sockets when encountered
"java.io.IOException: Invalid HFile block magic"
Key: HBASE-25507
URL: https://issues.apache.org/jira/browse/HBASE-25507
Bo Cui created HBASE-25506:
--
Summary: ServerManager affects MTTR of HMaster
Key: HBASE-25506
URL: https://issues.apache.org/jira/browse/HBASE-25506
Project: HBase
Issue Type: Improvement
31 matches
Mail list logo
