[jira] [Created] (HBASE-17844) Subset of HBASE-14614, Procedure v2: Core Assignment Manager

stack created HBASE-17844: - Summary: Subset of HBASE-14614, Procedure v2: Core Assignment Manager Key: HBASE-17844 URL: https://issues.apache.org/jira/browse/HBASE-17844 Project: HBase Issue Type:

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

Re: [DISCUSS] What are we going to call the releases leading up to HBase 2.0?

+1 on -alpha/-beta, and cannot wait to see an alpha1 out (smile) Best Regards, Yu On 29 March 2017 at 10:28, 张铎(Duo Zhang) wrote: > +1 on 2.0.0-alpha[x]/2.0.0-beta[x]. > > 2017-03-29 10:07 GMT+08:00 Andrew Purtell : > > > That settles it. :-) >

Re: How threads interact with each other in HBase

Hi Josh, Thanks a lot for your response and we really appreciate the effort you put in to help us. Following are responses to your comments: 1. We understand there is a block cache, and processing an RPC may only involve looking up the cache instead of going to HDFS. That's why we said "If the

Re: [DISCUSS] What are we going to call the releases leading up to HBase 2.0?

+1 on 2.0.0-alpha[x]/2.0.0-beta[x]. 2017-03-29 10:07 GMT+08:00 Andrew Purtell : > That settles it. :-) > > I'd also be cool with -alpha, -beta, etc. > > > On Mar 28, 2017, at 1:25 PM, Enis Söztutar wrote: > > > > I would automatically -1 any release

Re: [DISCUSS] What are we going to call the releases leading up to HBase 2.0?

That settles it. :-) I'd also be cool with -alpha, -beta, etc. > On Mar 28, 2017, at 1:25 PM, Enis Söztutar wrote: > > I would automatically -1 any release with a number like 1.99 regardless of > content. > > Semantic versioning which we are following already provides an

Re: [ANNOUNCE] - Welcome our new HBase committer Anastasia Braginsky

Congratulations! 2017-03-28 22:16 GMT+08:00 Kahlil Oppenheimer : > Congrats Anastasia! > > On Tue, Mar 28, 2017 at 9:50 AM Nick Dimiduk wrote: > > > Thank you for all your contributions Anastasia! > > > > On Mon, Mar 27, 2017 at 5:38 AM

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

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

[jira] [Resolved] (HBASE-17727) [C++] Make RespConverter work with RawAsyncTableImpl

[ https://issues.apache.org/jira/browse/HBASE-17727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar resolved HBASE-17727. --- Resolution: Fixed Fix Version/s: HBASE-14850 > [C++] Make RespConverter work with

Re: [DISCUSS] What are we going to call the releases leading up to HBase 2.0?

2.0.0-alpha / 2.0.0-beta sound good to me. On Tue, Mar 28, 2017 at 1:25 PM, Enis Söztutar wrote: > I would automatically -1 any release with a number like 1.99 regardless of > content. > > Semantic versioning which we are following already provides an answer for > this: >

[jira] [Resolved] (HBASE-17842) Reference book - HBase application integration test is not correct

[ https://issues.apache.org/jira/browse/HBASE-17842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser resolved HBASE-17842. Resolution: Invalid Agreed, Jan. [~iraj.hedayati], please feel free to contact Cloudera to report

Re: [DISCUSS] What are we going to call the releases leading up to HBase 2.0?

I'm partial to 2.0.0-alpha[x]/beta[x] * Conveys that it's 2.x (not 1.x) * Conveys "instability" * Doesn't buck Maven's view of the world (Maven is happy with a version string of 2.0.0-alpha) * Still enables a "2.0.0" later Sean Busbey wrote: Hi folks! What are folks opinions on how we name

Re: [DISCUSS] What are we going to call the releases leading up to HBase 2.0?

I would automatically -1 any release with a number like 1.99 regardless of content. Semantic versioning which we are following already provides an answer for this: http://semver.org/#spec-item-9 >From my experience as RM for 0.99.x series and 1.0.x series, I would suggest we do 2.0.0-alpha1 and

[DISCUSS] What are we going to call the releases leading up to HBase 2.0?

Hi folks! What are folks opinions on how we name releases leading up to HBase 2.0 that aren't quite done yet? For 1.0, we used 0.99 as a placeholder for "what we expect will be in 1.0 but is not yet ready for production use." That got us 0.99.0, 0.99.1, and 0.99.2 before we declared 1.0.0 ready

HBaseCon2017 Registration is now Open!

The HBaseCon West 2017 registration website is up [1]. Registration is no-charge (Courtesy of our gracious hosts). Space is limited so be sure to register early (This means YOU!, the HBase Community). Note, HBaseCon will be in Mountain View @ Google, NOT in San Francisco, on June 12th (The day

Re: How threads interact with each other in HBase

1.1 -> 2: don't forget about the block cache which can invalidate the need for any HDFS read. I think you're over-simplifying the write-path quite a bit. I'm not sure what you mean by an 'asynchronous write', but that doesn't exist at the HBase RPC layer as that would invalidate the

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

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

Re: [ANNOUNCE] - Welcome our new HBase committer Anastasia Braginsky

Thank you for all your contributions Anastasia! On Mon, Mar 27, 2017 at 5:38 AM ramkrishna vasudevan < ramkrishna.s.vasude...@gmail.com> wrote: > Hi All > > Welcome Anastasia Braginsky, one more female committer to HBase. She has > been active now for a while with her Compacting memstore feature

[jira] [Created] (HBASE-17843) JUnit test timed out in TestRegionReplicaFailover.java

Qilin Cao created HBASE-17843: - Summary: JUnit test timed out in TestRegionReplicaFailover.java Key: HBASE-17843 URL: https://issues.apache.org/jira/browse/HBASE-17843 Project: HBase Issue Type: