Janos Gub created HBASE-17779:
-
Summary: disable_table_replication returns misleading message and
does not turn off repliaton
Key: HBASE-17779
URL: https://issues.apache.org/jira/browse/HBASE-17779
Projec
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
[
https://issues.apache.org/jira/browse/HBASE-17771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar resolved HBASE-17771.
---
Resolution: Fixed
Fix Version/s: HBASE-14850
> [C++] Classes required for implementati
[
https://issues.apache.org/jira/browse/HBASE-17771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar reopened HBASE-17771:
---
Accidentally resolved this. Reopening.
> [C++] Classes required for implementation of BatchCall
[
https://issues.apache.org/jira/browse/HBASE-17466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar resolved HBASE-17466.
---
Resolution: Fixed
Fix Version/s: HBASE-14850
Pushed this to the branch.
> [C++] Test
On Fri, Mar 10, 2017 at 9:09 PM, Stack wrote:
> 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
>> It ignores the feedback
If I "ignore" feedback, I put my comment - why? I am always open for
further discussions. If reviewer does not insist on a particular request -
it will be dropped. I think it is fair.
>> he list is incomplete because a bunch of
>> follow-ons came of the review cycle (
Vlad, on the first point, I think what Stack is saying is that creating the new
branch (as Ted did) ignores the feedback incorporated thus far in the
iterations of the mega-patch. That's a wrong way to go.
On the separation into a backup module, again, that was reverted to ease
reviews of the me
I think there is some misconception of using the term "blockers" for
referring to those jiras. My understanding is that those three jiras are
blockers for the backup functionality to be more mature and more usable.
But they are not release blockers. Let's say we merged the code in, and for
some rea
I tried to delete the HBASE-14123 branch using commands I found on
http://stackoverflow.com/questions/2003505/how-to-delete-a-git-branch-both-locally-and-remotely
Not sure if there is lag on github side:
$ git push origin :origin/HBASE-14123
error: unable to delete 'origin/HBASE-14123': remote re
Andrew Purtell created HBASE-17780:
--
Summary: BoundedByteBufferPool "At capacity" messages are not
actionable
Key: HBASE-17780
URL: https://issues.apache.org/jira/browse/HBASE-17780
Project: HBase
I don't like that issues were identified as "blockers" but now there is an
attempt to walk that back.
I don't like that development of this feature has lingered for a long time
in this unfinished state when this work could have been done by now, now
that we are trying to get a 2.0 out the door. Be
That's because this was pushed with a different name. It's gone now.
apurtell@onyx:~/src/hbase$ git branch -a | grep 14123
remotes/origin/14123
apurtell@onyx:~/src/hbase$ git push origin :14123
Username for 'https://git-wip-us.apache.org': apurtell
Password for 'https://apurt...@git-wip-us.apach
As of 6:06pm PST, I still saw these branches on
https://github.com/apache/hbase/
Maybe there is some delay.
Thanks Andrew.
On Mon, Mar 13, 2017 at 5:59 PM, Andrew Purtell wrote:
> That's because this was pushed with a different name. It's gone now.
>
> apurtell@onyx:~/src/hbase$ git branch -a
Successful
If successful, the HTML and link-checking report for http://hbase.apache.org is
available at
https://builds.apache.org/job/HBase%20Website%20Link%20Ckecker/86/artifact/link_report/index.html.
If failed, see
https://builds.apache.org/job/HBase%20Website%20Link%20Ckecker/86/console.
+1
Checked sums and signatures: ok
Built from source: ok (7u80)
RAT check passed: ok (7u80)
Unit tests pass: ok (8u102)
Loaded 1M rows with LTT: ok (8u102), all keys verified, latencies in the
ballpark, nothing unusual in the logs
On Fri, Mar 10, 2017 at 2:31 PM, Sean Busbey wrote:
> The first
Anup Halarnkar created HBASE-17781:
--
Summary: TestAcidGuarantees
Key: HBASE-17781
URL: https://issues.apache.org/jira/browse/HBASE-17781
Project: HBase
Issue Type: Bug
Components:
Yu Li created HBASE-17782:
-
Summary: Introduce new configuration to decide reference type used
in IdReadWriteLock
Key: HBASE-17782
URL: https://issues.apache.org/jira/browse/HBASE-17782
Project: HBase
18 matches
Mail list logo
