Ajeet Rai created HBASE-25371:
-
Summary: When openRegion fails during initial verification(before
initializing and setting seq num), exception is observed during region close.
Key: HBASE-25371
URL:
Adam Wang created HBASE-25370:
-
Summary: Fix flaky test
TestClassFinder#testClassFinderDefaultsToOwnPackage
Key: HBASE-25370
URL: https://issues.apache.org/jira/browse/HBASE-25370
Project: HBase
Seems reasonable to at least have an easy option for running the
permutations even if it's not the default.
On Mon, Dec 7, 2020 at 3:23 PM Andrew Purtell wrote:
> > The dev-support/hbase-vote.sh has not been updated to match that logic.
>
> Ok, shall we at least do that? Seems like a good idea,
> The dev-support/hbase-vote.sh has not been updated to match that logic.
Ok, shall we at least do that? Seems like a good idea, although of course
the voter's resources will be consumed for a longer period of time.
On Mon, Dec 7, 2020 at 2:45 PM Nick Dimiduk wrote:
> On Mon, Dec 7, 2020 at
On Mon, Dec 7, 2020 at 2:30 PM Andrew Purtell wrote:
> Do we have a list of optional build profiles that are required or
> recommended for release or release testing? I might have missed it.
>
> If we do not have one, shall we start one?
>
> If we should start a list of optional build profiles
Do we have a list of optional build profiles that are required or
recommended for release or release testing? I might have missed it.
If we do not have one, shall we start one?
If we should start a list of optional build profiles that the RM and
release testers should ensure are successful, what
[
https://issues.apache.org/jira/browse/HBASE-25369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-25369.
--
Fix Version/s: (was: 3.0.0-alpha-1)
Resolution: Duplicate
> hbase-vote.sh mvn
Has anyone successfully built/run this RC with JDK11 and Hadoop3 profile?
I'm seeing test failures locally in the hbase-asyncfs module.
Reproducible with:
$
JAVA_HOME=/Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home
mvn clean install -Dhadoop.profile=3.0
Nick Dimiduk created HBASE-25369:
Summary: hbase-vote.sh mvn invocation broken with empty
MVN_PROPERTIES variable
Key: HBASE-25369
URL: https://issues.apache.org/jira/browse/HBASE-25369
Project:
Huaxiang Sun created HBASE-25368:
Summary: Filter out more invalid encoded name in
isEncodedRegionName(byte[] regionName)
Key: HBASE-25368
URL: https://issues.apache.org/jira/browse/HBASE-25368
Hello!
When I search Jira for your email address, I find a single result, an
account with the username "SWH12". This user account has the contributor
permission and should already be assignable to issues and be able to assign
itself an issue. Please confirm that this is the account you're using.
I don't need to do this. Viraj checked release repos and the .asc.asc files
have been present since 2.3 releases, which were performed with the release
script. (I don't blame the release script, this seems to be some kind of
Maven issue.)
On Sun, Dec 6, 2020 at 8:41 PM Andrew Purtell
wrote:
>
Thanks for looking into it. I’m inclined to consider this a Maven bug of some
kind.
Fortunately these files are harmless. This issue should not block any RC until
it is eventually fixed.
> On Dec 7, 2020, at 9:43 AM, Viraj Jasani wrote:
>
> It seems these files (site.xml.asc.asc and
It seems these files (site.xml.asc.asc and pom.asc.asc) are present
starting 2.3.0 release.
On 2020/12/07 17:27:51, Viraj Jasani wrote:
> > Viraj, we have not determined there is a staging repository problem yet.
> Those files could be “normal” and present in previous RCs and nobody
> noticed.
> Viraj, we have not determined there is a staging repository problem yet.
Those files could be “normal” and present in previous RCs and nobody
noticed.
Yeah I realized my if condition was not appropriate. +1 stays if we
conclude to go ahead with current RC i.e if presence of
.asc.asc is not
Thank you, that is very helpful. Please look for the .asc.asc file problem in
the resulting staging repo and write back.
> On Dec 7, 2020, at 8:53 AM, Stack wrote:
>
> On Sun, Dec 6, 2020 at 8:41 PM Andrew Purtell
> wrote:
>
>> Now that the Docker release script is working again (thanks
Viraj, we have not determined there is a staging repository problem yet. Those
files could be “normal” and present in previous RCs and nobody noticed.
> On Dec 7, 2020, at 5:59 AM, Viraj Jasani wrote:
>
> +1 (if staging repository issue is resolved for RC1)
>
> * Signature: ok
> *
On Sun, Dec 6, 2020 at 8:41 PM Andrew Purtell
wrote:
> Now that the Docker release script is working again (thanks Stack) I can
> make a test branch and run that to build a fake RC and examine the
> resulting temporary repository. If there are .asc.asc files again I’m not
> sure we learn more
hello:
Hello, I am contributing to the hbase community for the first
time. I want to solve the above problems, but I have no permission to assign to
myself.
So??I want to apply for the contributor permission of jira.Thanks!
Akshay Sudheer created HBASE-25367:
--
Summary: Sort broken after Change 'State time' in UI
Key: HBASE-25367
URL: https://issues.apache.org/jira/browse/HBASE-25367
Project: HBase
Issue Type:
[
https://issues.apache.org/jira/browse/HBASE-25336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-25336.
---
Hadoop Flags: Reviewed
Resolution: Fixed
Pushed to master and branch-2.
Thanks [~zghao] for
+1 (if staging repository issue is resolved for RC1)
* Signature: ok
* Checksum : ok
* Rat check (1.8.0_171): ok
- mvn clean apache-rat:check
* Built from source (1.8.0_171): ok
- mvn clean install -DskipTests
* CRUD: ok
* Load 10M rows: ok
* WebUI: ok
* Unit tests pass (1.8.0_171): failed
-
22 matches
Mail list logo
