[jira] [Created] (HBASE-18662) The default values for many configuration items in the code are not consistent with hbase-default.xml

Yun Zhao created HBASE-18662: Summary: The default values for many configuration items in the code are not consistent with hbase-default.xml Key: HBASE-18662 URL: https://issues.apache.org/jira/browse/HBASE-18662

[jira] [Created] (HBASE-18664) netty-transport-native-epoll is not found using 2.0.0-alpha2

Miklos Csanady created HBASE-18664: -- Summary: netty-transport-native-epoll is not found using 2.0.0-alpha2 Key: HBASE-18664 URL: https://issues.apache.org/jira/browse/HBASE-18664 Project: HBase

[jira] [Created] (HBASE-18663) netty-transport-native-epoll is not found using 2.0.0-alpha2

Miklos Csanady created HBASE-18663: -- Summary: netty-transport-native-epoll is not found using 2.0.0-alpha2 Key: HBASE-18663 URL: https://issues.apache.org/jira/browse/HBASE-18663 Project: HBase

Different behavior in ScannerCallables

Hi, I noticed that the behavior of ReversedScannerCallable#prepare [1] and ScannerCallable#prepare [2] methods differ how they call RpcRetryingCallerWithReadReplicas.getRegionLocations method. The reversed scanner uses the 'reload' parameter directly as the first argument -

[jira] [Created] (HBASE-18665) ReversedScannerCallable invokes getRegionLocations incorrectly

Peter Somogyi created HBASE-18665: - Summary: ReversedScannerCallable invokes getRegionLocations incorrectly Key: HBASE-18665 URL: https://issues.apache.org/jira/browse/HBASE-18665 Project: HBase

Re: Different behavior in ScannerCallables

Please open a JIRA. On Wed, Aug 23, 2017 at 5:28 AM, Peter Somogyi wrote: > Hi, > > I noticed that the behavior of ReversedScannerCallable#prepare [1] > and ScannerCallable#prepare [2] methods differ how they > call RpcRetryingCallerWithReadReplicas.getRegionLocations

Tips for Migrating to Apache HBase on Amazon S3 from HDFS

Starting with Amazon EMR 5.2.0, you have the option to run Apache HBase on Amazon S3. Running HBase on S3 gives you several added benefits, including lower costs, data durability, and easier scalability. HBase provides several options that you can use to migrate and back

Re: Tips for Migrating to Apache HBase on Amazon S3 from HDFS

Sorry. I let this through. I should have blocked it. St.Ack On Wed, Aug 23, 2017 at 3:21 AM, RuthEvans wrote: > Starting with Amazon EMR 5.2.0, you have the option to run Apache HBase > on Amazon S3. Running HBase on S3 gives you > several added

Re: Tips for Migrating to Apache HBase on Amazon S3 from HDFS

bq. The following diagram summarizes the steps for each option I don't see diagram. Is this writing published somewhere ? On Wed, Aug 23, 2017 at 3:21 AM, RuthEvans wrote: > Starting with Amazon EMR 5.2.0, you have the option to run Apache HBase >

Re: Tips for Migrating to Apache HBase on Amazon S3 from HDFS

I believe it's https://aws.amazon.com/blogs/big-data/tips-for-migrating-to-apache-hbase-on-amazon-s3-from-hdfs/ On Wed, Aug 23, 2017 at 5:26 PM Ted Yu wrote: > bq. The following diagram summarizes the steps for each option > > I don't see diagram. > > Is this writing

[jira] [Reopened] (HBASE-18509) [HLC] Finishing cleanups

