[jira] [Created] (HBASE-26402) Remove branch-1.4 from compatibility matrix and release manager section in our ref guide
Duo Zhang created HBASE-26402: - Summary: Remove branch-1.4 from compatibility matrix and release manager section in our ref guide Key: HBASE-26402 URL: https://issues.apache.org/jira/browse/HBASE-26402 Project: HBase Issue Type: Sub-task Components: documentation Reporter: Duo Zhang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-26401) Remove jenkins files for branch-1.4
Duo Zhang created HBASE-26401: - Summary: Remove jenkins files for branch-1.4 Key: HBASE-26401 URL: https://issues.apache.org/jira/browse/HBASE-26401 Project: HBase Issue Type: Sub-task Components: jenkins, scripts Reporter: Duo Zhang Assignee: Duo Zhang The nightly for branch-1.4 has been broken for a very long time. Since now we have decided to EOL branch-1.4, let's remove these jenkins files for branch-1.4. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-26355) Release 1.4.14
[ https://issues.apache.org/jira/browse/HBASE-26355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-26355. --- Resolution: Fixed Done. > Release 1.4.14 > -- > > Key: HBASE-26355 > URL: https://issues.apache.org/jira/browse/HBASE-26355 > Project: HBase > Issue Type: Task > Components: community >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > > Per the end of this thread: > https://lists.apache.org/thread.html/r34d3fb86d667f8b3e58cbba78655733ac76e10f5883650f4910adc5c%40%3Cdev.hbase.apache.org%3E > Let's do a final 1.4.14 release and mark branch-1.4 as EOL. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-26400) EOL 1.4.x
Duo Zhang created HBASE-26400: - Summary: EOL 1.4.x Key: HBASE-26400 URL: https://issues.apache.org/jira/browse/HBASE-26400 Project: HBase Issue Type: Task Reporter: Duo Zhang Assignee: Duo Zhang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-26399) branch-2 modules dependencies are confused
Mike Drob created HBASE-26399:
-
Summary: branch-2 modules dependencies are confused
Key: HBASE-26399
URL: https://issues.apache.org/jira/browse/HBASE-26399
Project: HBase
Issue Type: Task
Components: build
Affects Versions: 2.5.0
Environment: branch-2
Java version: 11.0.12
Apache Maven 3.8.3
Reporter: Mike Drob
When trying to build branch-2, I get several dependency resolution issues.
Different issues based on what approach I try.
{{mvn -e -B --no-transfer-progress -Dhadoop.profile=3.0
-Dhadoop-three.version=3.0.0-cdh6.3.2 clean install -Dmaven.test.skip=true}}
will fail with:
{noformat}
231.4 [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M3:enforce
(hadoop-profile-min-maven-min-java-banned-xerces) on project
hbase-build-configuration: Execution
hadoop-profile-min-maven-min-java-banned-xerces of goal
org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M3:enforce failed:
org.apache.maven.shared.dependency.graph.DependencyGraphBuilderException: Could
not resolve following dependencies:
[org.apache.hbase:hbase-annotations:jar:tests:2.5.0-SNAPSHOT (test)]: Could not
resolve dependencies for project
org.apache.hbase:hbase-build-configuration:pom:2.5.0-SNAPSHOT: Could not find
artifact org.apache.hbase:hbase-annotations:jar:tests:2.5.0-SNAPSHOT in
snapshots{noformat}
Note that I'm running this behind a corporate firewall, so if there is a
snapshot available upstream in apache snapshots repo, then I'm not able to
access it. I would have thought that it can use the locally built and installed
one instead, since build-configuration does correctly come after annotations.
If I change to {{-DskipTests}} then this target succeeds, but later {{mvn
site}} fails with
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.7.1:site (default-site) on project
hbase: Error generating maven-javadoc-plugin:3.2.0:aggregate-no-fork report:
[ERROR] Exit code: 1 -
/home/jenkins-agent/hbase/hbase-testing-util/src/main/java/org/apache/hadoop/hbase/testing/TestingHBaseClusterOption.java:24:
error: cannot find symbol
[ERROR] import org.apache.hadoop.hbase.StartMiniClusterOption;
[ERROR] ^
[ERROR] symbol: class StartMiniClusterOption
[ERROR] location: package org.apache.hadoop.hbase {noformat}
Again, I'm missing testing packages, this time for javadocs.
I believe I was getting similar errors on main branch, although I don't have
logs for that anymore.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: [DISCUSS] JIRA Version page only available to authenticated users
for example, this is roughly what HBase 2.4.7 would look like: https://gist.github.com/busbey/b5a849626bc4fcc2cbdd18f56c8d2807#file-apache-hbase-2-4-7-releasenotes-md (but the url would be to the rel/2.4.7 tag on github) On Tue, Oct 26, 2021 at 1:33 PM Sean Busbey wrote: > let's just start pointing at the release notes? for any given release that > should be where we as a community have spent the most effort crafting a > message for our downstream folks. > > preferably rendered. Could we start putting the generated release note > that just the part relevant to the specific patch release into the GitHub > release tag's release note? IIRC that will render markdown and is readable > without logging in. We could integrate populating it via the GitHub API > into the release tooling. > > On Tue, Oct 26, 2021 at 11:39 AM Nick Dimiduk wrote: > >> I find it surprising that our announcements point people at something that >> requires a login. It seems not very “open” or “inviting”. >> >> On Tue, Oct 26, 2021 at 07:26 Sean Busbey wrote: >> >> > We have historically linked to the Jira Version page because it >> provides a >> > starting point on issue navigation that we don't get elsewhere. Plenty >> of >> > interactions with our issue tracker require a login. Why is that >> threshold >> > not acceptable here? I think we should just note that a login with >> > low-friction signup is required. Though I guess we will need to validate >> > that it's still straightforward to create a jira account. >> > >> > The changelog and release notes for the release are both available on >> > downloads.a.o if we want to link to something available without a login >> > rather than just mentioning them. If we're going to change what we'd >> link >> > to I'd rather one of those than jira at all. >> > >> > On Tue, Oct 26, 2021 at 5:55 AM 张铎(Duo Zhang) >> > wrote: >> > >> > > At least for me I haven't typed it up in the past... >> > > >> > > I'm not sure whether you need to set up a template manually first... >> > > >> > > Wei-Chiu Chuang 于2021年10月26日周二 >> 下午5:48写道： >> > > >> > > > Duo, >> > > > Just out of curiosity, is this release note in the JIRA populated >> > > > automatically? Or someone typed it up? >> > > > >> > > > On Tue, Oct 26, 2021 at 4:25 PM 张铎(Duo Zhang) < >> palomino...@gmail.com> >> > > > wrote: >> > > > >> > > > > I think this is what we should link in the announcement? >> > > > > >> > > > > >> > > > > >> > > > >> > > >> > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310753&version=12350545 >> > > > > >> > > > > We should link the release note, not the page where we can >> generate >> > the >> > > > > release note... >> > > > > >> > > > > Just my thoughts. Thanks. >> > > > > >> > > > > Nick Dimiduk 于2021年10月26日周二 上午1:19写道： >> > > > > >> > > > > > Heya, >> > > > > > >> > > > > > The link we include in our announcement emails is only >> accessible >> > for >> > > > > > people who are logged into JIRA. Seems like bad form. >> > > > > > >> > > > > > I.e., >> > > https://issues.apache.org/jira/projects/HBASE/versions/12350545 >> > > > > > >> > > > > > I doubt this is by design on our part. I wonder if JIRA has >> always >> > > been >> > > > > > configured this way, or if it's an (un)intentional change on the >> > part >> > > > of >> > > > > > Infra. >> > > > > > >> > > > > > Should we instead link to something else? >> > > > > > >> > > > > > Thanks, >> > > > > > Nick >> > > > > > >> > > > > >> > > > >> > > >> > >> >
Re: [DISCUSS] JIRA Version page only available to authenticated users
let's just start pointing at the release notes? for any given release that should be where we as a community have spent the most effort crafting a message for our downstream folks. preferably rendered. Could we start putting the generated release note that just the part relevant to the specific patch release into the GitHub release tag's release note? IIRC that will render markdown and is readable without logging in. We could integrate populating it via the GitHub API into the release tooling. On Tue, Oct 26, 2021 at 11:39 AM Nick Dimiduk wrote: > I find it surprising that our announcements point people at something that > requires a login. It seems not very “open” or “inviting”. > > On Tue, Oct 26, 2021 at 07:26 Sean Busbey wrote: > > > We have historically linked to the Jira Version page because it provides > a > > starting point on issue navigation that we don't get elsewhere. Plenty of > > interactions with our issue tracker require a login. Why is that > threshold > > not acceptable here? I think we should just note that a login with > > low-friction signup is required. Though I guess we will need to validate > > that it's still straightforward to create a jira account. > > > > The changelog and release notes for the release are both available on > > downloads.a.o if we want to link to something available without a login > > rather than just mentioning them. If we're going to change what we'd link > > to I'd rather one of those than jira at all. > > > > On Tue, Oct 26, 2021 at 5:55 AM 张铎(Duo Zhang) > > wrote: > > > > > At least for me I haven't typed it up in the past... > > > > > > I'm not sure whether you need to set up a template manually first... > > > > > > Wei-Chiu Chuang 于2021年10月26日周二 > 下午5:48写道： > > > > > > > Duo, > > > > Just out of curiosity, is this release note in the JIRA populated > > > > automatically? Or someone typed it up? > > > > > > > > On Tue, Oct 26, 2021 at 4:25 PM 张铎(Duo Zhang) > > > > > wrote: > > > > > > > > > I think this is what we should link in the announcement? > > > > > > > > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310753&version=12350545 > > > > > > > > > > We should link the release note, not the page where we can generate > > the > > > > > release note... > > > > > > > > > > Just my thoughts. Thanks. > > > > > > > > > > Nick Dimiduk 于2021年10月26日周二 上午1:19写道： > > > > > > > > > > > Heya, > > > > > > > > > > > > The link we include in our announcement emails is only accessible > > for > > > > > > people who are logged into JIRA. Seems like bad form. > > > > > > > > > > > > I.e., > > > https://issues.apache.org/jira/projects/HBASE/versions/12350545 > > > > > > > > > > > > I doubt this is by design on our part. I wonder if JIRA has > always > > > been > > > > > > configured this way, or if it's an (un)intentional change on the > > part > > > > of > > > > > > Infra. > > > > > > > > > > > > Should we instead link to something else? > > > > > > > > > > > > Thanks, > > > > > > Nick > > > > > > > > > > > > > > > > > > > > >
[jira] [Created] (HBASE-26398) CellCounter fails for large tables filling up local disk
Istvan Toth created HBASE-26398: --- Summary: CellCounter fails for large tables filling up local disk Key: HBASE-26398 URL: https://issues.apache.org/jira/browse/HBASE-26398 Project: HBase Issue Type: Bug Components: mapreduce Affects Versions: 3.0.0-alpha-2 Reporter: Istvan Toth Assignee: Istvan Toth CellCounter dumps all cell coordinates into its output, which can become huge. The spill can fill the local disk on the reducer. CellCounter hardcodes *mapreduce.job.reduces* to *1*, so it is not possible to use multiple reducers to get around this. Fixing this is easy, by not hardcoding *mapreduce.job.reduces*, it still defaults to 1, but can be overriden by the user. CellCounter also generates two extra records with constant keys for each cell, which have to be processed by the reducer. Even with multiple reducers, these (1/3 of the totcal records) will got the same reducer, which can also fill up the disk. This can be fixed by adding a Combiner to the Mapper, which sums the counter records, thereby reducing the Mapper output records to 1/3 of their previous amount. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [DISCUSS] JIRA Version page only available to authenticated users
I find it surprising that our announcements point people at something that requires a login. It seems not very “open” or “inviting”. On Tue, Oct 26, 2021 at 07:26 Sean Busbey wrote: > We have historically linked to the Jira Version page because it provides a > starting point on issue navigation that we don't get elsewhere. Plenty of > interactions with our issue tracker require a login. Why is that threshold > not acceptable here? I think we should just note that a login with > low-friction signup is required. Though I guess we will need to validate > that it's still straightforward to create a jira account. > > The changelog and release notes for the release are both available on > downloads.a.o if we want to link to something available without a login > rather than just mentioning them. If we're going to change what we'd link > to I'd rather one of those than jira at all. > > On Tue, Oct 26, 2021 at 5:55 AM 张铎(Duo Zhang) > wrote: > > > At least for me I haven't typed it up in the past... > > > > I'm not sure whether you need to set up a template manually first... > > > > Wei-Chiu Chuang 于2021年10月26日周二 下午5:48写道： > > > > > Duo, > > > Just out of curiosity, is this release note in the JIRA populated > > > automatically? Or someone typed it up? > > > > > > On Tue, Oct 26, 2021 at 4:25 PM 张铎(Duo Zhang) > > > wrote: > > > > > > > I think this is what we should link in the announcement? > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310753&version=12350545 > > > > > > > > We should link the release note, not the page where we can generate > the > > > > release note... > > > > > > > > Just my thoughts. Thanks. > > > > > > > > Nick Dimiduk 于2021年10月26日周二 上午1:19写道： > > > > > > > > > Heya, > > > > > > > > > > The link we include in our announcement emails is only accessible > for > > > > > people who are logged into JIRA. Seems like bad form. > > > > > > > > > > I.e., > > https://issues.apache.org/jira/projects/HBASE/versions/12350545 > > > > > > > > > > I doubt this is by design on our part. I wonder if JIRA has always > > been > > > > > configured this way, or if it's an (un)intentional change on the > part > > > of > > > > > Infra. > > > > > > > > > > Should we instead link to something else? > > > > > > > > > > Thanks, > > > > > Nick > > > > > > > > > > > > > > >
[jira] [Resolved] (HBASE-26395) Add 1.4.14 to download page
[ https://issues.apache.org/jira/browse/HBASE-26395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-26395. --- Resolution: Fixed Pushed an addendum to fix the 1.4.14 src sha512 file link. > Add 1.4.14 to download page > --- > > Key: HBASE-26395 > URL: https://issues.apache.org/jira/browse/HBASE-26395 > Project: HBase > Issue Type: Sub-task > Components: website >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 3.0.0-alpha-2 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (HBASE-26395) Add 1.4.14 to download page
[ https://issues.apache.org/jira/browse/HBASE-26395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang reopened HBASE-26395: --- > Add 1.4.14 to download page > --- > > Key: HBASE-26395 > URL: https://issues.apache.org/jira/browse/HBASE-26395 > Project: HBase > Issue Type: Sub-task > Components: website >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 3.0.0-alpha-2 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [DISCUSS] JIRA Version page only available to authenticated users
We have historically linked to the Jira Version page because it provides a starting point on issue navigation that we don't get elsewhere. Plenty of interactions with our issue tracker require a login. Why is that threshold not acceptable here? I think we should just note that a login with low-friction signup is required. Though I guess we will need to validate that it's still straightforward to create a jira account. The changelog and release notes for the release are both available on downloads.a.o if we want to link to something available without a login rather than just mentioning them. If we're going to change what we'd link to I'd rather one of those than jira at all. On Tue, Oct 26, 2021 at 5:55 AM 张铎(Duo Zhang) wrote: > At least for me I haven't typed it up in the past... > > I'm not sure whether you need to set up a template manually first... > > Wei-Chiu Chuang 于2021年10月26日周二 下午5:48写道： > > > Duo, > > Just out of curiosity, is this release note in the JIRA populated > > automatically? Or someone typed it up? > > > > On Tue, Oct 26, 2021 at 4:25 PM 张铎(Duo Zhang) > > wrote: > > > > > I think this is what we should link in the announcement? > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310753&version=12350545 > > > > > > We should link the release note, not the page where we can generate the > > > release note... > > > > > > Just my thoughts. Thanks. > > > > > > Nick Dimiduk 于2021年10月26日周二 上午1:19写道： > > > > > > > Heya, > > > > > > > > The link we include in our announcement emails is only accessible for > > > > people who are logged into JIRA. Seems like bad form. > > > > > > > > I.e., > https://issues.apache.org/jira/projects/HBASE/versions/12350545 > > > > > > > > I doubt this is by design on our part. I wonder if JIRA has always > been > > > > configured this way, or if it's an (un)intentional change on the part > > of > > > > Infra. > > > > > > > > Should we instead link to something else? > > > > > > > > Thanks, > > > > Nick > > > > > > > > > >
[ANNOUNCE] Apache HBase 1.4.14 is now available for download
The HBase team is happy to announce the immediate availability of HBase1.4.14. Apache HBase™ is an open-source, distributed, versioned, non-relational database. Apache HBase gives you low latency random access to billions of rows with millions of columns atop non-specialized hardware. To learn more about HBase, see https://hbase.apache.org/. HBase 1.4.14 is the latest release of the HBase 1.4 line, continuing on the theme of bringing a stable, reliable database to the Apache Big Data ecosystem and beyond. 1.4.14 includes ~45 bugs and improvement fixes done since 1.4.13. The full list of issues can be found here: https://s.apache.org/hbase-1.4.14-jira-release-notes And notice that 1.4.14 is the last release of the HBase 1.4 line. Thank you for trusting and choosing the 1.4.x release line. In the future, users are encouraged to upgrade to our current stable release line 2.4.x. To download please follow the links and instructions on our website: https://hbase.apache.org/downloads.html For instructions on verifying ASF release downloads, please see https://www.apache.org/dyn/closer.cgi#verify Project member signature keys can be found at https://www.apache.org/dist/hbase/KEYS Thanks to all the contributors who made this release possible! Best, The HBase Dev Team
[jira] [Resolved] (HBASE-26395) Add 1.4.14 to download page
[ https://issues.apache.org/jira/browse/HBASE-26395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-26395. --- Hadoop Flags: Reviewed Resolution: Fixed Merged to master. Thanks [~haxiaolin] for reviewing. > Add 1.4.14 to download page > --- > > Key: HBASE-26395 > URL: https://issues.apache.org/jira/browse/HBASE-26395 > Project: HBase > Issue Type: Sub-task > Components: website >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 3.0.0-alpha-2 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-26397) Display the excluded datanodes on regionserver UI
Xiaolin Ha created HBASE-26397: -- Summary: Display the excluded datanodes on regionserver UI Key: HBASE-26397 URL: https://issues.apache.org/jira/browse/HBASE-26397 Project: HBase Issue Type: Sub-task Reporter: Xiaolin Ha Assignee: Xiaolin Ha -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [DISCUSS] JIRA Version page only available to authenticated users
At least for me I haven't typed it up in the past... I'm not sure whether you need to set up a template manually first... Wei-Chiu Chuang 于2021年10月26日周二 下午5:48写道： > Duo, > Just out of curiosity, is this release note in the JIRA populated > automatically? Or someone typed it up? > > On Tue, Oct 26, 2021 at 4:25 PM 张铎(Duo Zhang) > wrote: > > > I think this is what we should link in the announcement? > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310753&version=12350545 > > > > We should link the release note, not the page where we can generate the > > release note... > > > > Just my thoughts. Thanks. > > > > Nick Dimiduk 于2021年10月26日周二 上午1:19写道： > > > > > Heya, > > > > > > The link we include in our announcement emails is only accessible for > > > people who are logged into JIRA. Seems like bad form. > > > > > > I.e., https://issues.apache.org/jira/projects/HBASE/versions/12350545 > > > > > > I doubt this is by design on our part. I wonder if JIRA has always been > > > configured this way, or if it's an (un)intentional change on the part > of > > > Infra. > > > > > > Should we instead link to something else? > > > > > > Thanks, > > > Nick > > > > > >
Re: [DISCUSS] JIRA Version page only available to authenticated users
Duo, Just out of curiosity, is this release note in the JIRA populated automatically? Or someone typed it up? On Tue, Oct 26, 2021 at 4:25 PM 张铎(Duo Zhang) wrote: > I think this is what we should link in the announcement? > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310753&version=12350545 > > We should link the release note, not the page where we can generate the > release note... > > Just my thoughts. Thanks. > > Nick Dimiduk 于2021年10月26日周二 上午1:19写道： > > > Heya, > > > > The link we include in our announcement emails is only accessible for > > people who are logged into JIRA. Seems like bad form. > > > > I.e., https://issues.apache.org/jira/projects/HBASE/versions/12350545 > > > > I doubt this is by design on our part. I wonder if JIRA has always been > > configured this way, or if it's an (un)intentional change on the part of > > Infra. > > > > Should we instead link to something else? > > > > Thanks, > > Nick > > >
Re: [DISCUSS] JIRA Version page only available to authenticated users
I think this is what we should link in the announcement? https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310753&version=12350545 We should link the release note, not the page where we can generate the release note... Just my thoughts. Thanks. Nick Dimiduk 于2021年10月26日周二 上午1:19写道： > Heya, > > The link we include in our announcement emails is only accessible for > people who are logged into JIRA. Seems like bad form. > > I.e., https://issues.apache.org/jira/projects/HBASE/versions/12350545 > > I doubt this is by design on our part. I wonder if JIRA has always been > configured this way, or if it's an (un)intentional change on the part of > Infra. > > Should we instead link to something else? > > Thanks, > Nick >
