Yeah, my thoughts exactly... though thanks Harsh for taking action to
clean up the documentation! Good on you.
On Thu, Mar 9, 2017 at 11:01 AM, Jean-Marc Spaggiari
wrote:
> So there is no way to use the pinning feature without having to use the
> favored nodes option? :(
On Fri, Mar 10, 2017 at 6:01 PM, Ted Yu wrote:
> HBASE-14123 branch has been created, with Vlad's mega patch v61.
>
The patch put up for VOTE here was done on a branch. The call to merge
seems to have been premature given the many cycles of review and test that
happened
stack created HBASE-17772:
-
Summary: IntegrationTestRSGroup won't run
Key: HBASE-17772
URL: https://issues.apache.org/jira/browse/HBASE-17772
Project: HBase
Issue Type: Bug
Components:
HBASE-14123 branch has been created, with Vlad's mega patch v61.
FYI
On Fri, Mar 10, 2017 at 3:30 PM, Ted Yu wrote:
> Thanks for the feedback, Andrew.
>
> How about the following plan:
>
> create branch HBASE-14123 off of master with mega patch v61 as the first
> commit
Thanks for the feedback, Andrew.
How about the following plan:
create branch HBASE-14123 off of master with mega patch v61 as the first
commit (reviewed by Stack and Enis)
Vlad and I continue development (the 3 blockers) based on HBASE-14123 branch
when all of the blockers get +1 and merged into
Sudeep Sunthankar created HBASE-17771:
-
Summary: [C++] Classes required for implementation of
BatchCallerBuilder
Key: HBASE-17771
URL: https://issues.apache.org/jira/browse/HBASE-17771
Project:
I have no vote here, but I'd argue that HBASE-14417 and HBASE-14141
shouldn't be blockers. I agree that HBASE-15227 to add fault tolerance is a
blocker.
HBASE-14417 is support for incrementally backing up bulk loaded rows.
That's an important feature, but if you don't use bulk loads, or don't
Thanks for the offer but I like that you were honest about compiling a list
of issues that you thought were blockers for release. Since this proposal
is a merge into 2.0, and we are trying to release 2.0, I am -1 on this
merge until those blockers are addressed.
I had a look at the list.
I think
No problem I will downgrade Blockers to Majors if it scares you, Andrew
Sent from my iPhone
> On Mar 10, 2017, at 1:52 PM, Andrew Purtell wrote:
>
> I know the merge of this feature has lagged substantially. I think that is
> regrettable but on another thread we are
The first release candidate for HBase 1.2.5 is available for download at:
https://dist.apache.org/repos/dist/dev/hbase/hbase-1.2.5RC0/
Maven artifacts are also available in a staging repository at:
https://repository.apache.org/content/repositories/orgapachehbase-1164/
Artifacts are signed
I have started testing rsgroups. Unfortunately I can't release from master
into our production so have had to backport onto ~1.3.0, including all
subsequent fixes applied in-situ to trunk. Thanks so much for the work
separating the rsgroup code into a separate maven module, that helps
tremendously
I know the merge of this feature has lagged substantially. I think that is
regrettable but on another thread we are lamenting that 2.0 is already
late. Unless I misunderstand, this is a proposal to merge something with
known blockers into trunk before we branch it for 2.0 which will
effectively
They are not blockers for merge - only for 2.0. GA
As I said already the feature is usable right now
We would like to continue working on master and we would like to see a
commitment from community
Sent from my iPhone
On Mar 10, 2017, at 11:16 AM, Andrew Purtell wrote:
[
https://issues.apache.org/jira/browse/HBASE-17725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-17725.
-
Resolution: Fixed
Hadoop Flags: Incompatible change
Release Note:
HBASE-16972
Agreed, let's delete it. We need to really for branch-2 soon, so lets get
rid of the obsolete one.
Enis
On Fri, Mar 10, 2017 at 7:47 AM, Ted Yu wrote:
> Yeah, we should do another round of cleanup.
>
> On Fri, Mar 10, 2017 at 7:45 AM, Sean Busbey wrote:
On Fri, Mar 10, 2017 at 11:10 AM, Andrew Purtell
wrote:
> I would also like us to reexamine our branch RM model.
>
> Prior to 1.0 , branch RMs curated branches that lead to minor releases.
>
> Post 1.0, branch RMs curate branches that only lead to patch releases.
>
> This
> Only BLOCKERs and CRITICALs are guaranteed for HBase 2.0 release.
If we have identified blockers, why merge this before they are in?
Otherwise we can't release 2.0, and it is overdue.
On Wed, Mar 8, 2017 at 1:32 PM, Vladimir Rodionov
wrote:
> Hello, HBase folks
>
>
I would also like us to reexamine our branch RM model.
Prior to 1.0 , branch RMs curated branches that lead to minor releases.
Post 1.0, branch RMs curate branches that only lead to patch releases.
This seems like a poorer use of precious resource (RM bandwidth and time),
one we can scarcely
I agree AMv2/Pv2 is almost finished and this makes sense as 2.0.
Agreed, upgrade issues need to be addressed, but I have been assuming this
will be done after branching during the stabilization and polishing part.
Need the branch-2 first to stabilize and polish.
Most of the rest justifies a 3.0,
Sean Busbey created HBASE-17770:
---
Summary: Update all build jobs to compress test log files
Key: HBASE-17770
URL: https://issues.apache.org/jira/browse/HBASE-17770
Project: HBase
Issue Type:
On Mon, Mar 6, 2017 at 6:15 PM, Enis Söztutar wrote:
> Thanks Stack for the nice writeup.
>
> I think we should shoot for an alpha release sooner than 2 months. It gives
> a test target, and will be a great way to test-drive and push for the
> release vehicles (packing,
On Thu, Mar 9, 2017 at 10:25 PM, Stack wrote:
> On Tue, Mar 7, 2017 at 1:51 PM, Josh Elser wrote:
>
>> Thanks for pulling in the FS Quotas work, Stack. I'm trying to cross the
>> last T's and dot the last I's.
>>
>> The biggest thing I know I need to do
Yeah, we should do another round of cleanup.
On Fri, Mar 10, 2017 at 7:45 AM, Sean Busbey wrote:
> It was an accidental push from back in June 2016:
>
> https://s.apache.org/l4Qc
>
> This happens from time to time and should be fine to delete.
>
> IIRC, the last round of
It was an accidental push from back in June 2016:
https://s.apache.org/l4Qc
This happens from time to time and should be fine to delete.
IIRC, the last round of clean ups was in March 2016 on HBASE-15006.
Maybe time for another go?
On Thu, Mar 9, 2017 at 5:09 PM, Ted Yu
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
Guangxu Cheng created HBASE-17769:
-
Summary: In webUI, master and regionserver address should use
rpc-port instead of infoport
Key: HBASE-17769
URL: https://issues.apache.org/jira/browse/HBASE-17769
Sudeep Sunthankar created HBASE-17768:
-
Summary: Makefile should recompile only the changed sources
Key: HBASE-17768
URL: https://issues.apache.org/jira/browse/HBASE-17768
Project: HBase
Still need one more +1
On Thu, Mar 9, 2017 at 11:27 PM, Vladimir Rodionov
wrote:
> bump
>
> On Thu, Mar 9, 2017 at 10:11 AM, Ted Yu wrote:
>
>> +1 from me as well.
>>
>> On Wed, Mar 8, 2017 at 3:48 PM, Enis Söztutar wrote:
>>
>> >
[
https://issues.apache.org/jira/browse/HBASE-17712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang reopened HBASE-17712:
---
> Remove/Simplify the logic of RegionScannerImpl.handleFileNotFound
>
29 matches
Mail list logo