[jira] [Resolved] (HBASE-25350) The scan command gives a row, but get does not have this row.

2020-12-02 Thread ClownfishYang (Jira)
[ https://issues.apache.org/jira/browse/HBASE-25350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ClownfishYang resolved HBASE-25350. --- Resolution: Not A Problem Finally I found out that TTL caused this problem. > The scan

[jira] [Created] (HBASE-25354) Update create-release scripts; rotted

2020-12-02 Thread Michael Stack (Jira)
Michael Stack created HBASE-25354: - Summary: Update create-release scripts; rotted Key: HBASE-25354 URL: https://issues.apache.org/jira/browse/HBASE-25354 Project: HBase Issue Type: Bug

[jira] [Created] (HBASE-25353) [Flakey Tests] branch-2 TestShutdownBackupMaster

2020-12-02 Thread Michael Stack (Jira)
Michael Stack created HBASE-25353: - Summary: [Flakey Tests] branch-2 TestShutdownBackupMaster Key: HBASE-25353 URL: https://issues.apache.org/jira/browse/HBASE-25353 Project: HBase Issue

Re: Coprocs and Off-Heap Writes

2020-12-02 Thread ramkrishna vasudevan
Hi Anoop has clearly answered I believe. the short answer is in your CP it is better you copy/clone the cells so that there is no reference. I believe the Index related WAL codec in Phoenix was also trying to do something similar if I remember correctly. (I may be wrong though). Regards Ram On

Re: Coprocs and Off-Heap Writes

2020-12-02 Thread Anoop John
Hi Geoffrey, In case of off heap backed write path (RPC layer itself), the write payload is accepted into DBBs that we get from a pool. And cells will be created over this DBB. In case we add Tags in CPs, there will be a new Cell POJO created. But that will anyways refer to old POJO for all

[jira] [Created] (HBASE-25352) API compatibilty checker fails with "Argument list too long"

2020-12-02 Thread Andrew Kyle Purtell (Jira)
Andrew Kyle Purtell created HBASE-25352: --- Summary: API compatibilty checker fails with "Argument list too long" Key: HBASE-25352 URL: https://issues.apache.org/jira/browse/HBASE-25352 Project:

Re: DISCUSS: Remove hbase-backup from master?

2020-12-02 Thread mallik.v.ar...@gmail.com
On Tue, Dec 1, 2020 at 11:26 PM Stack wrote: > On Tue, Dec 1, 2020 at 6:38 AM mallik.v.ar...@gmail.com < > mallik.v.ar...@gmail.com> wrote: > > > On Tue, Dec 1, 2020 at 7:34 PM Sean Busbey wrote: > > > > > One reason for moving it out of core is that at some point we will have > > > hbase 3

Re: [DISCUSS] Consider truncating CHANGES.md files on new release branches

2020-12-02 Thread Nick Dimiduk
On Wed, Dec 2, 2020 at 11:16 AM Andrew Purtell wrote: > Like this? > > https://gist.github.com/apurtell/f5959f36b0b13d5e92f35b22549020cc > +1 ! On Wed, Dec 2, 2020 at 10:04 AM Nick Dimiduk wrote: > >> On Tue, Dec 1, 2020 at 12:16 PM Andrew Purtell >> wrote: >> >>> I think by git tag would

Coprocs and Off-Heap Writes

2020-12-02 Thread Geoffrey Jacoby
I'm code-reviewing a Phoenix PR [1] right now, which adds Tags to a mutation's Cells in a coproc. A question has come up regarding coprocs and the optional off-heaping of the write path in HBase 2.x and up. For what parts of the write path (and hence, which coproc hooks) is it safe to change the

Re: [DISCUSS] Consider truncating CHANGES.md files on new release branches

2020-12-02 Thread Stack
On Wed, Dec 2, 2020 at 11:16 AM Andrew Purtell wrote: > Like this? > > https://gist.github.com/apurtell/f5959f36b0b13d5e92f35b22549020cc > > > Looks good to me. 2.3.0 CHANGELOG doesn't display because it is too big -- it is an accumulation of all changes up to 2.3 (good IMO) whereas 2.2+2.1,

Heads up, new release branch branch-2.4

2020-12-02 Thread Andrew Purtell
I have branched branch-2.4, only locally for now, at commit 9cc2f7624817f256bc7984662d2f6532bc5eb033 (HBASE-25349 [Flakey Tests] branch-2 TestRefreshRecoveredReplication ...) Not pushed up yet. Waiting to fine tune RC details for CHANGES.md. See thread "[DISCUSS] Consider truncating CHANGES.md

Re: [DISCUSS] Consider truncating CHANGES.md files on new release branches

2020-12-02 Thread Andrew Purtell
Like this? https://gist.github.com/apurtell/f5959f36b0b13d5e92f35b22549020cc On Wed, Dec 2, 2020 at 10:04 AM Nick Dimiduk wrote: > On Tue, Dec 1, 2020 at 12:16 PM Andrew Purtell > wrote: > >> I think by git tag would work. Given the URL can be different from the >> visible anchor text we

Re: [DISCUSS] Consider truncating CHANGES.md files on new release branches

2020-12-02 Thread Nick Dimiduk
On Tue, Dec 1, 2020 at 12:16 PM Andrew Purtell wrote: > I think by git tag would work. Given the URL can be different from the > visible anchor text we could use an exact git sha too, if there is concern > that tags might be changed either accidentally or intentionally in a way > that breaks

[jira] [Resolved] (HBASE-25349) [Flakey Tests] branch-2 TestRefreshRecoveredReplication.testReplicationRefreshSource:141 Waiting timed out after [60,000] msec

2020-12-02 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HBASE-25349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stack resolved HBASE-25349. --- Fix Version/s: 2.4.0 3.0.0-alpha-1 Hadoop Flags: Reviewed

[jira] [Created] (HBASE-25351) Backport HBASE-25246 to branch-1

2020-12-02 Thread Viraj Jasani (Jira)
Viraj Jasani created HBASE-25351: Summary: Backport HBASE-25246 to branch-1 Key: HBASE-25351 URL: https://issues.apache.org/jira/browse/HBASE-25351 Project: HBase Issue Type: Sub-task

[jira] [Resolved] (HBASE-25246) Backup/Restore hbase cell tags.

2020-12-02 Thread Andrew Kyle Purtell (Jira)
[ https://issues.apache.org/jira/browse/HBASE-25246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Kyle Purtell resolved HBASE-25246. - Fix Version/s: 2.4.0 3.0.0-alpha-1 Hadoop Flags:

[jira] [Created] (HBASE-25350) The scan command gives a row, but get does not have this row.

2020-12-02 Thread ClownfishYang (Jira)
ClownfishYang created HBASE-25350: - Summary: The scan command gives a row, but get does not have this row. Key: HBASE-25350 URL: https://issues.apache.org/jira/browse/HBASE-25350 Project: HBase