Re: [VOTE] HBase Thirdparty 2.2.0 RC1

Sure ,I will repost question and logs with new thread . Thanks On Mon, 1 Apr 2019 at 11:59 PM, Stack wrote: > Shekar: > > You put your note on a VOTE thread. Please redo your query in its own > thread to hbase dev. > > Can you paste some log when you redo your message on the dev list? > >

[jira] [Created] (HBASE-22145) windows hbase-env causes hbase cli/etc to ignore HBASE_OPTS

Sergey Shelukhin created HBASE-22145: Summary: windows hbase-env causes hbase cli/etc to ignore HBASE_OPTS Key: HBASE-22145 URL: https://issues.apache.org/jira/browse/HBASE-22145 Project: HBase

[jira] [Created] (HBASE-22144) MultiRowRangeFilter does not work with reversed scans

Josh Elser created HBASE-22144: -- Summary: MultiRowRangeFilter does not work with reversed scans Key: HBASE-22144 URL: https://issues.apache.org/jira/browse/HBASE-22144 Project: HBase Issue

Re: [DISCUSS] release hbase-connectors

You the man Balazs. No harm in putting up a 1.0.0 I'd say. (There's a bit of a script on HBASE-22136 used building an hbase-thirdparty that might be of use. The README in hbase-thirdparty has some notes on how it was RC'd that might be of help doing hbase-connectors. Shout if I can help).

Re: [VOTE] HBase Thirdparty 2.2.0 RC1

Shekar: You put your note on a VOTE thread. Please redo your query in its own thread to hbase dev. Can you paste some log when you redo your message on the dev list? Thanks, S On Mon, Apr 1, 2019 at 12:33 AM Shekhar Dhotre < shekhar.dho...@clairvoyantsoft.com> wrote: > Hi All , > I have a

Re: [DISCUSS] hbck2 evolve independently X avoiding having client side logic on hbck2 commands

On Mon, Apr 1, 2019 at 9:56 AM Wellington Chevreuil < wellington.chevre...@gmail.com> wrote: > > > > Am interested to hear what's the general opinion on the way to move forward > with hbck2? Should we completely discourage client bound logic patches such > as the one from HBASE-22143 ? >

[DISCUSS] hbck2 evolve independently X avoiding having client side logic on hbck2 commands

My understanding on the motivation of moving hbck2 (and potentially other operation related tools) to a separate project was to allow it to evolve on its own cadence, as new interventions to fix previously unforeseen problems were identified, we would now be able to deliver updated tool versions

[jira] [Resolved] (HBASE-21525) java.io.IOException: java.lang.ClassNotFoundException: clone_snapshot from hbase2.0.0 to hbase1.2.0

[ https://issues.apache.org/jira/browse/HBASE-21525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pankaj Kumar resolved HBASE-21525. -- Resolution: Duplicate Closing this as a duplicate of HBASE-16189 > java.io.IOException:

Re: [DISCUSS] release hbase-connectors

We're not ready to work with Java 11 as a project yet, IMHO, so Java 8 should be fine. On Mon, Apr 1, 2019 at 6:43 AM Balazs Meszaros wrote: > Hi All, > > Since 2.0 connectors have been moved out from hbase repository to > hbase-connectors. We have several 2.x releases so far, but we haven't >

[jira] [Created] (HBASE-22143) HBCK2 setRegionState command

Wellington Chevreuil created HBASE-22143: Summary: HBCK2 setRegionState command Key: HBASE-22143 URL: https://issues.apache.org/jira/browse/HBASE-22143 Project: HBase Issue Type: New

Re: [VOTE] HBase Thirdparty 2.2.0 RC1

+1 Checked signature, checksum Built from source Ran Apache Rat check Ran HBase master tests using this RC Checked CHANGES and RELEASENOTES On Sat, Mar 30, 2019 at 10:14 PM Stack wrote: > Please consider the following as the 2.2.0 release of Apache HBase > Thirdparty. It is the second release

[jira] [Created] (HBASE-22142) Space quota: If table is dropped inside namespace, data size usage is still considered for the drop table.

Shardul Singh created HBASE-22142: - Summary: Space quota: If table is dropped inside namespace, data size usage is still considered for the drop table. Key: HBASE-22142 URL:

[DISCUSS] release hbase-connectors

Hi All, Since 2.0 connectors have been moved out from hbase repository to hbase-connectors. We have several 2.x releases so far, but we haven't released hbase-connectors. 1. Are there any known issues which prevents us releasing it? Currently I see 5 open issue where component = hbase-connectors

[jira] [Created] (HBASE-22141) Fix TestAsyncDecommissionAdminApi

Duo Zhang created HBASE-22141: - Summary: Fix TestAsyncDecommissionAdminApi Key: HBASE-22141 URL: https://issues.apache.org/jira/browse/HBASE-22141 Project: HBase Issue Type: Sub-task

Hbase master down due to null cluster ID

Hi All , I have a cluster which is setup to replicate to GCP . In the log its showing cluster ID null so found this document which shows how to setup cluster ID .but that is for a third party product called FusionInsight Manager.

Re: [VOTE] HBase Thirdparty 2.2.0 RC1

+1 (binding) Checked sigs and sums: OK Built from src: OK Minor: >From dev_files/make_rc.sh we are using "git archive" instead of "maven package assembly:single", thus producing more files as listed below. Is this on purpose? Thanks. hbase-thirdparty-2.2.0/.gitignore

Re: Replacement for CellUtil.setTimestamp()

The later JIRAs like https://issues.apache.org/jira/browse/HBASE-19092 exposed a CellBuilder and the CP has access to a the RawCellBuilder which will allow you to do a setTimeStamp on it. But note that it allows does a deep copy of the Cell bytes when the new cell is created out of the builder.

Re: [VOTE] HBase Thirdparty 2.2.0 RC1

Hi All , I have a cluster which is setup to replicate to GCP . In the log its showing cluster ID null so found this document which shows how to setup cluster ID .but that is for a third party product called FusionInsight Manager.

[jira] [Created] (HBASE-22140) Fix those flaky tests in master branch

Zheng Hu created HBASE-22140: Summary: Fix those flaky tests in master branch Key: HBASE-22140 URL: https://issues.apache.org/jira/browse/HBASE-22140 Project: HBase Issue Type: Bug