Re: [DISCUSSION] Upgrading core dependencies

I was more on the thinking to avoid/reduce pulling in hbase dependencies into hbase-spark, and that maybe even hbase-spark can depend on shaded client and server -- it will be easier and more feasible if the shaded client becomes the default as you mentioned. Your idea that hbase-spark itself beco

[jira] [Reopened] (HBASE-17280) Add mechanism to control hbase cleaner behavior

[ https://issues.apache.org/jira/browse/HBASE-17280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Jadhav reopened HBASE-17280: - > Add mechanism to control hbase cleaner behavior > --- >

[jira] [Created] (HBASE-17615) Use nonce and procedure v2 for add/remove replication peer

Guanghao Zhang created HBASE-17615: -- Summary: Use nonce and procedure v2 for add/remove replication peer Key: HBASE-17615 URL: https://issues.apache.org/jira/browse/HBASE-17615 Project: HBase

Re: [DISCUSSION] Upgrading core dependencies

On Wed, Feb 8, 2017 at 10:24 AM Jerry He wrote: > Yeah. Talking about the dependency, the hbase-spark module already has > dependency on hbase-server (coming from the spark bulk load producing > hfiles). > This is not very good. We have to be careful not entangling it more. > Also, there is alre

[jira] [Reopened] (HBASE-17572) HMaster: Caught throwable while processing event C_M_MERGE_REGION (UndeclaredThrowableException)

[ https://issues.apache.org/jira/browse/HBASE-17572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell reopened HBASE-17572: Reopening. I was able to reproduce again with branch-1 (not branch-1.3). I misjudged this. In

Re: [DISCUSSION] Upgrading core dependencies

(late to the party, but..) +1 Nick sums this up better than I could have. Nick Dimiduk wrote: For the client: I'm a fan of shaded client modules by default and minimizing the exposure of that surface area of 3rd party libs (none, if possible). For example, Elastic Search has a similar set of ch

[jira] [Created] (HBASE-17614) Move Backup/Restore into separate module

Vladimir Rodionov created HBASE-17614: - Summary: Move Backup/Restore into separate module Key: HBASE-17614 URL: https://issues.apache.org/jira/browse/HBASE-17614 Project: HBase Issue Typ

Re: [DISCUSSION] Upgrading core dependencies

Yeah. Talking about the dependency, the hbase-spark module already has dependency on hbase-server (coming from the spark bulk load producing hfiles). This is not very good. We have to be careful not entangling it more. Also, there is already problem running the hbase-spark due to dependency confli

Successful: HBase Generate Website

Build status: Successful If successful, the website and docs have been generated. To update the live site, follow the instructions below. If failed, skip to the bottom of this email. Use the following commands to download the patch and apply it to a clean branch based on origin/asf-site. If yo

FINAL REMINDER: CFP for ApacheCon closes February 11th

Dear Apache Enthusiast, This is your FINAL reminder that the Call for Papers (CFP) for ApacheCon Miami is closing this weekend - February 11th. This is your final opportunity to submit a talk for consideration at this event. This year, we are running several mini conferences in conjunction with t

[jira] [Resolved] (HBASE-17607) Rest api for scan should return 404 when table not exists

[ https://issues.apache.org/jira/browse/HBASE-17607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-17607. --- Resolution: Duplicate Duplicated by HBASE-17603. > Rest api for scan should return 404 when table no

[jira] [Created] (HBASE-17613) avoid copy of family when initializing the FSWALEntry

ChiaPing Tsai created HBASE-17613: - Summary: avoid copy of family when initializing the FSWALEntry Key: HBASE-17613 URL: https://issues.apache.org/jira/browse/HBASE-17613 Project: HBase Issue