[jira] [Updated] (HBASE-10800) Use CellComparator instead of KVComparator
[ https://issues.apache.org/jira/browse/HBASE-10800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-10800: --- Attachment: HBASE-10800_16.patch Wraps long lines. Fixes checkstyle comments related to Unused Imports. Fixes javadoc warnings. CellComparator.compareKeyBasedOnColHint() I have added back the familyOffset and familyLength here because for cases where we get the compareKeyForNextRow the family offset and length should be 0 which we cannot get from the cell. Hence it is better we explicitly pass them there. Use CellComparator instead of KVComparator -- Key: HBASE-10800 URL: https://issues.apache.org/jira/browse/HBASE-10800 Project: HBase Issue Type: Sub-task Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0 Attachments: HBASE-10800_1.patch, HBASE-10800_11.patch, HBASE-10800_12.patch, HBASE-10800_13.patch, HBASE-10800_14.patch, HBASE-10800_15.patch, HBASE-10800_16.patch, HBASE-10800_2.patch, HBASE-10800_3.patch, HBASE-10800_4.patch, HBASE-10800_4.patch, HBASE-10800_5.patch, HBASE-10800_6.patch, HBASE-10800_7.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-10800) Use CellComparator instead of KVComparator
[ https://issues.apache.org/jira/browse/HBASE-10800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-10800: --- Status: Open (was: Patch Available) Use CellComparator instead of KVComparator -- Key: HBASE-10800 URL: https://issues.apache.org/jira/browse/HBASE-10800 Project: HBase Issue Type: Sub-task Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0 Attachments: HBASE-10800_1.patch, HBASE-10800_11.patch, HBASE-10800_12.patch, HBASE-10800_13.patch, HBASE-10800_14.patch, HBASE-10800_15.patch, HBASE-10800_2.patch, HBASE-10800_3.patch, HBASE-10800_4.patch, HBASE-10800_4.patch, HBASE-10800_5.patch, HBASE-10800_6.patch, HBASE-10800_7.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13071) Hbase Streaming Scan Feature
[ https://issues.apache.org/jira/browse/HBASE-13071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14491898#comment-14491898 ] stack commented on HBASE-13071: --- bq. the scans should be meaty, with large prefetches (we used 100-1000 records), and the per-record processing at the client side should be non-negligible What would you suggest then [~ebortnik] and [~eshcar]? Defaults in hbase are 30 rows at a time, not 1000. Would it make sense if this facility could be turned on by enabling a property on a Scan object? bq. We are not familiar with the PerformanceEvaluation tool Np. It is a coarse tool we've been using since early days to run loadings on hbase. See bin/hbase pe bq. Re/ auto-tuning, I believe this is a bit premature. Let's keep the code simple, and let the client control. The optimization does not necessarily need to be a default. I suggest auto-tune so the feature is useful more often than not. Regards it not needing to be the default, would be cool if user didn't have to go figure an opaque option to get this benefit. Let me try and repro the benefit seen in posted graphs. Thanks. Hbase Streaming Scan Feature Key: HBASE-13071 URL: https://issues.apache.org/jira/browse/HBASE-13071 Project: HBase Issue Type: New Feature Reporter: Eshcar Hillel Attachments: 99.eshcar.png, HBASE-13071_98_1.patch, HBASE-13071_trunk_1.patch, HBASE-13071_trunk_10.patch, HBASE-13071_trunk_2.patch, HBASE-13071_trunk_3.patch, HBASE-13071_trunk_4.patch, HBASE-13071_trunk_5.patch, HBASE-13071_trunk_6.patch, HBASE-13071_trunk_7.patch, HBASE-13071_trunk_8.patch, HBASE-13071_trunk_9.patch, HBaseStreamingScanDesign.pdf, HbaseStreamingScanEvaluation.pdf, HbaseStreamingScanEvaluationwithMultipleClients.pdf, gc.delay.png, gc.eshcar.png, gc.png, hits.delay.png, hits.eshcar.png, hits.png, latency.delay.png, latency.png, network.png A scan operation iterates over all rows of a table or a subrange of the table. The synchronous nature in which the data is served at the client side hinders the speed the application traverses the data: it increases the overall processing time, and may cause a great variance in the times the application waits for the next piece of data. The scanner next() method at the client side invokes an RPC to the regionserver and then stores the results in a cache. The application can specify how many rows will be transmitted per RPC; by default this is set to 100 rows. The cache can be considered as a producer-consumer queue, where the hbase client pushes the data to the queue and the application consumes it. Currently this queue is synchronous, i.e., blocking. More specifically, when the application consumed all the data from the cache --- so the cache is empty --- the hbase client retrieves additional data from the server and re-fills the cache with new data. During this time the application is blocked. Under the assumption that the application processing time can be balanced by the time it takes to retrieve the data, an asynchronous approach can reduce the time the application is waiting for data. We attach a design document. We also have a patch that is based on a private branch, and some evaluation results of this code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13455) Procedure V2 - master truncate table
[
https://issues.apache.org/jira/browse/HBASE-13455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14491395#comment-14491395
]
Hadoop QA commented on HBASE-13455:
---
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12724799/HBASE-13455-v1.patch
against master branch at commit e75c6201c69e57416525135a397a971ad4d1b902.
ATTACHMENT ID: 12724799
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 11 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.1 2.5.2 2.6.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/13676//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/13676//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/13676//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/13676//console
This message is automatically generated.
Procedure V2 - master truncate table
Key: HBASE-13455
URL: https://issues.apache.org/jira/browse/HBASE-13455
Project: HBase
Issue Type: Sub-task
Components: master
Affects Versions: 2.0.0, 1.1.0
Reporter: Matteo Bertozzi
Assignee: Matteo Bertozzi
Priority: Minor
Fix For: 2.0.0
Attachments: HBASE-13455-v0.patch, HBASE-13455-v1.patch
master side, part of HBASE-12439
and replaces the truncate table handlers with the procedure version.
https://reviews.apache.org/r/33102
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13455) Procedure V2 - master truncate table
[ https://issues.apache.org/jira/browse/HBASE-13455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Bertozzi updated HBASE-13455: Attachment: HBASE-13455-v1.patch Procedure V2 - master truncate table Key: HBASE-13455 URL: https://issues.apache.org/jira/browse/HBASE-13455 Project: HBase Issue Type: Sub-task Components: master Affects Versions: 2.0.0, 1.1.0 Reporter: Matteo Bertozzi Assignee: Matteo Bertozzi Priority: Minor Fix For: 2.0.0 Attachments: HBASE-13455-v0.patch, HBASE-13455-v1.patch master side, part of HBASE-12439 and replaces the truncate table handlers with the procedure version. https://reviews.apache.org/r/33102 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13455) Procedure V2 - master truncate table
[ https://issues.apache.org/jira/browse/HBASE-13455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Bertozzi updated HBASE-13455: Attachment: (was: HBASE-13455-v1.patch) Procedure V2 - master truncate table Key: HBASE-13455 URL: https://issues.apache.org/jira/browse/HBASE-13455 Project: HBase Issue Type: Sub-task Components: master Affects Versions: 2.0.0, 1.1.0 Reporter: Matteo Bertozzi Assignee: Matteo Bertozzi Priority: Minor Fix For: 2.0.0 Attachments: HBASE-13455-v0.patch, HBASE-13455-v1.patch master side, part of HBASE-12439 and replaces the truncate table handlers with the procedure version. https://reviews.apache.org/r/33102 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13202) Procedure v2 - core framework
[ https://issues.apache.org/jira/browse/HBASE-13202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Bertozzi updated HBASE-13202: Attachment: ProcedureV2-overview.pdf HBASE-13203-v2-branch_1.patch Procedure v2 - core framework - Key: HBASE-13202 URL: https://issues.apache.org/jira/browse/HBASE-13202 Project: HBase Issue Type: Sub-task Components: master Affects Versions: 2.0.0, 1.1.0 Reporter: Matteo Bertozzi Assignee: Matteo Bertozzi Fix For: 2.0.0 Attachments: HBASE-13202-v0-hbase-12439.patch, HBASE-13202-v1-hbase-12439.patch, HBASE-13202-v2.patch, HBASE-13203-v2-branch_1.patch, ProcedureV2-overview.pdf core package, part of HBASE-12439 this is just the proc-v2 submodule. it depends only on hbase-common. https://reviews.apache.org/r/27703/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13344) Add enforcer rule that matches our JDK support statement
[ https://issues.apache.org/jira/browse/HBASE-13344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Warhaftig updated HBASE-13344: --- Affects Version/s: 2.0.0 Status: Patch Available (was: Open) Submitted patch 'HBASE-13344-master.patch' to add dependency enforcer rule to master. Will cherry-pick to other branches if approved. Add enforcer rule that matches our JDK support statement Key: HBASE-13344 URL: https://issues.apache.org/jira/browse/HBASE-13344 Project: HBase Issue Type: Improvement Components: build Affects Versions: 2.0.0 Reporter: Sean Busbey Priority: Minor Labels: beginner, maven Fix For: 2.0.0 Attachments: HBASE-13344-master.patch The [ref guide gives a list of JDKs that we expect our hbase versions to work with at runtime|http://hbase.apache.org/book.html#basic.prerequisites]. Let's add in the extra-enforcer-rules mojo and start using [the bytecode version rule|http://mojo.codehaus.org/extra-enforcer-rules/enforceBytecodeVersion.html] to make sure that the result of our builds on a given branch won't fail out because of a misconfigured target jdk version (or a dependency that targets a later jdk). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13344) Add enforcer rule that matches our JDK support statement
[ https://issues.apache.org/jira/browse/HBASE-13344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Warhaftig updated HBASE-13344: --- Attachment: HBASE-13344-master.patch Add enforcer rule that matches our JDK support statement Key: HBASE-13344 URL: https://issues.apache.org/jira/browse/HBASE-13344 Project: HBase Issue Type: Improvement Components: build Affects Versions: 2.0.0 Reporter: Sean Busbey Priority: Minor Labels: beginner, maven Fix For: 2.0.0 Attachments: HBASE-13344-master.patch The [ref guide gives a list of JDKs that we expect our hbase versions to work with at runtime|http://hbase.apache.org/book.html#basic.prerequisites]. Let's add in the extra-enforcer-rules mojo and start using [the bytecode version rule|http://mojo.codehaus.org/extra-enforcer-rules/enforceBytecodeVersion.html] to make sure that the result of our builds on a given branch won't fail out because of a misconfigured target jdk version (or a dependency that targets a later jdk). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13344) Add enforcer rule that matches our JDK support statement
[
https://issues.apache.org/jira/browse/HBASE-13344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14491747#comment-14491747
]
Hadoop QA commented on HBASE-13344:
---
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12724841/HBASE-13344-master.patch
against master branch at commit e75c6201c69e57416525135a397a971ad4d1b902.
ATTACHMENT ID: 12724841
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation, build,
or dev-support patch that doesn't require tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.1 2.5.2 2.6.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/13677//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/13677//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/13677//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/13677//console
This message is automatically generated.
Add enforcer rule that matches our JDK support statement
Key: HBASE-13344
URL: https://issues.apache.org/jira/browse/HBASE-13344
Project: HBase
Issue Type: Improvement
Components: build
Affects Versions: 2.0.0
Reporter: Sean Busbey
Priority: Minor
Labels: beginner, maven
Fix For: 2.0.0
Attachments: HBASE-13344-master.patch
The [ref guide gives a list of JDKs that we expect our hbase versions to work
with at runtime|http://hbase.apache.org/book.html#basic.prerequisites].
Let's add in the extra-enforcer-rules mojo and start using [the bytecode
version
rule|http://mojo.codehaus.org/extra-enforcer-rules/enforceBytecodeVersion.html]
to make sure that the result of our builds on a given branch won't fail out
because of a misconfigured target jdk version (or a dependency that targets a
later jdk).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