[ https://issues.apache.org/jira/browse/HBASE-18509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Patel reopened HBASE-18509: The refactoring messed up some of the tests that were mocking the clocks. I've submitted a patch that

[jira] [Created] (HBASE-18667) Disable error-prone for hbase-protocol-shaded

Mike Drob created HBASE-18667: - Summary: Disable error-prone for hbase-protocol-shaded Key: HBASE-18667 URL: https://issues.apache.org/jira/browse/HBASE-18667 Project: HBase Issue Type: Sub-task

Re: [DISCUSS] Merging Hybrid Logical Clocks with Master

Thanks Amit for continuing on the work. I am biased, but of course would like to see this merged back to master (and possibly make it to 2.0) once the issues are ironed out. We can eliminate a very large class of problems with a mathematically sound strategy. Enis On Tue, Aug 22, 2017 at 1:28

[jira] [Resolved] (HBASE-18321) [hbase-thirdparty] Fix generation of META-INF/DEPENDENCIES to include dependency list and versions

[ https://issues.apache.org/jira/browse/HBASE-18321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-18321. --- Resolution: Fixed Fix Version/s: 1.0.1 Pushed to master branch of hbase-thirdparty >

[jira] [Created] (HBASE-18668) Fix TestCellACLWithMultipleVersions failing

Amit Patel created HBASE-18668: -- Summary: Fix TestCellACLWithMultipleVersions failing Key: HBASE-18668 URL: https://issues.apache.org/jira/browse/HBASE-18668 Project: HBase Issue Type: Sub-task

[jira] [Created] (HBASE-18669) build failed on windows case of whoami return result which conatins "\"

Yechao Chen created HBASE-18669: --- Summary: build failed on windows case of whoami return result which conatins "\" Key: HBASE-18669 URL: https://issues.apache.org/jira/browse/HBASE-18669 Project: HBase

[VOTE] hbase-thirdparty project, first release candidate 1.0.1RC0

This is a minor update to hbase-thirdparty, our little side project of relocated popular includes such as guava, protobuf, and netty (See [1] for more on what hbase-thirdparty is). hbase-thirdparty 1.0.1RC0 is available at: https://dist.apache.org/repos/dist/dev/hbase/hbase-thirdparty/1.0.1RC0/

[jira] [Resolved] (HBASE-18669) build failed on windows case of whoami return result which conatins "\"

[ https://issues.apache.org/jira/browse/HBASE-18669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yechao Chen resolved HBASE-18669. - Resolution: Duplicate duplicate HBASE-18461 > build failed on windows case of whoami return

[jira] [Resolved] (HBASE-18664) netty-transport-native-epoll is not found using 2.0.0-alpha2

[ https://issues.apache.org/jira/browse/HBASE-18664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John resolved HBASE-18664. Resolution: Duplicate Duplicate of HBASE-18663 > netty-transport-native-epoll is not

[jira] [Created] (HBASE-18670) Add .DS_Store to .gitignore

Chia-Ping Tsai created HBASE-18670: -- Summary: Add .DS_Store to .gitignore Key: HBASE-18670 URL: https://issues.apache.org/jira/browse/HBASE-18670 Project: HBase Issue Type: Task

[jira] [Created] (HBASE-18666) [hbase-thirdparty] Exclude errorprone annotation com.google.errorprone.annotations.CanIgnoreReturnValue

stack created HBASE-18666: - Summary: [hbase-thirdparty] Exclude errorprone annotation com.google.errorprone.annotations.CanIgnoreReturnValue Key: HBASE-18666 URL: https://issues.apache.org/jira/browse/HBASE-18666

[jira] [Resolved] (HBASE-18313) [hbase-thirdparty] Produce src jars/tgz

[ https://issues.apache.org/jira/browse/HBASE-18313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-18313. --- Resolution: Fixed Assignee: Duo Zhang Hadoop Flags: Reviewed Fix Version/s: 1.0.1

[jira] [Resolved] (HBASE-18666) [hbase-thirdparty] Exclude errorprone annotation com.google.errorprone.annotations.CanIgnoreReturnValue

[ https://issues.apache.org/jira/browse/HBASE-18666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-18666. --- Resolution: Fixed Pushed to master in hbase-thirdparty > [hbase-thirdparty] Exclude errorprone annotation