[jira] [Reopened] (HBASE-20737) put collection into ArrayList instead of addAll function
[ https://issues.apache.org/jira/browse/HBASE-20737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] taiyinglee reopened HBASE-20737: > put collection into ArrayList instead of addAll function > > > Key: HBASE-20737 > URL: https://issues.apache.org/jira/browse/HBASE-20737 > Project: HBase > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: taiyinglee >Assignee: taiyinglee >Priority: Trivial > Fix For: 3.0.0, 2.1.0 > > Attachments: HBASE-20737.v0.patch, HBASE-20737.v0.patch > > > [https://docs.oracle.com/javase/7/docs/api/java/util/Collection.html] > [https://docs.oracle.com/javase/7/docs/api/java/util/ArrayList.html] > [https://docs.oracle.com/javase/7/docs/api/java/util/Set.html] > > /hbase/hbase-server/src/main/java/org/apache/hadoop/hbase/master/ClusterStatusPublisher.java > change > List> entries = new ArrayList<>(); > entries.addAll(lastSent.entrySet()); > to > List> entries = new > ArrayList<>(lastSent.entrySet()); -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20750) If shaded client artifacts are built without the -Prelease flag, make sure they'll fail loudly if used
Sean Busbey created HBASE-20750:
---
Summary: If shaded client artifacts are built without the
-Prelease flag, make sure they'll fail loudly if used
Key: HBASE-20750
URL: https://issues.apache.org/jira/browse/HBASE-20750
Project: HBase
Issue Type: Improvement
Components: build, shading
Affects Versions: 3.0.0, 2.1.0
Reporter: Sean Busbey
If someone builds the shaded jars and doesn't pass the {{-Prelease}} flag, we
get near-empty jars.
We should make sure that if they're loaded they fail loudly rather than as
no-ops as they are now.
On a Hadoop 3 cluster without YARN-7190, this results in the following
confusing result:
{code}
Busbey-MBA:hbase busbey$
./hbase-assembly/target/hbase-2.1.0-SNAPSHOT-client/bin/hbase version
HBase 1.2.6
Source code repository
file:///home/busbey/projects/hbase/hbase-assembly/target/hbase-1.2.6
revision=Unknown
Compiled by busbey on Mon May 29 02:25:32 CDT 2017
>From source with checksum 7e8ce83a648e252758e9dae1fbe779c9
{code}
On a cluster not impacted by YARN-7190 we'll jsut get a confusing class not
found exception.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-20749) Upgrade our use of checkstyle to 8.6+
Sean Busbey created HBASE-20749: --- Summary: Upgrade our use of checkstyle to 8.6+ Key: HBASE-20749 URL: https://issues.apache.org/jira/browse/HBASE-20749 Project: HBase Issue Type: Improvement Components: build, community Reporter: Sean Busbey We should upgrade our checkstyle version to 8.6 or later so we can use the "match violation message to this regex" feature for suppression. That will allow us to make sure we don't regress on HTrace v3 vs v4 APIs (came up in HBASE-20332). We're currently blocked on upgrading to 8.3+ by [checkstyle #5279|https://github.com/checkstyle/checkstyle/issues/5279], a regression that flags our use of both the "separate import groups" and "put static imports over here" configs as an error. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20748) HBaseContext bulkLoad: being able to use custom versions
Charles PORROT created HBASE-20748: -- Summary: HBaseContext bulkLoad: being able to use custom versions Key: HBASE-20748 URL: https://issues.apache.org/jira/browse/HBASE-20748 Project: HBase Issue Type: Improvement Components: spark Reporter: Charles PORROT Attachments: bulkLoadCustomVersions.scala The _bulkLoad_ methods of _class org.apache.hadoop.hbase.spark_ use the system's current time for the version of the cells to bulk-load. This makes this method, and its twin _bulkLoadThinRows_, useless if you need to use your own versionning system. Thus, I propose a third _bulkLoad_ method, based on the original method. Instead of using an _Iterator(KeyFamilyQualifier, Array[Byte])_ as the basis for the writes, this new method would use an _Iterator(KeyFamilyQualifier, Array[Byte], Long_), with the _Long_ being the version. In case of illogical version (for instance, a negative version), the method would throw back to the current timestamp. See the attached file for a proposal of this new _bulkLoad_ method. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [VOTE] First release candidate for hbase-2.0.1 (RC0) is available
+1 - Checksum, signature: OK - RAT check: OK - Built from source: OK - Unit tests: OK - Web UI and shell: OK - LTT w/ 1M rows: OK On Mon, Jun 18, 2018 at 9:29 AM Peter Somogyi wrote: > +1 (non-binding) > > Checksums, signatures - OK > Build from source - OK > Unit tests - OK > Rat check - OK > Started in pseudo-distributed mode - OK > Shell CRUD operations - OK > Web UI / LOGs - OK > > On Wed, Jun 13, 2018 at 11:15 PM Stack wrote: > > > The first release candidate for Apache HBase 2.0.1 is available for > > download and testing. This is a bug fix release with 70+ commits [1]. > > Release notes are available here [2]. > > > > Artifacts are available here: > > > > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.1RC0/ > > > > Corresponding convenience artifacts for maven use are in the staging > > repository: > > > > https://repository.apache.org/content/repositories/orgapachehbase-1222 > > > > All artifacts are signed with my code signing key, 8ACC93D2, which is > > also in the project KEYS file: > > > > http://www.apache.org/dist/hbase/KEYS > > > > These artifacts correspond to commit ref > > > > 987f7b6d37c2fcacc942cc66e5c5122aba8fdfbe > > > > which has been tagged as 2.0.1RC0. > > > > Please take a few minutes to verify the release and vote on releasing it: > > > > [ ] +1 Release these artifacts as Apache HBase 2.0.1 > > [ ] -1 Do not release this package because ... > > > > This VOTE thread will remain open for at least 72 hours. > > > > Thanks, > > S > > > > 1. > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.1RC0/CHANGES.md > > 2. https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.1RC0/ > > RELEASENOTES.md > > >
Re: [VOTE] First release candidate for hbase-2.0.1 (RC0) is available
+1 (non-binding) Checksums, signatures - OK Build from source - OK Unit tests - OK Rat check - OK Started in pseudo-distributed mode - OK Shell CRUD operations - OK Web UI / LOGs - OK On Wed, Jun 13, 2018 at 11:15 PM Stack wrote: > The first release candidate for Apache HBase 2.0.1 is available for > download and testing. This is a bug fix release with 70+ commits [1]. > Release notes are available here [2]. > > Artifacts are available here: > > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.1RC0/ > > Corresponding convenience artifacts for maven use are in the staging > repository: > > https://repository.apache.org/content/repositories/orgapachehbase-1222 > > All artifacts are signed with my code signing key, 8ACC93D2, which is > also in the project KEYS file: > > http://www.apache.org/dist/hbase/KEYS > > These artifacts correspond to commit ref > > 987f7b6d37c2fcacc942cc66e5c5122aba8fdfbe > > which has been tagged as 2.0.1RC0. > > Please take a few minutes to verify the release and vote on releasing it: > > [ ] +1 Release these artifacts as Apache HBase 2.0.1 > [ ] -1 Do not release this package because ... > > This VOTE thread will remain open for at least 72 hours. > > Thanks, > S > > 1. https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.1RC0/CHANGES.md > 2. https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.1RC0/ > RELEASENOTES.md >
