Duo Zhang created HBASE-21094:
-
Summary: Remove the explicit timeout config for
TestTruncateTableProcedure
Key: HBASE-21094
URL: https://issues.apache.org/jira/browse/HBASE-21094
Project: HBase
Duo Zhang created HBASE-21093:
-
Summary: Increase the dispatch delay for testing DDL procedures
Key: HBASE-21093
URL: https://issues.apache.org/jira/browse/HBASE-21093
Project: HBase
Issue Type:
Sean Busbey created HBASE-21092:
---
Summary: links in jira comments from the nightly job don't lead to
referenced report
Key: HBASE-21092
URL: https://issues.apache.org/jira/browse/HBASE-21092
Project:
Starting work on it now. If you've got branch-1 work pending that you'd
like to see in 1.4.7 please commit it in the next day or so. So far there
are 15 issues resolved in this RC, including a crash bug:
https://issues.apache.org/jira/projects/HBASE/versions/12343765
--
Best regards,
Andrew
Thanks for the suggestion, Misty!
While I think the green/yellow/red + symbols is a nice way to visually
understand things, each of those will also have to come with its own
explanation of what they mean.
I think one problem with this model is differentiating between "known
bad" and
Josh Elser created HBASE-21091:
--
Summary: Update Hadoop compatibility table
Key: HBASE-21091
URL: https://issues.apache.org/jira/browse/HBASE-21091
Project: HBase
Issue Type: Improvement
On 8/21/18 2:09 PM, Sean Busbey wrote:
On Tue, Aug 21, 2018 at 12:53 PM, Josh Elser wrote:
On 8/21/18 12:46 PM, Sean Busbey wrote:
On Tue, Aug 21, 2018 at 11:32 AM, Josh Elser wrote:
On 8/21/18 12:22 PM, Sean Busbey wrote:
I believe "NT" is already meant to cover the "NP" case. How
And, sorry if not clear, only source level compatibility is needed. The goal
wouldn't be drop in binary compatibility for user convenience, it would be
source compatibility so we don't have to replace all of the HTrace
instrumentation points cross stack in the short term, so, stack developer
I was assuming taking the HTrace API implementation, removing all code from the
methods, and reimplementing with Brave wouldn't face insurmountable challenges,
especially given the result is only meant for near term use, but I can't say
I've tried nor looked into it in details. Was thinking
On Mon, Aug 20, 2018 at 9:30 PM Sean Busbey wrote:
> A couple of other contribution concerns:
>
> a) Yetus Precommit works with github PRs, but the ASF Jenkins admin
> job that sends requests over to our job that runs the precommit tests
> does not. It's a minor issue (in that collectively we
On Tue, Aug 21, 2018 at 10:09 AM Andrew Purtell wrote:
> What if someone built a HTrace facade for Zipkin / Brave?
I like the idea but taking a look, HTrace does static dispatch. I was
thinking that precludes our being able to do a facade. I would love to hear
otherwise.
Thanks,
S
> Hadoop,
[
https://issues.apache.org/jira/browse/HBASE-21079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Krish Dey resolved HBASE-21079.
---
Resolution: Not A Problem
Release Note:
need to add following in secure cluster to prevent it
On Tue, Aug 21, 2018 at 12:53 PM, Josh Elser wrote:
>
>
> On 8/21/18 12:46 PM, Sean Busbey wrote:
>>
>> On Tue, Aug 21, 2018 at 11:32 AM, Josh Elser wrote:
>>>
>>>
>>>
>>> On 8/21/18 12:22 PM, Sean Busbey wrote:
I believe "NT" is already meant to cover the "NP" case. How can we
To be clear, I'm good with a symbolic representation, but I think we should
be making positive statements about configs we stand behind rather than
those we don't. More of a bounded set.
On Tue, Aug 21, 2018, 11:01 AM Misty Linville wrote:
> Let's change that table to positive statements.
On Tue, Aug 21, 2018 at 1:01 PM, Misty Linville wrote:
> Let's change that table to positive statements. Production, supported,
> recommended, tested. WDYT?
>
That doesn't work because downstream consumers presume that something
not being listed means that we don't have an opinion. Everything
Let's change that table to positive statements. Production, supported,
recommended, tested. WDYT?
On Tue, Aug 21, 2018, 8:12 AM Josh Elser wrote:
> Mich T had cross-posted a question to users@{hbase,phoenix} the only
> day. After some more information, we were able to find out that Mich was
>
On 8/21/18 12:46 PM, Sean Busbey wrote:
On Tue, Aug 21, 2018 at 11:32 AM, Josh Elser wrote:
On 8/21/18 12:22 PM, Sean Busbey wrote:
I believe "NT" is already meant to cover the "NP" case. How can we
rephrase it to better cover the meaning you want?
In my mind "not tested" isn't
:) I like color + symbol too
On 8/21/18 1:03 PM, Andrew Purtell wrote:
+1, I like the traffic light notion, and the colors and shapes Mike
proposes will be recognized cross culturally and cross language as far as I
know. (No need to bring up a weird counter example, but I would find it
It is my impression as mainly a lurker on a bunch of GH based projects,
that there are a ton of younger software developers have no idea that other
options besides Github even exist. We can tell them to open a JIRA, god
forbid attach a patch to JIRA, but they'll shrug and forget about it. They
Josh Elser created HBASE-21090:
--
Summary: Default WebUI to read-only when cluster has kerberos
authn but no webUI authn
Key: HBASE-21090
URL: https://issues.apache.org/jira/browse/HBASE-21090
Project:
What if someone built a HTrace facade for Zipkin / Brave? Hadoop, HBase,
Phoenix, and other HTrace API users would still need to move away from
embedding HTrace instrumentation points to whatever is the normal API of
the accepted replacement, but such a facade would give you a drop in
replacement
+1, I like the traffic light notion, and the colors and shapes Mike
proposes will be recognized cross culturally and cross language as far as I
know. (No need to bring up a weird counter example, but I would find it
interesting for reasons unrelated to this discussion...)
On Tue, Aug 21, 2018 at
If we're doing traffic light style (which I think is a good idea) I would
ask that we also have distinct symbols instead of circles for everything.
Green check mark, Yellow caution sign, Red X seem relatively universal?
On Tue, Aug 21, 2018 at 11:46 AM, Sean Busbey wrote:
> On Tue, Aug 21, 2018
On Tue, Aug 21, 2018 at 11:32 AM, Josh Elser wrote:
>
>
> On 8/21/18 12:22 PM, Sean Busbey wrote:
>>
>> I believe "NT" is already meant to cover the "NP" case. How can we
>> rephrase it to better cover the meaning you want?
>
>
> In my mind "not tested" isn't honest because we have many folks who
Sean Busbey created HBASE-21089:
---
Summary: clean out stale / invalid PRs
Key: HBASE-21089
URL: https://issues.apache.org/jira/browse/HBASE-21089
Project: HBase
Issue Type: Task
On 8/21/18 12:22 PM, Sean Busbey wrote:
I believe "NT" is already meant to cover the "NP" case. How can we
rephrase it to better cover the meaning you want?
In my mind "not tested" isn't honest because we have many folks who have
been doing testing on Hadoop 3.x versions. There is a very
On Tue, Aug 21, 2018 at 11:24 AM, Josh Elser wrote:
> On 8/21/18 12:15 PM, Sean Busbey wrote:
>>
>> On Tue, Aug 21, 2018 at 11:03 AM, Josh Elser wrote:
>>>
>>> Summarizing my feelings: A first-step might be to inch towards some
>>> middle
>>> ground where we allow code-review via PRs, but we
So, I actually had "not tested" above "not supported" in a draft, but
then flipped them :)
Really, I consider "NT" to be an outlier (we're acknowledging that we
just don't know). In my head, I was proposing a 3+1 (S/NP/X or NT), but
I do like your assessment of a traffic-light (Yellow can
On 8/21/18 12:15 PM, Sean Busbey wrote:
On Tue, Aug 21, 2018 at 11:03 AM, Josh Elser wrote:
Summarizing my feelings: A first-step might be to inch towards some middle
ground where we allow code-review via PRs, but we still require a Jira issue
and a patch to trigger QA (and avoid authorship
I believe "NT" is already meant to cover the "NP" case. How can we
rephrase it to better cover the meaning you want?
if "S" and "F" are meant to mean "production ready" why don't we just
make that status "production ready" and pick a symbol for it? (maybe a
check mark since this is no longer a
Hi Josh,
I'd prefer we maintain the simple "traffic light" labels for our
compatibility. I'm confused about what the difference might be between "NP"
and "X". I'm also confused how there can be any label with less
functionality than "X".
-n
On Tue, 21 Aug 2018 at 08:12 Josh Elser wrote:
>
Is our goal to add an option(PRs) way for contributions or to replace the
jira-patch way?
I supposed to be the former, but looks like the latter.
From: Sean Busbey
Sent: 22 August 2018 00:15:50
To: dev
Subject: Re: [DISCUSS] Move to github flow (WAS
Ted Yu created HBASE-21088:
--
Summary: HStoreFile should be closed in HStore#hasReferences
Key: HBASE-21088
URL: https://issues.apache.org/jira/browse/HBASE-21088
Project: HBase
Issue Type: Bug
On Tue, Aug 21, 2018 at 11:03 AM, Josh Elser wrote:
> Summarizing my feelings: A first-step might be to inch towards some middle
> ground where we allow code-review via PRs, but we still require a Jira issue
> and a patch to trigger QA (and avoid authorship issues, release note issues,
> etc) to
Is GitHub integration going to make patch review more palatable and
efficient for reviewers? Maybe we can increase our roster of regular
reviewers by using GitHub.
We can make a bot that looks for things in PR comment text. That way you
could add the JIRA number in a way the bit can pick it up
Summarizing my feelings: A first-step might be to inch towards some
middle ground where we allow code-review via PRs, but we still require a
Jira issue and a patch to trigger QA (and avoid authorship issues,
release note issues, etc) to "gate" the commit.
That gives us clear next steps:
1)
Congratulations to you and all involved in organizing this successful
event, Yu Li! Thank you for your leadership.
It would be great if any attendees on these lists would to share their
experiences from event. It's awesome to see the growth of the HBase
community in Asia.
Misty
On Mon, Aug 20,
Mich T had cross-posted a question to users@{hbase,phoenix} the only
day. After some more information, we were able to find out that Mich was
trying to use Hadoop 3.1 with HBase 1.2.6
After pointing Mich to the compatibility table[1], I was about to puff
out my chest and say "look! this table
On Tue, Aug 21, 2018 at 3:44 AM Tsuyoshi Ozawa wrote:
> Thanks for starting discussion, Stack.
>
> The ZipKin seems to be coming to the Apache Incubator. As Andrew
> Purtell said on HADOOP-15566, it would be good option since there is
> no problem about licenses.
>
Sean Busbey created HBASE-21087:
---
Summary: flaky dashboard needs a way to annotate when there's
already a jira associated with a test failure
Key: HBASE-21087
URL: https://issues.apache.org/jira/browse/HBASE-21087
[
https://issues.apache.org/jira/browse/HBASE-20988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-20988.
-
Resolution: Duplicate
> TestShell shouldn't be skipped for hbase-shell module test
>
[
https://issues.apache.org/jira/browse/HBASE-21086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-21086.
-
Resolution: Duplicate
duplicate of HBASE-21076. please review there?
> NPE in
Duo Zhang created HBASE-21086:
-
Summary: NPE in TestTableResource
Key: HBASE-21086
URL: https://issues.apache.org/jira/browse/HBASE-21086
Project: HBase
Issue Type: Bug
Reporter: Duo
Allan Yang created HBASE-21085:
--
Summary: Adding getter methods to some private fields in
ProcedureV2 module
Key: HBASE-21085
URL: https://issues.apache.org/jira/browse/HBASE-21085
Project: HBase
Toshihiro Suzuki created HBASE-21084:
Summary: The split parent region becomes online after cloning a
snapshot
Key: HBASE-21084
URL: https://issues.apache.org/jira/browse/HBASE-21084
Project:
Thanks for starting discussion, Stack.
The ZipKin seems to be coming to the Apache Incubator. As Andrew
Purtell said on HADOOP-15566, it would be good option since there is
no problem about licenses.
https://wiki.apache.org/incubator/ZipkinProposal
Stack, do you have any knowledge about
Allan Yang created HBASE-21083:
--
Summary: Introduce a mechanism to bypass the execution of a stuck
procedure
Key: HBASE-21083
URL: https://issues.apache.org/jira/browse/HBASE-21083
Project: HBase
Duo Zhang created HBASE-21082:
-
Summary: Reimplement assign/unassign related procedure metrics
Key: HBASE-21082
URL: https://issues.apache.org/jira/browse/HBASE-21082
Project: HBase
Issue Type:
Dear all,
As chairman of the conference, I'm glad to announce the success of
HBaseConAsia2018 (Aug. 17th, Beijing, China). There were totally 494
attendees at scene and 14796 views from live broadcast. Shared are part of
the pictures and more coming, slides and videos will be uploaded later
(will
Not going to comment on the "old dog" ;-)
But yeah...almost everyone I meet is using IntelliJ and I _believe_ that
one of the differences between the two is that Eclipse by default only
suspends a single thread while IntelliJ by default suspends the whole app.
I'll try to test it. And if I find
50 matches
Mail list logo
