[jira] [Updated] (HBASE-21362) Disable printing of stack-trace in shell when quotas are violated

[ https://issues.apache.org/jira/browse/HBASE-21362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-21362: --- Attachment: (was: hbase-21362.master.001.patch) > Disable printing of stack-trace in shell when quotas

[jira] [Work started] (HBASE-21362) Disable printing of stack-trace in shell when quotas are violated

[ https://issues.apache.org/jira/browse/HBASE-21362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-21362 started by Sakthi. -- > Disable printing of stack-trace in shell when quotas are violated >

[jira] [Updated] (HBASE-21362) Disable printing of stack-trace in shell when quotas are violated

[ https://issues.apache.org/jira/browse/HBASE-21362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-21362: --- Attachment: hbase-21362.master.001.patch > Disable printing of stack-trace in shell when quotas are

[jira] [Work started] (HBASE-21361) Disable printing of stack-trace in shell when quotas are not enabled

[ https://issues.apache.org/jira/browse/HBASE-21361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-21361 started by Sakthi. -- > Disable printing of stack-trace in shell when quotas are not enabled >

[jira] [Commented] (HBASE-21620) Problem in scan query when using more than one column prefix filter in some cases.

[ https://issues.apache.org/jira/browse/HBASE-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726494#comment-16726494 ] Mohamed Mohideen Meeran commented on HBASE-21620: - [~openinx] Can you please tell for

[jira] [Updated] (HBASE-21588) Procedure v2 wal splitting implementation

[ https://issues.apache.org/jira/browse/HBASE-21588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jingyun Tian updated HBASE-21588: - Attachment: HBASE-21588.master.008.patch > Procedure v2 wal splitting implementation >

[jira] [Commented] (HBASE-21620) Problem in scan query when using more than one column prefix filter in some cases.

[ https://issues.apache.org/jira/browse/HBASE-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726482#comment-16726482 ] Zheng Hu commented on HBASE-21620: -- The TestRegionServerAbortTimeout is unrelated to this patch, and

[jira] [Commented] (HBASE-21620) Problem in scan query when using more than one column prefix filter in some cases.

[ https://issues.apache.org/jira/browse/HBASE-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726468#comment-16726468 ] Hadoop QA commented on HBASE-21620: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Updated] (HBASE-21618) Scan with the same startRow(inclusive=true) and stopRow(inclusive=false) returns one result

[ https://issues.apache.org/jira/browse/HBASE-21618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-21618: --- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-1 and

[jira] [Commented] (HBASE-21618) Scan with the same startRow(inclusive=true) and stopRow(inclusive=false) returns one result

[ https://issues.apache.org/jira/browse/HBASE-21618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726459#comment-16726459 ] Hadoop QA commented on HBASE-21618: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (HBASE-21401) Sanity check when constructing the KeyValue

[ https://issues.apache.org/jira/browse/HBASE-21401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726452#comment-16726452 ] Zheng Hu commented on HBASE-21401: -- bq. Please fix checkstyle on commit. Add a release note too saying

[jira] [Commented] (HBASE-21610) numOpenConnections metric is set to -1 when zero server channel exist

[ https://issues.apache.org/jira/browse/HBASE-21610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726436#comment-16726436 ] Hudson commented on HBASE-21610: Results for branch branch-2.1 [build #700 on

[jira] [Commented] (HBASE-21401) Sanity check when constructing the KeyValue

[ https://issues.apache.org/jira/browse/HBASE-21401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726430#comment-16726430 ] stack commented on HBASE-21401: --- +1 let safety win. Let’s address the overparsing in other follow on

[jira] [Commented] (HBASE-21401) Sanity check when constructing the KeyValue

[ https://issues.apache.org/jira/browse/HBASE-21401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726432#comment-16726432 ] stack commented on HBASE-21401: --- Please fix checkstyle on commit. Add a release note too saying what this

[jira] [Updated] (HBASE-21620) Problem in scan query when using more than one column prefix filter in some cases.

[ https://issues.apache.org/jira/browse/HBASE-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-21620: - Attachment: HBASE-21620.v2.patch > Problem in scan query when using more than one column prefix filter

[jira] [Updated] (HBASE-21618) Scan with the same startRow(inclusive=true) and stopRow(inclusive=false) returns one result

[ https://issues.apache.org/jira/browse/HBASE-21618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-21618: --- Attachment: HBASE-21618.branch-1.001.patch > Scan with the same startRow(inclusive=true)

[jira] [Commented] (HBASE-21618) Scan with the same startRow(inclusive=true) and stopRow(inclusive=false) returns one result

[ https://issues.apache.org/jira/browse/HBASE-21618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726405#comment-16726405 ] Guanghao Zhang commented on HBASE-21618: Pushed to branch-2.0+. And add a pacth for branch-1.

[jira] [Commented] (HBASE-21401) Sanity check when constructing the KeyValue

[ https://issues.apache.org/jira/browse/HBASE-21401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726398#comment-16726398 ] Zheng Hu commented on HBASE-21401: -- bq. I don't like that we are adding friction to KV making because

[jira] [Commented] (HBASE-21626) log the regions blocking WAL from being archived

[ https://issues.apache.org/jira/browse/HBASE-21626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726382#comment-16726382 ] Hadoop QA commented on HBASE-21626: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (HBASE-21620) Problem in scan query when using more than one column prefix filter in some cases.

[ https://issues.apache.org/jira/browse/HBASE-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726381#comment-16726381 ] Zheng Hu commented on HBASE-21620: -- It's a critial bug. when I run the UT without the fix, my

[jira] [Commented] (HBASE-21401) Sanity check when constructing the KeyValue

[ https://issues.apache.org/jira/browse/HBASE-21401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726378#comment-16726378 ] stack commented on HBASE-21401: --- [~openinx] As you can tell, I don't like that we are adding friction to

[jira] [Commented] (HBASE-21620) Problem in scan query when using more than one column prefix filter in some cases.

[ https://issues.apache.org/jira/browse/HBASE-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726372#comment-16726372 ] stack commented on HBASE-21620: --- This looks like a great fix but it looks risky putting it into branch-2.0

[jira] [Updated] (HBASE-21620) Problem in scan query when using more than one column prefix filter in some cases.

[ https://issues.apache.org/jira/browse/HBASE-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-21620: -- Fix Version/s: (was: 2.0.4) (was: 2.1.2) > Problem in scan query when using more

[jira] [Commented] (HBASE-21618) Scan with the same startRow(inclusive=true) and stopRow(inclusive=false) returns one result

[ https://issues.apache.org/jira/browse/HBASE-21618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726368#comment-16726368 ] stack commented on HBASE-21618: --- +1 Agree makes no sense. Nice cleanup [~zghaobac] around those test for a

[jira] [Updated] (HBASE-21610) numOpenConnections metric is set to -1 when zero server channel exist

[ https://issues.apache.org/jira/browse/HBASE-21610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-21610: -- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.0.4 2.1.2

[jira] [Commented] (HBASE-21610) numOpenConnections metric is set to -1 when zero server channel exist

[ https://issues.apache.org/jira/browse/HBASE-21610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726339#comment-16726339 ] Hadoop QA commented on HBASE-21610: --- | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote ||

[jira] [Commented] (HBASE-21020) Determine WAL API changes for replication

[ https://issues.apache.org/jira/browse/HBASE-21020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726319#comment-16726319 ] Hadoop QA commented on HBASE-21020: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (HBASE-21614) RIT recovery with ServerCrashProcedure doesn't account for all regions

[ https://issues.apache.org/jira/browse/HBASE-21614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726263#comment-16726263 ] Hadoop QA commented on HBASE-21614: --- | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote ||

[jira] [Updated] (HBASE-21623) ServerCrashProcedure can stomp on a RIT for a wrong server

[ https://issues.apache.org/jira/browse/HBASE-21623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HBASE-21623: - Summary: ServerCrashProcedure can stomp on a RIT for a wrong server (was:

[jira] [Created] (HBASE-21627) race condition between a recovered RIT for meta replica, and master startup

Sergey Shelukhin created HBASE-21627: Summary: race condition between a recovered RIT for meta replica, and master startup Key: HBASE-21627 URL: https://issues.apache.org/jira/browse/HBASE-21627

[jira] [Updated] (HBASE-21624) master startup should not wait on assigning meta replicas

[ https://issues.apache.org/jira/browse/HBASE-21624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HBASE-21624: - Description: Due to some other bug, a meta replica is stuck in transition forever.

[jira] [Updated] (HBASE-21624) master startup should not wait (or die) on assigning meta replicas

[ https://issues.apache.org/jira/browse/HBASE-21624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HBASE-21624: - Summary: master startup should not wait (or die) on assigning meta replicas (was:

[jira] [Created] (HBASE-21626) log the regions blocking WAL from being archived

Sergey Shelukhin created HBASE-21626: Summary: log the regions blocking WAL from being archived Key: HBASE-21626 URL: https://issues.apache.org/jira/browse/HBASE-21626 Project: HBase

[jira] [Updated] (HBASE-21626) log the regions blocking WAL from being archived

[ https://issues.apache.org/jira/browse/HBASE-21626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HBASE-21626: - Status: Patch Available (was: Open) > log the regions blocking WAL from being archived

[jira] [Updated] (HBASE-21626) log the regions blocking WAL from being archived

[ https://issues.apache.org/jira/browse/HBASE-21626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HBASE-21626: - Attachment: HBASE-21626.patch > log the regions blocking WAL from being archived >

[jira] [Updated] (HBASE-21610) numOpenConnections metric is set to -1 when zero server channel exist

[ https://issues.apache.org/jira/browse/HBASE-21610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-21610: -- Attachment: HBASE-21610.patch > numOpenConnections metric is set to -1 when zero server channel exist >

[jira] [Comment Edited] (HBASE-21625) a runnable procedure v2 does not run

[ https://issues.apache.org/jira/browse/HBASE-21625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726213#comment-16726213 ] Sergey Shelukhin edited comment on HBASE-21625 at 12/20/18 8:54 PM:

[jira] [Commented] (HBASE-21625) a runnable procedure v2 does not run

[ https://issues.apache.org/jira/browse/HBASE-21625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726213#comment-16726213 ] Sergey Shelukhin commented on HBASE-21625: -- Looked a little bit at scheduling... that is much

[jira] [Updated] (HBASE-21625) a runnable procedure v2 does not run

[ https://issues.apache.org/jira/browse/HBASE-21625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HBASE-21625: - Description: This is on master snapshot as of a few weeks ago. Haven't looked at the

[jira] [Updated] (HBASE-21625) a runnable procedure v2 does not run

[ https://issues.apache.org/jira/browse/HBASE-21625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HBASE-21625: - Description: This is on master snapshot as of a few weeks ago. Haven't looked at the

[jira] [Updated] (HBASE-21625) a runnable procedure v2 does not run

[ https://issues.apache.org/jira/browse/HBASE-21625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HBASE-21625: - Description: This is on master as of a few weeks ago. Haven't looked at the code much

[jira] [Updated] (HBASE-21625) a runnable procedure v2 does not run

[ https://issues.apache.org/jira/browse/HBASE-21625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HBASE-21625: - Description: This is on master snapshot as of a few weeks ago. Haven't looked at the

[jira] [Commented] (HBASE-21625) a runnable procedure v2 does not run

[ https://issues.apache.org/jira/browse/HBASE-21625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726193#comment-16726193 ] Sergey Shelukhin commented on HBASE-21625: -- cc [~mbertozzi] > a runnable procedure v2 does not

[jira] [Updated] (HBASE-21625) a runnable procedure v2 does not run

[ https://issues.apache.org/jira/browse/HBASE-21625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HBASE-21625: - Description: This is on master as of a few weeks ago. Haven't looked at the code much

[jira] [Created] (HBASE-21625) a runnable procedure v2 does not run

Sergey Shelukhin created HBASE-21625: Summary: a runnable procedure v2 does not run Key: HBASE-21625 URL: https://issues.apache.org/jira/browse/HBASE-21625 Project: HBase Issue Type: Bug

[jira] [Created] (HBASE-21624) master startup should not sleep on assigning meta replicas

Sergey Shelukhin created HBASE-21624: Summary: master startup should not sleep on assigning meta replicas Key: HBASE-21624 URL: https://issues.apache.org/jira/browse/HBASE-21624 Project: HBase

[jira] [Updated] (HBASE-21624) master startup should not wait on assigning meta replicas

[ https://issues.apache.org/jira/browse/HBASE-21624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HBASE-21624: - Summary: master startup should not wait on assigning meta replicas (was: master

[jira] [Commented] (HBASE-21614) RIT recovery with ServerCrashProcedure doesn't account for all regions

[ https://issues.apache.org/jira/browse/HBASE-21614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726163#comment-16726163 ] Sergey Shelukhin commented on HBASE-21614: -- Cannot repro either test failure locally, and they

[jira] [Updated] (HBASE-21614) RIT recovery with ServerCrashProcedure doesn't account for all regions

[ https://issues.apache.org/jira/browse/HBASE-21614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HBASE-21614: - Attachment: HBASE-21614.master.002.patch > RIT recovery with ServerCrashProcedure

[jira] [Updated] (HBASE-21020) Determine WAL API changes for replication

[ https://issues.apache.org/jira/browse/HBASE-21020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated HBASE-21020: -- Attachment: HBASE-21020.HBASE-20952.005.patch > Determine WAL API changes for replication >

[jira] [Commented] (HBASE-21020) Determine WAL API changes for replication

[ https://issues.apache.org/jira/browse/HBASE-21020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726110#comment-16726110 ] Ankit Singhal commented on HBASE-21020: --- Hopefully, everything should be fine now. :) > Determine

[jira] [Commented] (HBASE-21620) Problem in scan query when using more than one column prefix filter in some cases.

[ https://issues.apache.org/jira/browse/HBASE-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726064#comment-16726064 ] Hadoop QA commented on HBASE-21620: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (HBASE-21596) HBase Shell "delete" command can cause older versions to be shown even if VERSIONS is configured as 1

[ https://issues.apache.org/jira/browse/HBASE-21596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726027#comment-16726027 ] Wellington Chevreuil commented on HBASE-21596: -- Actually real issue is that scanners are

[jira] [Commented] (HBASE-21588) Procedure v2 wal splitting implementation

[ https://issues.apache.org/jira/browse/HBASE-21588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725920#comment-16725920 ] Hadoop QA commented on HBASE-21588: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (HBASE-21620) Problem in scan query when using more than one column prefix filter in some cases.

[ https://issues.apache.org/jira/browse/HBASE-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725882#comment-16725882 ] Zheng Hu commented on HBASE-21620: -- Discussed with Guanghao, we can use the preivous return code and

[jira] [Updated] (HBASE-21620) Problem in scan query when using more than one column prefix filter in some cases.

[ https://issues.apache.org/jira/browse/HBASE-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-21620: - Attachment: HBASE-21620.v1.patch > Problem in scan query when using more than one column prefix filter

[jira] [Commented] (HBASE-21620) Problem in scan query when using more than one column prefix filter in some cases.

[ https://issues.apache.org/jira/browse/HBASE-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725868#comment-16725868 ] Hadoop QA commented on HBASE-21620: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (HBASE-21512) Introduce an AsyncClusterConnection and replace the usage of ClusterConnection

[ https://issues.apache.org/jira/browse/HBASE-21512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725848#comment-16725848 ] Hudson commented on HBASE-21512: Results for branch HBASE-21512 [build #23 on

[jira] [Commented] (HBASE-21588) Procedure v2 wal splitting implementation

[ https://issues.apache.org/jira/browse/HBASE-21588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725826#comment-16725826 ] Hadoop QA commented on HBASE-21588: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (HBASE-21618) Scan with the same startRow(inclusive=true) and stopRow(inclusive=false) returns one result

[ https://issues.apache.org/jira/browse/HBASE-21618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725809#comment-16725809 ] Hadoop QA commented on HBASE-21618: --- | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote ||

[jira] [Commented] (HBASE-21618) Scan with the same startRow(inclusive=true) and stopRow(inclusive=false) returns one result

[ https://issues.apache.org/jira/browse/HBASE-21618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725800#comment-16725800 ] Hadoop QA commented on HBASE-21618: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (HBASE-21572) The "progress" object in "Compactor" is not thread-safe, this may cause the misleading progress information on the web UI.

[ https://issues.apache.org/jira/browse/HBASE-21572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725798#comment-16725798 ] Hadoop QA commented on HBASE-21572: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (HBASE-21621) Reversed scan does not return expected number of rows

[ https://issues.apache.org/jira/browse/HBASE-21621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725774#comment-16725774 ] Hadoop QA commented on HBASE-21621: --- | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote ||

[jira] [Commented] (HBASE-21620) Problem in scan query when using more than one column prefix filter in some cases.

[ https://issues.apache.org/jira/browse/HBASE-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725742#comment-16725742 ] Mohamed Mohideen Meeran commented on HBASE-21620: - Thanks [~openinx]. It is working in

[jira] [Updated] (HBASE-21588) Procedure v2 wal splitting implementation

[ https://issues.apache.org/jira/browse/HBASE-21588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jingyun Tian updated HBASE-21588: - Attachment: HBASE-21588.master.006.patch > Procedure v2 wal splitting implementation >

[jira] [Updated] (HBASE-21588) Procedure v2 wal splitting implementation

[ https://issues.apache.org/jira/browse/HBASE-21588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jingyun Tian updated HBASE-21588: - Attachment: HBASE-21588.master.007.patch > Procedure v2 wal splitting implementation >

[jira] [Updated] (HBASE-21617) HBase Bytes.putBigDecimal error

[ https://issues.apache.org/jira/browse/HBASE-21617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] apcahephoenix updated HBASE-21617: -- Attachment: (was: TestBytes.java) > HBase Bytes.putBigDecimal error >

[jira] [Comment Edited] (HBASE-21617) HBase Bytes.putBigDecimal error

[ https://issues.apache.org/jira/browse/HBASE-21617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725720#comment-16725720 ] apcahephoenix edited comment on HBASE-21617 at 12/20/18 9:50 AM: - Thanks

[jira] [Updated] (HBASE-21617) HBase Bytes.putBigDecimal error

[ https://issues.apache.org/jira/browse/HBASE-21617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] apcahephoenix updated HBASE-21617: -- Attachment: (was: Bytes.java) > HBase Bytes.putBigDecimal error >

[jira] [Commented] (HBASE-21617) HBase Bytes.putBigDecimal error

[ https://issues.apache.org/jira/browse/HBASE-21617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725720#comment-16725720 ] apcahephoenix commented on HBASE-21617: --- Thanks Zheng Hu, reviews link is

[jira] [Updated] (HBASE-21617) HBase Bytes.putBigDecimal error

[ https://issues.apache.org/jira/browse/HBASE-21617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] apcahephoenix updated HBASE-21617: -- Attachment: TestBytes_HBASE_21617.patch Bytes_HBASE_21617.patch > HBase

[jira] [Updated] (HBASE-21572) The "progress" object in "Compactor" is not thread-safe, this may cause the misleading progress information on the web UI.

[ https://issues.apache.org/jira/browse/HBASE-21572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lixiaobao updated HBASE-21572: -- Attachment: (was: HBASE-21572.patch) > The "progress" object in "Compactor" is not thread-safe,

[jira] [Updated] (HBASE-21572) The "progress" object in "Compactor" is not thread-safe, this may cause the misleading progress information on the web UI.

[ https://issues.apache.org/jira/browse/HBASE-21572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lixiaobao updated HBASE-21572: -- Attachment: HBASE-21572.patch Status: Patch Available (was: Open) > The "progress" object

[jira] [Updated] (HBASE-21572) The "progress" object in "Compactor" is not thread-safe, this may cause the misleading progress information on the web UI.

[ https://issues.apache.org/jira/browse/HBASE-21572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lixiaobao updated HBASE-21572: -- Status: Open (was: Patch Available) > The "progress" object in "Compactor" is not thread-safe, this

[jira] [Updated] (HBASE-21620) Problem in scan query when using more than one column prefix filter in some cases.

[ https://issues.apache.org/jira/browse/HBASE-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-21620: - Affects Version/s: 2.0.4 2.1.2 2.2.0

[jira] [Commented] (HBASE-21618) Scan with the same startRow(inclusive=true) and stopRow(inclusive=false) returns one result

[ https://issues.apache.org/jira/browse/HBASE-21618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725684#comment-16725684 ] Zheng Hu commented on HBASE-21618: -- [~stack], I thinks this fix should go in HBase2.0.4 & HBase2.1.2,

[jira] [Updated] (HBASE-21620) Problem in scan query when using more than one column prefix filter in some cases.

[ https://issues.apache.org/jira/browse/HBASE-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-21620: - Fix Version/s: 1.4.10 2.0.4 2.1.2 2.2.0

[jira] [Updated] (HBASE-21620) Problem in scan query when using more than one column prefix filter in some cases.

[ https://issues.apache.org/jira/browse/HBASE-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-21620: - Attachment: (was: HBASE-21620.branch-1.patch) > Problem in scan query when using more than one

[jira] [Updated] (HBASE-21618) Scan with the same startRow(inclusive=true) and stopRow(inclusive=false) returns one result

[ https://issues.apache.org/jira/browse/HBASE-21618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-21618: - Fix Version/s: (was: 2.0.5) (was: 2.1.3) 2.0.4

[jira] [Commented] (HBASE-21620) Problem in scan query when using more than one column prefix filter in some cases.

[ https://issues.apache.org/jira/browse/HBASE-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725670#comment-16725670 ] Zheng Hu commented on HBASE-21620: -- [~mohamed.meeran], I think HBASE-201620.branch-1.patch can help

[jira] [Updated] (HBASE-21620) Problem in scan query when using more than one column prefix filter in some cases.

[ https://issues.apache.org/jira/browse/HBASE-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-21620: - Attachment: HBASE-21620.branch-1.patch > Problem in scan query when using more than one column prefix

[jira] [Updated] (HBASE-21620) Problem in scan query when using more than one column prefix filter in some cases.

[ https://issues.apache.org/jira/browse/HBASE-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-21620: - Attachment: HBASE-21620.branch-1.patch > Problem in scan query when using more than one column prefix

[jira] [Updated] (HBASE-21621) Reversed scan does not return expected number of rows

[ https://issues.apache.org/jira/browse/HBASE-21621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-21621: --- Attachment: HBASE-21621.master.002.patch > Reversed scan does not return expected number

[jira] [Updated] (HBASE-21588) Procedure v2 wal splitting implementation

[ https://issues.apache.org/jira/browse/HBASE-21588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jingyun Tian updated HBASE-21588: - Attachment: HBASE-21588.master.005.patch > Procedure v2 wal splitting implementation >

[jira] [Assigned] (HBASE-21621) Reversed scan does not return expected number of rows

[ https://issues.apache.org/jira/browse/HBASE-21621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang reassigned HBASE-21621: -- Assignee: Guanghao Zhang > Reversed scan does not return expected number of rows >

[jira] [Updated] (HBASE-21618) Scan with the same startRow(inclusive=true) and stopRow(inclusive=false) returns one result

[ https://issues.apache.org/jira/browse/HBASE-21618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-21618: --- Attachment: HBASE-21618.master.002.patch > Scan with the same startRow(inclusive=true) and

[jira] [Commented] (HBASE-21621) Reversed scan does not return expected number of rows

[ https://issues.apache.org/jira/browse/HBASE-21621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725644#comment-16725644 ] Hadoop QA commented on HBASE-21621: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Updated] (HBASE-21618) Scan with the same startRow(inclusive=true) and stopRow(inclusive=false) returns one result

[ https://issues.apache.org/jira/browse/HBASE-21618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-21618: --- Attachment: HBASE-21618.master.003.patch > Scan with the same startRow(inclusive=true) and

[jira] [Assigned] (HBASE-21618) Scan with the same startRow(inclusive=true) and stopRow(inclusive=false) returns one result

[ https://issues.apache.org/jira/browse/HBASE-21618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang reassigned HBASE-21618: -- Assignee: Guanghao Zhang > Scan with the same startRow(inclusive=true) and