Thanks for the great reply, Andrew!
Andrew Purtell wrote:
I find the InterfaceAudience annotations on this really strange. How can
we have a Public audience Interface (o.a.h.h.c.Table) with Private methods?
I'm also not sure the Private annotations on the Table interface are that
useful. An
(top-post since I can't find a better place to respond to everyone who
chimed in here)
Huge thanks, everyone! This was absolutely the best email thread (and
JIRA issue) I could've come back to after not keeping up with email for
the day.
Stack wrote:
On Tue, Aug 16, 2016 at 8:20 AM, Sean Bu
So, the answer to Sean's original question is "as robust as snapshots
presently are"? (independence of backup/restore failure tolerance from
snapshot failure tolerance)
Is this just a question WRT context of the change, or is it means for a
veto from you, Sean? Just trying to make sure I'm fol
you here, Sean? Why HBASE-7912 is
not good enough yet to be integrated into 2.0 branch?
-Vlad
On Wed, Sep 7, 2016 at 8:23 AM, Sean Busbey wrote:
On Tue, Sep 6, 2016 at 10:36 PM, Josh Elser wrote:
So, the answer to Sean's original question is "as robust as snapshots
presently are&quo
Sean Busbey wrote:
This would be a very big breaking change in release numbering that goes
against our compatibility guidelines. We only drop support for Java
versions on major releases.
If we want features that require newer jdks sooner, we should make major
releases sooner.
+1 On this exac
Hi folks,
I'd like to propose the introduction of FileSystem quotas to HBase.
Here's a design doc[1] available which (hopefully) covers all of the
salient points of what I think an initial version of such a feature
would include.
tl;dr We can define quotas on tables and namespaces. Region si
that people can comment on it ?
Is there a JIRA opened for this work ?
Please open one if there is none.
Thanks
On Fri, Oct 28, 2016 at 9:00 AM, Josh Elser wrote:
Hi folks,
I'd like to propose the introduction of FileSystem quotas to HBase.
Here's a design doc[1] available which
1 and patches starting
to land.
I'm also happy to entertain more discussion if anyone hasn't found the
time to read/comment yet.
Thanks!
- Josh
Josh Elser wrote:
Sure thing, Ted.
https://docs.google.com/document/d/1VtLWDkB2tpwc_zgCNPE1ulZOeecF-YA2FYSK3TSs_bw/edit?usp=sharing
er-allocation would be minimal
and
negligible in production. Thus, the proposal is to implement the soft
approach with good documentation about how much space can be
over-allocated
in a worst-case scenario.
Enis
On Wed, Nov 2, 2016 at 12:15 PM, Josh Elser wrote:
Thanks for the reviews so far,
oduction. Thus, the proposal is to implement the soft
approach with good documentation about how much space can be
over-allocated
in a worst-case scenario.
Enis
On Wed, Nov 2, 2016 at 12:15 PM, Josh Elser wrote:
Thanks for the reviews so far, Ted and Stack. The comments were great
and
much apprec
Yep -- see avatica-metrics[1], avatica-dropwizard-metrics3[2], and my
dropwizard-hadoop-metrics2[3] project for what Nick is referring to.
What I ended up doing in Calcite/Avatica was a step beyond your #3,
Enis. Instead of choosing a subset of some standard metrics library to
expose, I "re-bu
+1
I just pull it up via the javadoc jars with my IDE. Not worth the
time/effort to build/maintain. It would be good to add a pointer to
external websites instead of just making broken links (for those who
have the current URLs bookmarked).
Stack wrote:
The xref pages were useful once befor
Hi folks,
I've gotten far enough along that I have some confidence in what I
worked on early on in the feature is actually sensible. As such, I'd
like to start working through the review process of each incremental bit
of work (the child issues).
As each child issue is reviewed, it would be
Enis Söztutar wrote:
Bumping this up in case people are interested.
Also this is not coprocessor-specific, because I think we can incrementally
start using the new hbase-metrics module, and get rid of our complicated
metrics2 based patterns for core metrics as well. We should of course start
e
Thanks, all. I'm looking forward to continuing to work with you all!
Nick Dimiduk wrote:
On behalf of the Apache HBase PMC, I am pleased to announce that Josh Elser
has accepted the PMC's invitation to become a committer on the project. We
appreciate all of Josh's generous con
Hiya folks,
Just wanted to shoot out a quick note that the filesystem quota work is
really coming along. With the last patch I put up (HBASE-17001), we
actually have some end-to-end tests that show the feature (I'm
pleasantly tickled at how nice it turned out from a user POV).
If anyone was
Big +1 to your efforts, Andrew, and an EOL on 0.98
Ted Yu wrote:
Kudos to Andrew.
On Mon, Jan 9, 2017 at 11:26 AM, Enis Söztutar wrote:
Thanks Andrew for carrying this.
+1 on the EOL messaging.
Enis
On Mon, Jan 9, 2017 at 10:37 AM, Mikhail Antonov
wrote:
Yeah - thank you for all hard wo
+1 If any "worker" thread can't safely/reasonably retry some unexpected
exception without a reasonable expectation of self-healing, tank the RS.
Having those threads die but not the RS could go uncaught for indefinite
period of time.
Sean Busbey wrote:
I've noticed a few other places where w
to revisit that and make sure that all the threads are
injected with the UEH.
The replication source threads are started on demand, that is why the UEH
is not injected I think. But agreed that we should do the safe route here,
and abort the regionserver.
Enis
On Thu, Jan 26, 2017 at 2:19 PM,
If you have the cycles to add the validation, absolutely :)
Lars George wrote:
Duh, my bad, JM you are right, I missed to type the leading slashes...
then a little better error handling may be nice. Not sure, you guys
think this warrants a JIRA?
On Fri, Feb 3, 2017 at 3:52 PM, Ted Yu wrote:
L
Hiya,
Shamelessly soliciting some of your already full day to take a look at
the space quota work. Locally, I actually have the feature working
pretty well, but the feature branch is lagging quite a bit behind due to
the review process.
In case you forgot the pertinent details..
Parent JIRA
(late to the party, but..)
+1 Nick sums this up better than I could have.
Nick Dimiduk wrote:
For the client: I'm a fan of shaded client modules by default and
minimizing the exposure of that surface area of 3rd party libs (none, if
possible). For example, Elastic Search has a similar set of ch
Hiya,
I wanted to put out a quick note that the space quota work (HBASE-16961)
is getting pretty close to something I'd feel comfortable hitting "master".
The last "big" changeset is under review now, leaving only much smaller
bug-fixes (instead of the big feature work). There is some necessa
Hiya folks,
As we're wrapping up on the current set of features listed in
HBASE-16961 for tracking and limiting the HDFS space used by HBase
tables and namespaces, I wanted to present a doc that outlines an
approach to tracking snapshots in the context of space quotas.
As most operators know
Oops! Thanks, Ted. Will flip that now.
Ted Yu wrote:
Josh:
The design doc in [1] is View only.
Can you give viewers permission to comment ?
On Wed, Feb 22, 2017 at 2:04 PM, Josh Elser wrote:
Hiya folks,
As we're wrapping up on the current set of features listed in HBASE-16961
for tra
+1 (non-binding)
* sigs/xsums are good
* Can build from source
* No unexpected binaries in source tarball
* apache-rat:check passes on source tarball
* Can run locally from bin tarball
Nick Dimiduk wrote:
I'm happy to announce the first release candidate of HBase 1.1.9 (HBase-1.1.
9RC0) is avai
A minor "bump" here, folks.
Thanks to Ted and Zach for your comments so far, but more are always
welcome.
Josh Elser wrote:
Hiya folks,
As we're wrapping up on the current set of features listed in
HBASE-16961 for tracking and limiting the HDFS space used by HBase
tables an
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 still is to write a new chapter to
the book. After that, I'd start entertaining larger reviews/discussions
to merge the feature into master. Anyone with
+1 (non-binding)
* xsums/sigs OK
* Compat report looks OK for a patch release
* Spot-checked source release and ran apache-rat:check
* Can build from source (and run a subset of tests)
* KEYS has the signing key
* Commit is in source repository
Sean Busbey wrote:
The first release candidate for
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 still is to write a new chapter to
the book. After that, I'd start
I took a moment to read through the "blockers" as originally identified
by Vlad, and (to echo Enis' take) I read the majority of them as being
blockers not for the next release, but for a "full-fledged feature". I'm
going to intentional avoid addressing the discussion of shipping partial
featur
r all table to reset
broken system table).
I am currently starting working on HBASE-15227. It will probably take a
week or two to finish.
On a doc side, as I already mention we will need to update command-line
tool section in the doc I posted above.
-Vlad
On Tue, Mar 14, 2017 at 1:57 PM, Josh
anyone is doing the community a favor by
trying to walk that back.
On Tue, Mar 14, 2017 at 1:57 PM, Josh Elser wrote:
I took a moment to read through the "blockers" as originally identified by
Vlad, and (to echo Enis' take) I read the majority of them as being
blockers not for t
It is an honest
assessment and I don't think anyone is doing the community a favor by
trying to walk that back.
On Tue, Mar 14, 2017 at 1:57 PM, Josh Elser wrote:
I took a moment to read through the "blockers" as originally identified by
Vlad, and (to echo Enis' take) I rea
+1 to the JDK8 default implementation approach. I'd say this would be
good to push forward for the future.
For 1.x, I see no reason why we couldn't provide concrete
implementations as a stop-gap. Identifying and creating those classes is
probably the biggest barrier :). I don't think anything
Sean Busbey wrote:
On Mon, Mar 20, 2017 at 11:09 AM, Ted Yu wrote:
Is Yetus 0.4.0 release stable ?
yes.
If we use Yetus annotations, is there only one jar pulled in as dependency ?
IIRC, we'll get one jar as a dependency. There shouldn't be any
transitive dependencies involved.
Less
Please do. Thanks for checking.
+1 (binding)
Sean Busbey wrote:
Hi Josh!
Are you comfortable with me considering your vote binding now that
you're a PMC member?
On Sat, Mar 11, 2017 at 5:24 PM, Josh Elser wrote:
+1 (non-binding)
* xsums/sigs OK
* Compat report looks OK for a patch re
Hiya folks,
As advertised (warned? *winks*), all of the sub-tasks on HBASE-16961
have been resolved after being committed to the HBASE-16961 branch in SCM.
While Ted has been a stalwart reviewer, it would be good to get another
set of eyes (or a few sets) on the changes before considering I s
If you could encapsulate what you're trying to do into a
unit-test/standalone class, it would likely be much more approachable
for anyone to reproduce and help debug your issues.
You've provided a lot of information, but very little of it is helpful
in actually figuring out why what you've don
Rebase is done for those who want to just look at some code.
https://github.com/apache/hbase/compare/HBASE-16961
Josh Elser wrote:
Hiya folks,
As advertised (warned? *winks*), all of the sub-tasks on HBASE-16961
have been resolved after being committed to the HBASE-16961 branch in SCM.
While
where you want to go for two if you
could look into my problem and provide some suggestion.
Thanks,
Yoom
- Original Message -----
From: "Josh Elser"
To: dev@hbase.apache.org
Sent: Monday, March 20, 2017 6:29:41 PM
Subject: Re: Multiple match's Filter is NOT WORKING
If you could e
bump
Josh Elser wrote:
Rebase is done for those who want to just look at some code.
https://github.com/apache/hbase/compare/HBASE-16961
Josh Elser wrote:
Hiya folks,
As advertised (warned? *winks*), all of the sub-tasks on HBASE-16961
have been resolved after being committed to the HBASE
Sean Busbey wrote:
Heya folks,
Hadoop has just closed their RCs on a 2.8.0 release[1]. During voting,
two Hadoop PMC members positioned the release as "not production
ready"[2], similar to how the 2.7.0 release was flagged[3].
Oh good.
The RC only just passed, so the actual release bits an
le of
application and verification of a simple space quota, say by namespace. If this
already exists a pointer would be helpful. To start I'd want to run through
something expected to work.
On Mar 23, 2017, at 10:45 AM, Josh Elser wrote:
bump
Josh Elser wrote:
Rebase is done for those w
For those who miss it on the JIRA notification email, see:
https://issues.apache.org/jira/browse/HBASE-16961?focusedCommentId=15941163&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15941163
Josh Elser wrote:
Thanks Andrew!
An integration is actually somet
1.1 -> 2: don't forget about the block cache which can invalidate the
need for any HDFS read.
I think you're over-simplifying the write-path quite a bit. I'm not sure
what you mean by an 'asynchronous write', but that doesn't exist at the
HBase RPC layer as that would invalidate the consistenc
I'm partial to 2.0.0-alpha[x]/beta[x]
* Conveys that it's 2.x (not 1.x)
* Conveys "instability"
* Doesn't buck Maven's view of the world (Maven is happy with a version
string of 2.0.0-alpha)
* Still enables a "2.0.0" later
Sean Busbey wrote:
Hi folks!
What are folks opinions on how we name r
Just checked and I don't see 'em there anymore. I assume someone else
has already done this :)
Enis Söztutar wrote:
Thanks for the cleanup. Indeed we should remove these from jira admin so
that they don't show up in auto-fill.
Enis
On Fri, Mar 31, 2017 at 8:34 AM, Stack wrote:
On Thu, Mar
+1 to that :D
Stack wrote:
Hot Dog!
On Fri, Mar 31, 2017 at 3:03 PM, Misty Stanley-Jones
wrote:
FYI, the linked Jenkins job now automatically updates the site! No more
need to manually push. Merry Christmas! :)
- Original message -
From: Apache Jenkins Server
To: dev@hbase.apache.org
ou use SYNC_WAL or FSYNC_WAL flag.
>
> On Tue, Mar 28, 2017 at 12:11 PM, Josh Elser wrote:
>
>> 1.1 -> 2: don't forget about the block cache which can invalidate the need
>> for any HDFS read.
>>
>> I think you're over-simplifying the write-path quite a
n you need to call hsync() instead
of hflush(), and that would be the correct behavior if you use FSYNC_WAL
flag (per HBase documentation).
However, HBase does not do that.
Suli
On Sun, Apr 2, 2017 at 11:26 AM, Josh Elser
wrote:
No, that's not correct. HBase would, by definition, not be a
+1 (binding)
* xsums/sigs OK
* Can build from src
* License headers/src-release files look OK
* bin tarball's LICENSE is lacking [1]
* Can run tests (still going, but will comment if something bad arises)
* Glanced at compat report (thanks for publishing!).
Thanks Yu and Andrew for looking at 1.
+1 to that one, Jerry :). I think we're missing some context, Suli.
Also, I don't know of any code path in which an RPC would be partially
processed and then returned to the queue. Calls go from wire -> queue ->
handler, they can't move backwards. They either move forward or throw an
exception
Stack wrote:
Let me revive this thread.
Lets do Sean's idea of a pre-build step where we package and relocate
('shade') critical dependencies (Going by the thread above, Ram, Anoop, and
Andy seems good w/ general idea).
In implementation, we (The HBase PMC) would ask for a new repo [1]. I
Sean Busbey wrote:
On Tue, Apr 11, 2017 at 11:43 PM Nick Dimiduk wrote:
This effort is about our internals. We have a mess of other components
all
up inside us such as HDFS, etc., each with their own sets of dependencies
many of which we have in common. This project t is about making it so
Yeah, neat idea now that I understand the big picture :)
Instead of trying to do this purely server-side, have you considered a
first "wag" at a solution of hooking into the existing RPC quota work?
Presently, in the context of a user's RPCs, quotas only limit the number
of RPCs that user mak
Nick Dimiduk wrote:
> Well put, Nick.
>
> With Sean's point about the Hadoop shaded client, it seems to me that we
> have things which could be pursued in parallel:
>
> 1) Roadmap to Hadoop3 (and shaded hdfs client).
> 2) Identify components which we use from Hadoop, for each component:
>
Stack wrote:
On Wed, Apr 12, 2017 at 8:22 AM, Josh Elser wrote:
This makes me wonder if we could construct source jars just the same as
we're creating shaded jars. Google has lead me to [2][3], but I've never
tried either. The latter option seems to be acknowledging that
+1 (binding) with a nit.
* NOTICE file needs an update (copyright year). The notes about
"Licensed under Apache License, version 2.0" also appear unnecessary to
me (but are only "bad" in that it unnecessarily bloats our NOTICE).
* xsums/sigs OK
* Can build tarball from source
* Ran YCSB agains
Hi folks,
Here's a formal thread for discussion on merging the space quota feature
(presently in the branch HBASE-16961[1]) into master. The tl;dr on the
feature is that this extends the RPC quota feature to include
configurable limits on the size of tables and namespaces. Please check
the ar
&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15941163
Stack wrote:
Sounds like an excellent idea to me. If I were to take a tour over the
quotas feature, how would you direct my perambulations Josh?
Thanks,
St.Ack
On Tue, Apr 25, 2017 at 9:13 AM, Josh Elser wrote:
Hi folks,
Yep!
Removing the previous release's bits is a standing request from infra to
reduce hosting bandwidth, for the ASF and its mirrors. All of the old
stuff will still be available via archive.a.o.
Mikhail Antonov wrote:
That might be something I missed during 1.3.1 release preparation - is the
I've been running into an issue where the PreCommit job fails when
building the Yetus Docker image because it attempts to fetch a version
of Oracle JDK8 (8u121) where only a newer version is present (8u131).
I've seen my tasks [1] fail as well someone else's [2], but I've also
seen some others
after a time. Do we know about how
long this has been happening?
Maybe we could do a get-apt update before the install call?
On Tue, May 2, 2017 at 10:41 AM, Josh Elser wrote:
I've been running into an issue where the PreCommit job fails when building
the Yetus Docker image because it att
Aha. That's an interesting point. I missed that the first time :)
Ted Yu wrote:
[3] [4] are for master branch.
Don't know why branch-1 testing is "special".
On Tue, May 2, 2017 at 8:41 AM, Josh Elser wrote:
I've been running into an issue where the PreCommit jo
Thanks, Allen (and Sean).
Let me poke and I'll report back.
Allen Wittenauer wrote:
Hmmm. It's an interesting side-effect of how docker caches intermediate images:
===
Step 10/35 : RUN apt-get -q update
---> Using cache
---> 79fd4a487c35
Step 11/35 : RUN echo oracle-java7-installer
sh
Appears to have done the trick.
https://builds.apache.org/job/PreCommit-HBASE-Build/6671/console
Will open up a new issue just to fix this across the gamut.
Thanks again, all.
Josh Elser wrote:
Thanks, Allen (and Sean).
Let me poke and I'll report back.
Allen Wittenauer wrote:
Hmmm.
(-cc dev@yetus, +bcc dev@yetus)
HBASE-17985 is committed and should do the trick.
Re-trigger QA if you had some JIRA issue blocked on this issue. If
anyone is still seeing failure, please leave a note on/re-open HBASE-17985.
Thanks!
Josh Elser wrote:
Appears to have done the trick.
https
x27;t said
anything yet?
I would like to keep pushing on this, but I also don't want to call a
premature vote to merge.
- Josh
[1] https://issues.apache.org/jira/browse/HBASE-17977
[2] https://issues.apache.org/jira/browse/HBASE-17978
[3] https://issues.apache.org/jira/browse/HBASE-17
e.
In terms of high level design and the ops model, I'd be good with a merge.
On Fri, May 5, 2017 at 1:43 PM, Stack wrote:
On Fri, May 5, 2017 at 9:12 AM, Josh Elser wrote:
Just an update: Andrew P provided some great feedback which I've finally
got all merged into the feature branc
Folks,
This is a vote to (rebase and) merge the branch HBASE-16961 into master.
Per the book, this requires 3 binding +1's from other committers to merge.
Relevant info for those who want to revisit any topics:
DISCUSS on merge[1]
Design Doc[2]
Staged user manual[3]
I'll plan to leave this o
Reminder: I hope to close this in ~30hrs and there have been no votes so
far.
Josh Elser wrote:
Folks,
This is a vote to (rebase and) merge the branch HBASE-16961 into master.
Per the book, this requires 3 binding +1's from other committers to merge.
Relevant info for those who wa
I'm also happy to not immediately merge after this
vote completes.
Andrew Purtell wrote:
Would it help to cut a branch for 2.0 before attempting to merge in a new
major feature?
On Tue, May 9, 2017 at 8:41 AM, Josh Elser wrote:
Reminder: I hope to close this in ~30hrs and there have
, Josh Elser wrote:
I won't pretend to be involved enough in the 2.0 work to give an opinion
:) -- I did say earlier that I'm happy to land this in 2.0 or 3.0 (whatever
master decides to be at the time I merge).
If the spirit of the voters is to include this in 3.0 and not 2.0, that's
As requested (later in this thread), I'll make sure this VOTE stays open
at least until 2017-05-17 (an extra week). If time continues to be a
barrier for review/input, please do speak up.
Josh Elser wrote:
Folks,
This is a vote to (rebase and) merge the branch HBASE-16961 into master
You issue a Get request for the rowkey you're looking for (checking for
existence) or your use a Scanner to read all rowkeys (data) in the table.
Developer Brasil wrote:
How to find the rowkey of a table in HBASE
--
View this message in context:
http://apache-hbase.679495.n3.nabble.com/How-
Since we're struggling to get votes cast (I can only assume due to lack
of time from individuals since there have been no objections/concerns
raised).
Here's my +1 too
Josh Elser wrote:
Folks,
This is a vote to (rebase and) merge the branch HBASE-16961 into master.
Per the
bits to merge into master around EOD (I'm in EST). If there
are others that share the concern Andrew raised about this landing in
2.0 (as opposed to waiting for a branch-2 or hbase 3.0 branch), please
speak up and we can figure those details. Thanks!
- Josh
Josh Elser wrote:
Folks,
This
branch for 2, IIRC, this is pretty well contained so
should not throw-off work like the big patch out on HBASE-14614 branch.
St.Ack
On Fri, May 19, 2017 at 7:30 AM, Josh Elser wrote:
Calling this VOTE as we have 3 +1's (myself, Ted, and Enis).
Special thanks to Ted, Enis, and Andrew fo
On 6/7/17 1:17 AM, Stack wrote:
Lets start in on the hardening of hbase-2.0.0. All features are in though
in need of test and polish. There are tasks outstanding around migration
from hbase-1 to hbase-2 and narratives to tell our users around timeout,
etc. We still need to update dependencies,
On 6/7/17 11:04 AM, Josh Elser wrote:
On 6/7/17 1:17 AM, Stack wrote:
Lets start in on the hardening of hbase-2.0.0. All features are in though
in need of test and polish. There are tasks outstanding around migration
from hbase-1 to hbase-2 and narratives to tell our users around timeout
On 6/7/17 11:15 AM, Sean Busbey wrote:
On Wed, Jun 7, 2017 at 10:08 AM, Josh Elser wrote:
On 6/7/17 11:04 AM, Josh Elser wrote:
On 6/7/17 1:17 AM, Stack wrote:
Lets start in on the hardening of hbase-2.0.0. All features are in though
in need of test and polish. There are tasks
On 6/14/17 3:53 AM, Peter Somogyi wrote:
Hi,
As one of my first task with HBase I started to look into
why IntegrationTestRegionReplicaReplication fails. I would like to get some
suggestions from you.
I noticed when I run the test using normal cluster or minicluster I get the
same error message
+1 (binding)
* No unexpected binaries in source release
* L&N look good
* Could build from source
* Could run bin-tarball as-is
* Checked compat report (thanks for publishing)
* xsum/sigs OK
* Ran a PE randomwritetest
On 6/10/17 7:40 PM, Nick Dimiduk wrote:
I'm happy to announce the first relea
seen
this test failing and increasing timeouts (look at the test code options to
do with increasing timeout) helped quite some.
____
From: Josh Elser
Sent: Wednesday, June 14, 2017 3:17 PM
To: dev@hbase.apache.org
Subject: Re: Problem with IntegrationTestRegionRep
Done ;)
There were two issues still tagged as alpha-1 (JIRA didn't want to show
me them before performing the action), but I bumped them to alpha-2.
On 6/20/17 12:19 PM, Mike Drob wrote:
Hi Stack,
Can you mark jira version 2.0.0-alpha-1 as released?
Thanks,
Mike
On Sat, Jun 10, 2017 at 10:
On 6/20/17 1:28 AM, Stack wrote:
On Thu, Apr 13, 2017 at 4:46 PM, Josh Elser wrote:
...
I think pushing this part forward with some code is the next logical step.
Seems to be consensus about taking our known internal dependencies and
performing this shade magic.
I opened HBASE-18240 &quo
tl;dr Infra is upgrading Jenkins in 2 weeks and Java7 Maven jobs
may/may-not work after this. See explanation below from [1]:
Users with jobs configured with the "Maven project" type may not be able
to use Java 7 for their Maven jobs. The correct behavior is not
guaranteed so proceed at your
d976bf31865596f@%3Cdev.hbase.apache.org%3E
On Tue, Jun 27, 2017 at 10:57 AM, Josh Elser wrote:
tl;dr Infra is upgrading Jenkins in 2 weeks and Java7 Maven jobs
may/may-not work after this. See explanation below from [1]:
Users with jobs configured with the "Maven project" type may not be able
to u
On 6/27/17 7:20 PM, Stack wrote:
* test-patch's whitespace plugin can configured to ignore some files (but I
can't think of any we'd care to so whitelist)
Generated files.
Oh my goodness, yes, please. This has been such a pain in the rear for
me as I've been rebasing space quota patches. S
I'm pleased to announce yet another PMC addition in the form of Devaraj
Das. One of the "old guard" in the broader Hadoop umbrella, he's also a
long-standing member in our community. We all look forward to the
continued contributions and project leadership.
Please join me in welcoming Devaraj!
Shibin,
Please keep all communication on public forums (JIRA or mailing lists).
This is very important to make sure that all parties interested can
participate -- we do not want to be exclusionary.
To answer your question, your change below is half-way there:
Your change below would prevent
On 7/21/17 12:03 PM, Stack wrote:
Status update girls and boys!
hbase-2.0.0-alpha1 went out June 22nd.
alpha2 has been a bit slow to follow (holidays) though there has been
steady progress closing out blockers and criticals by a bunch of you all.
The plan is for a release in the first week or
On behalf of the Apache HBase PMC, I'm pleased to announce that Mike
Drob has accepted the PMC's invitation to become a committer.
Mike has been doing some great things lately in the project and this is
a simple way that we can express our thanks. As my boss likes to tell
me: the reward for a
On 7/31/17 9:00 AM, Stack wrote:
On Mon, Jul 24, 2017 at 12:25 PM, Josh Elser wrote:
...
I like the idea of this also hitting 2.0 as it would make the feature a
bit more "real", but am obviously a little nervous (I have no reason to be
nervous though). I am pretty happy with the
+1 (binding)
* xsums/sigs OK
* apache-rat:check OK
* Poked at L&N in both src/bin (bin's NOTICE seems bloated with ASLv2
entries, but this isn't a blocker)
* Compat report is great (thanks for publishing)
* Tag is published
Thanks for putting together, Nick!
On 8/12/17 6:09 PM, Nick Dimiduk w
+1 (binding)
* Saw the same unit test failures as Andrew did (obviously)
* Ran a brief randomWrite PE locally and didn't have any obvious issues
I took a glance at the contents of the lib/ dir for the bin tarball, and
noticed that we seem to be duplicating a few dependencies (e.g.
jetty-util,
Hi folks,
I find myself in a position where I have a bit more time to start
investing into HBase 2.0, but I find myself a bit stymied about where
to begin. I appreciate the document tracking the high-level features
that Stack has been maintaining (and reminding the rest of us to
update), but it's
On 9/7/17 12:35 AM, Stack wrote:
On Wed, Sep 6, 2017 at 8:18 PM, Josh Elser wrote:
Hi folks,
I find myself in a position where I have a bit more time to start
investing into HBase 2.0, but I find myself a bit stymied about where
to begin. I appreciate the document tracking the high-level
Based on the list of stuff on HBASE-14414 and offline-chats had with
Vlad myself, I know of the following being needed
https://issues.apache.org/jira/browse/HBASE-15227 - Fault tolerance
umbrella (no-op on its own)
https://issues.apache.org/jira/browse/HBASE-17852 - I believe Vlad is
working o
1 - 100 of 881 matches
Mail list logo
