Ah thanks Andy. It seemed mostly a copy (with some internal
modification). Now, where is that used at all?
On Sun, Jun 19, 2016 at 7:06 PM, Andrew Purtell
wrote:
> We have additional functionality that the Hadoop supplied one does not,
> importantly the ability to dump
Appy, could you make another link? if there's a "no-expiration" option
that would be best.
On Fri, Jun 17, 2016 at 7:23 PM, Apekshit Sharma wrote:
> Or you can join the team using this link:
>
Friendly reminder that this vote closes in about 1 hour.
+1
* checked sigs and sums
* checked source against commit hash
* checked source builds binaries
* compatibility report looks good[1]. No IA.Public impact.
[1]:
Matteo Bertozzi created HBASE-16068:
---
Summary: Procedure v2 - use consts for conf properties in tests
Key: HBASE-16068
URL: https://issues.apache.org/jira/browse/HBASE-16068
Project: HBase
li xiang created HBASE-16069:
Summary: Typo "trapsparently" in item 3 of chapter 87.2
Key: HBASE-16069
URL: https://issues.apache.org/jira/browse/HBASE-16069
Project: HBase
Issue Type: Bug
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
benbenqiang created HBASE-16072:
---
Summary: CRUD actions stucked when using spark1.6 manipulate
hbase1.2.1
Key: HBASE-16072
URL: https://issues.apache.org/jira/browse/HBASE-16072
Project: HBase
ChiaPing Tsai created HBASE-16071:
-
Summary: The VisibilityLabelFilter should not count the "delete
cell"
Key: HBASE-16071
URL: https://issues.apache.org/jira/browse/HBASE-16071
Project: HBase
ramkrishna.s.vasudevan created HBASE-16070:
--
Summary: Mapreduce Serialization class do not Interface audience
Key: HBASE-16070
URL: https://issues.apache.org/jira/browse/HBASE-16070
Project:
BTW, I am looking at 1.2 branch, though here the Hadoop one does
exactly the same as what the HBase one does. Where do I see the
difference? Master looks the same too. Are you referring to the
histogram classes?
On Mon, Jun 20, 2016 at 1:36 PM, Lars George wrote:
> Ah
Sean Busbey created HBASE-16073:
---
Summary: update compatibility_checker for jacc dropping comma sep
args
Key: HBASE-16073
URL: https://issues.apache.org/jira/browse/HBASE-16073
Project: HBase
MetricMutableHistogram and all ( The classes which were ports of hadoop's
classes) have been removed. They are no longer used. However the ones
hadoop supplies were very slow so instead we use MutableHistogram.
See: HBASE-15222
On Mon, Jun 20, 2016 at 5:19 AM, Lars George
This vote fails with
* +1 (binding): 2
* +1 (non-binding): 1
I'll spin up a new RC soon with a longer voting period.
On Tue, Jun 14, 2016 at 11:43 PM, Sean Busbey wrote:
> Hi folks!
>
> I'm happy to announce that the first release candidate of HBase 1.2.2 is
> available
check out the corresponding shouldXXX commands:
public boolean shouldDisableBalancer() {
return fixAny || disableBalancer;
}
If fixAny which is true if any of the -fix is run, we disable the master
chores.
For -fixHdfsOverlaps and -fixHdfsHoles, I've mentioned this in the jira I
think,
Enis, what I suggested was that even no repair is suggested, we still
should disable master maint tasks in online check for more deterministic
result.
Thanks
Stephen
On Mon, Jun 20, 2016 at 1:44 PM, Enis Söztutar wrote:
> check out the corresponding shouldXXX commands:
>
>
Bibin A Chundatt created HBASE-16077:
Summary: Replication status doesnt show failed RS metrics in CLI
Key: HBASE-16077
URL: https://issues.apache.org/jira/browse/HBASE-16077
Project: HBase
Anyone can join anytime with @apache.org email id using following link.
https://apache-hbase.slack.com/x-37639653748-52658243986/signup
Sorry, but slack doesn't allow doing same for @gmail.com email ids.
On Mon, Jun 20, 2016 at 11:36 AM, Apekshit Sharma wrote:
> Here's new
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/48/artifact/link_report/index.html.
If failed, see
https://builds.apache.org/job/HBase%20Website%20Link%20Ckecker/48/console.
} else if (cmd.equals("-disableBalancer")) {
setDisableBalancer();
} else if (cmd.equals("-disableSplitAndMerge")) {
setDisableSplitAndMerge();
In HBCK, we will either use the options to disable master maintenance work
(see above) or the master maintenance are
[
https://issues.apache.org/jira/browse/HBASE-14397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Antonov resolved HBASE-14397.
-
Resolution: Fixed
> PrefixFilter doesn't filter all remaining rows if the prefix is
Here's new link:
https://apache-hbase.slack.com/shared_invite/NTI1OTc5NzQ4ODctMTQ2NjQ0Nzc0NC01ZDg1YjIyZjcw
Sorry can't do anything about expiration, that's slack's policy: no link
active more than 48 hours.
On Mon, Jun 20, 2016 at 9:14 AM, Sean Busbey wrote:
> Appy, could
Youngjoon Kim created HBASE-16076:
-
Summary: Cannot configure split policy in HBase shell
Key: HBASE-16076
URL: https://issues.apache.org/jira/browse/HBASE-16076
Project: HBase
Issue Type:
Mikhail Antonov created HBASE-16075:
---
Summary: TestAcidGuarantees is flaky
Key: HBASE-16075
URL: https://issues.apache.org/jira/browse/HBASE-16075
Project: HBase
Issue Type: Bug
A while ago we ran an effort to crack down on broken/flaky tests on
branch-1, and I guess some of the branch builds are again in a sorry state,
so writing here to raise awareness (kind of).
As I'm looking at
https://builds.apache.org/job/HBase-1.3 and
https://builds.apache.org/job/HBase-1.4
On Mon, Jun 20, 2016 at 1:49 PM, Stephen Jiang
wrote:
> Enis, what I suggested was that even no repair is suggested, we still
> should disable master maint tasks in online check for more deterministic
> result.
>
I see, makes sense as long as we are finished with
Mikhail Antonov created HBASE-16074:
---
Summary: ITBLL fails, reports lost big or tine families
Key: HBASE-16074
URL: https://issues.apache.org/jira/browse/HBASE-16074
Project: HBase
Issue
If there’s no technical limitation, we should definitely do it. As you
note, customers running in production hate when they have to shut down
clusters and with some of the testing infrastructure being rolled out, this
is definitely something we can set up automated testing for. +1
-Dima
On Mon,
Is this change for 2.0 ?
For 1.x, this would be incompatible change, right ?
On Mon, Jun 20, 2016 at 2:33 PM, Enis Söztutar wrote:
> On Mon, Jun 20, 2016 at 1:49 PM, Stephen Jiang
> wrote:
>
> > Enis, what I suggested was that even no repair is
Time to formalize 2.0 rolling upgrade scenario?
0.94 -> 0.96 singularity was a real pain for operators and for our users.
If possible we should not have the users suffer through the same thing
unless there is a very compelling reason. For the current stuff in master,
there is nothing that will
29 matches
Mail list logo