[NOTICE] jira lockdown

Hi folks! Just a quick heads-up that the ASF JIRA is currently locked down to counter a spam attack. Unfortunately, this lock down prevents our normal open-policy that allows anyone with a JIRA account to create, assign, and comment on issues. If you are caught up in this, please drop me a note

[VOTE] The 1st HBase 0.98.19 release candidate (RC0) is available

The 1st HBase 0.98.19 release candidate (RC0) is available for download at https://dist.apache.org/repos/dist/dev/hbase/0.98.19RC0/ and Maven artifacts are also available in the temporary repository https://repository.apache.org/content/repositories/orgapachehbase-1135 . The detailed source and

[jira] [Created] (HBASE-15698) Increment TimeRange not serialized to server

James Taylor created HBASE-15698: Summary: Increment TimeRange not serialized to server Key: HBASE-15698 URL: https://issues.apache.org/jira/browse/HBASE-15698 Project: HBase Issue Type: Bug

Re: Allowing clients to set priorities

I like the idea of reservations. So in this sort of scheme, there would be separate handler pools and a (hopefully, dynamic) configuration to route requests to a specific pool? Or maybe a default configuration set by the site file as done today, but with a runtime facility for adding more handler

Re: Google Summer Of Code 2016

Cool. Congrats. Enis On Fri, Apr 22, 2016 at 2:56 PM, Talat Uyarer wrote: > Hi all, > I really thankful for Apache HBase Community for sharing your ideas and > accepting my GSoC 2016 proposal. Specially > thankful for Enis to shared a good idea and Stack for volunteering to >

Re: Allowing clients to set priorities

Sure: For the first item. Yes that was implemented but there were a few issues. It is related to PHOENIX-938, but also had this desire back in the days at Flurry, I recall us always wishing for a way that we could reserve a group of handlers for specific users or tables. The other issue with

Re: Google Summer Of Code 2016

Hi all, I really thankful for Apache HBase Community for sharing your ideas and accepting my GSoC 2016 proposal. Specially thankful for Enis to shared a good idea and Stack for volunteering to mentor my project. I am really excited to work with you :) Talat On Apr 22, 2016 12:22 PM, "Elliott

[jira] [Created] (HBASE-15697) Excessive TestHRegion running time on branch-1

Andrew Purtell created HBASE-15697: -- Summary: Excessive TestHRegion running time on branch-1 Key: HBASE-15697 URL: https://issues.apache.org/jira/browse/HBASE-15697 Project: HBase Issue

Re: Branch for 1.3

bq. There are several patches Let us know the JIRA numbers. I can help with reviewing if needed. Cheers On Fri, Apr 22, 2016 at 2:18 PM, Mikhail Antonov wrote: > Last time I've tried to run 1.3 builds there were issues with balancer, > which are fixed now. There are

Re: Branch for 1.3

Last time I've tried to run 1.3 builds there were issues with balancer, which are fixed now. There are several patches I definitely would like to pull in, other than that I feel we are pretty close. I'll start spinning internal builds in a few days and if things look good will start preparing

[jira] [Resolved] (HBASE-15695) Ambari support for bucket caching parameter - hbase.bucketcache.ioengine

[ https://issues.apache.org/jira/browse/HBASE-15695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh resolved HBASE-15695. Resolution: Invalid closing since it was refiled as an ambari ticket. See link. > Ambari

Re: Google Summer Of Code 2016

On Fri, Apr 22, 2016 at 12:07 PM, Stack wrote: > Congrats Talat. You are our GSoC. We'll try and be nice (smile). > Congrats. That's awesome!

Re: Google Summer Of Code 2016

Congrats Talat. You are our GSoC. We'll try and be nice (smile). St.Ack On Fri, Mar 25, 2016 at 1:52 PM, Stack wrote: > Thanks Talat... I shoved some comments up in it but looks basically sound. > Thanks for sending it in. > St.Ack > > On Fri, Mar 25, 2016 at 11:09 AM, Talat

Re: Allowing clients to set priorities

A few things: + Our Matteo reminded me of the HBASE-11048 "Support setting custom priority per client RPC"/PHOENIX-938 "Use higher priority queue for index updates to prevent deadlock" work which adds in a factory so clients can do their rpccontroller. You'd build on this or controllers will

[jira] [Created] (HBASE-15696) Move region location cache serialization into serde

Elliott Clark created HBASE-15696: - Summary: Move region location cache serialization into serde Key: HBASE-15696 URL: https://issues.apache.org/jira/browse/HBASE-15696 Project: HBase Issue

[jira] [Created] (HBASE-15695) Ambari support for bucket caching parameter - hbase.bucketcache.ioengine

Nitin Verma created HBASE-15695: --- Summary: Ambari support for bucket caching parameter - hbase.bucketcache.ioengine Key: HBASE-15695 URL: https://issues.apache.org/jira/browse/HBASE-15695 Project:

Re: Allowing clients to set priorities

Sure sorry didn't provide a good example. There are two situations where I have thought this feature might be useful. Maybe more... 1. For something like Phoenix, there are situations where you want certain operations for tables / users to always have handlers available to do work. For

Successful: HBase Generate Website

Build status: Successful If successful, the website and docs have been generated. 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 you prefer to keep the hbase-site repo around

Re: Branch for 1.3

Mikhail: Any plan when to spin 1.3 RC0 ? HBaseCon is not very far. I was wondering if 1.3 release can be done before HBaseCon. Cheers On Thu, Feb 25, 2016 at 12:54 PM, Mikhail Antonov wrote: > To me it's not really about individual big features (besides, big features >

[jira] [Created] (HBASE-15693) Reconsider the ImportOrder rule of checkstyle

Duo Zhang created HBASE-15693: - Summary: Reconsider the ImportOrder rule of checkstyle Key: HBASE-15693 URL: https://issues.apache.org/jira/browse/HBASE-15693 Project: HBase Issue Type: Bug