Since remote facilities will be available, I'd like to dial in as well.
Thanks,
Nick
On Thu, Jan 8, 2015 at 2:24 AM, Rajeshbabu Chintaguntla <
chrajeshbab...@gmail.com> wrote:
> Yes Andrew I can use GoToMeeting.
>
> Thanks,
> Rajeshbabu.
>
> On Wed, Jan 7, 2015 at 9:16 PM, Andrew Purtell
> wrot
Where does the HBase Shell implementation fall in this matrix? Asking for a
friend [0] :)
[0]: https://issues.apache.org/jira/browse/HBASE-12833
On Fri, Dec 5, 2014 at 4:36 PM, Nick Dimiduk wrote:
> Right. So either two sections or simply remove the specificity of
> "Server-Side&q
Would be great to bring out jetty dependency into the modern era for this
release. I'm not sure how much work it will be if we're inheriting this
from Hadoop though.
https://issues.apache.org/jira/browse/HBASE-12894
On Wednesday, January 21, 2015, Andrew Purtell wrote:
> > The unit tests are no
Thank you so much Enis!
Rather than ballooning our JIRA count, can we update the QE bot to track
it's work queue more intelligently?
On Fri, Jan 30, 2015 at 10:47 AM, Enis Söztutar wrote:
> Agreed. Subtasks can be used for this.
>
> Enis
>
> On Fri, Jan 30, 2015 at 9:10 AM, Andrew Purtell
> wr
Sounds like you're wanting to do a lot of what the TableInputFormat
facilitates for mapreduce programs. Probably you can use code from that
package to turn a Scan into input splits, which contain region name
and RegionServer location, and consume those from your custom coordinator.
-n
On Tuesday,
I don't think we have enough release managers or enough bandwidth as a
community to evaluate RC's for a monthly minor release cycle. My
understanding was that we'd continue doing patch releases on the monthly
cycle (RM's willing) and spin minor releases as we have new RM's volunteer.
I don't think
I believe your posted example is intended to be supported. There's no
enforcement, for instance, that the master is upgraded before all RS's.
On Wed, Mar 4, 2015 at 4:06 PM, Matteo Bertozzi
wrote:
> the book (http://hbase.apache.org/book.html#hbase.versioning)
> talks about "only allow upgrading
es it's reasonable to support it both ways.The book is
> currently unavailable from the HBase site, so I can't check the exact
> wording we ended up with.
>
> -- Lars
> From: Nick Dimiduk >
> To: hbase-dev >
> Sent: Wednesday, March 4, 2015 4:49 PM
> Su
> so basically we can face with situation when master is upgraded and
> hits old region server.
>
> On Thu, Mar 5, 2015 at 5:21 AM, Nick Dimiduk > wrote:
>
> > My point was that we cannot make this guarantee as there's a client
> > embedded in the master (
ecked that bit.
> >
> > Client is definitely used to access meta, which can be hosted anywhere,
> > so basically we can face with situation when master is upgraded and
> > hits old region server.
> >
> >
> >
> > On Thu, Mar 5, 2015 at 5:21 AM, Nick Dimi
Maybe break it into smaller commits?
On Thu, Mar 5, 2015 at 12:58 PM, Misty Stanley-Jones <
mstanleyjo...@cloudera.com> wrote:
> The transfer of the apidocs, devapidocs, xref, and xref-test is STILL in
> progress. :/ Hopefully soon.
>
> On Fri, Mar 6, 2015 at 3:39 AM, Andrew Purtell
> wrote:
>
>
st a new
> > cluster we won't have that problem (and we'd be free to add new stuff as
> we
> > see fit, as long as we do break old RPCs)
> > As long as the servers do not use that RPC amongst each other, we have
> not
> > broken server-server compatibility
FYI.
On Thu, Mar 5, 2015 at 5:57 PM, Arpit Agarwal (JIRA)
wrote:
> Arpit Agarwal created HDFS-7896:
> ---
>
> Summary: HDFS Slow disk detection
> Key: HDFS-7896
> URL: https://issues.apache.org/jira/browse/HDFS-7896
>
Nice work fellas!
On Mon, Mar 9, 2015 at 2:52 PM, Stack wrote:
> These fellas are great and have been doing nice, juicy contribs over the
> last year or two. Please welcome them to the hbase committer crew.
>
> Welcome aboard lads!
> St.Ack
>
>
> > Furthermore, "hadoop jar" is how you're supposed to launch YARN apps. If
> we
> > say that doing things via the hbase command is acceptable, we're opening
> > ourselves up to an expansion of what the hbase command has to do. (i.e.
> > perhaps it should detect if the passed class is a YARN dri
The advantage of shading/JarJaring our dependencies is we *don't* get stuck
with hbase-A.B-hadoop-Z.Y. Those releases are a hassle for users, and a
hassle for release managers. The disadvantage being runtime bloat in the
form of an excessive number of classes to load.
I think there's a middle grou
ch, before I file a jira for
> > > isolating third-party deps what scope are we looking for? hbase-client
> > and
> > > the MR tooling only? i.e I'd prefer to state that folks making use of
> > > LimitedPrivate features like coprocessors don't get isolation
I think we can learn a lesson or two from the vendor marketing machines --
a release timed with HBaseCon would be ideal in this regard. My obligations
to the event are minimal, so I'm willing to volunteer as RM for 1.1. Do we
think we can make some of these decisions in time for spinning RC's in
mi
bq. Our commit log conventions aren't universally followed, due to human
error
Going forward, I think we can alleviate this issue with a git hook and a
regexp.
On Mon, Mar 16, 2015 at 10:38 AM, Andrew Purtell
wrote:
> > I think Jira management should be left to the committers. One can pretty
>
Yes please!
On Mon, Mar 16, 2015 at 12:43 PM, Zee Chen wrote:
> Of the existing BucketCache IOEngines, the FileIOEngine uses pread() to
> copy data from kernel space to user space. This is a good choice when the
> total working set size is much bigger than the available RAM and the
> latency is
I've been thinking of something along these lines as well. Rather an either
official Apache project, I was thinking it could be something as simple as
a github managed dockerfile that stands up a HBase + Phoenix singlenode
deal, see if momentum builds.
Another idea is Phoenix could include HBase i
HBase shipping a tgz containing Phoenix sounds backwards to me. It seems
like Hadoop project shipping a tgz with Hive included as a convenience.
Such convenience packages would be great, but I don't think it's HBase
project's responsibility to do so any more than it would be Hadoop
project's respon
lusion
of a Phoenix Query Server (PHOENIX-971) impact your opinion on this?
On Wed, Mar 18, 2015 at 2:45 PM, Nick Dimiduk wrote:
>
> >
> > HBase shipping a tgz containing Phoenix sounds backwards to me. It seems
> > like Hadoop project shipping a tgz with Hive inclu
Thanks for chiming in Jon.
I'd like to see the MOB feature included in 1.1, so long as it can be
shipped disabled by default to avoid surprises for unrelated users. That
said, it will depend on contributors' bandwidth to port the patches. Since
Jon is willing, it seems likely that the feature will
Hi folks,
It looks like there's quite a few commits that were missing on the
branch-1.0 line. When porting patches from master to current release
branches, please remember that a patch must land on all non-retired
branches "greater than" a target branch. For example, to back-port to 0.98,
it must
Got it. Thanks.
On Monday, March 23, 2015, Stack wrote:
> On Mon, Mar 23, 2015 at 8:37 PM, Elliott Clark > wrote:
>
> > I thought we were only back porting fixes to 1.0.1 other wise it's not
> just
> > a patch release. And we would be completely going away from semver.
> >
> >
> What the fella
On Tue, Mar 24, 2015 at 8:15 AM, Wilm Schumacher
wrote:
> This will be an interesting discussion, as the API changes quite
> fundamental with 2.0.0.
>
Are you referring to the new Admin, Table, BufferedMutator interfaces?
Those are available now in 1.0.
+1
verify signatures
started local-mode cluster with default configs:
- ran LTT for 45 mins with 1 table, GZ 10mm rows. skimmed logs, looks good.
- meanwhile, poked around in the webUI
- noticed master/conf is 404 (not sink-worthy)
- issued split, compaction requests, all good.
- table.
With about 100 issues beyond the 1.0.x line [0], I think it's time to start
talking about our 1.1.0 release. Noteworthy goodness already committed to
the branch includes:
- Async RPC client (HBASE-12684)
- Improved compaction controls (HBASE-8329, HBASE-12859)
- Per-column family flush (HBASE-1
Congratulations Sean! Nice work.
On Thu, Mar 26, 2015 at 10:26 AM, Andrew Purtell
wrote:
> On behalf of the Apache HBase PMC I"m pleased to announce that Sean Busbey
> has accepted our invitation to become a PMC member on the Apache HBase
> project. Sean has been an active and positive contribut
Nice work Srikanth!
On Thu, Apr 2, 2015 at 10:49 PM, Mikhail Antonov
wrote:
> Congratulations Srikanth!
>
> -Mikhail
>
> On Thu, Apr 2, 2015 at 8:44 PM, Pankaj kr wrote:
> > Congrats Srikanth..!!
> >
> > -Original Message-
> > From: Andrew Purtell [mailto:apurt...@apache.org]
> > Sent:
Thanks a lot for the efforts Jerry, welcome.
On Fri, Apr 3, 2015 at 1:46 AM, Srikanth Srungarapu
wrote:
> Kudos, Jerry!
>
> On Thu, Apr 2, 2015 at 10:49 PM, Mikhail Antonov
> wrote:
>
> > Congrats Jerry!
> >
> > -Mikhail
> >
> > On Thu, Apr 2, 2015 at 9:21 PM, Pankaj kr wrote:
> > > Congrats J
straightforward back-port. Any takers on that?
While I'm here rattling your chains, do us all a favor and go take the
latest RC's from other releases for a spin. We have two up for votes as we
speak: 0.98.12 and 1.0.1.
Happy HBaseing,
-n
On Wed, Mar 25, 2015 at 6:05 PM, Nick Dimiduk
On the OSS side, have a look at Bosun [0]. I haven't used it myself, but it
builds on OpenTSDB, which itself is an HBase application. It looks like the
just-released Ambari 2.0 [1] also has improved metrics/monitoring support,
which also appear to use HBase.
-n
[0]: http://bosun.org
[1]:
https://
Heya devs,
Looking for an appropriate answer for this question, it seems we don't have
a public Cell implementation that can be used for generating HFiles. How
are folks expected to generate Cells instances if KeyValue is
@InterfaceAudience.Private ?
-n
On Tue, Apr 14, 2015 at 9:00 AM,
On Thu, Apr 9, 2015 at 12:44 AM, Mikhail Antonov
wrote:
> Semver states that "MAJOR version when you make incompatible API
> changes". I read it literally as "in 2.0 you can remove anything
> compared to 1.0". Realistically, that probably means we can at least
> remove APIs which could be relati
project.
Yours,
-n
On Wed, Apr 8, 2015 at 1:40 AM, Nick Dimiduk wrote:
> Heya folks,
>
> We're down to a week remaining before my proposed branch date. A couple
> big-ticket items have made it in since my last mail (HBASE-12972,
> HBASE-12975, HBASE-11598, HBASE-1317
ations of parameters.
>
> On Tue, Apr 14, 2015 at 9:04 AM Nick Dimiduk wrote:
>
> > Heya devs,
> >
> > Looking for an appropriate answer for this question, it seems we don't
> have
> > a public Cell implementation that can be used for generating HFiles. How
Let's see this done in time for HBaseCon!
Thanks,
Nick
On Tue, Apr 14, 2015 at 8:53 PM, Nick Dimiduk wrote:
> Hi Devs,
>
> I plan to create branch-1.1 on Thursday, sometime in the waking hours of
> PST. Please consider this your 48-hour-ish notice. In the mean time I'll be
&
pected.
-n
On Thu, Apr 16, 2015 at 5:59 PM, Nick Dimiduk wrote:
>
> > Devs --
> >
> > I've created the new brach-1.1 and bumped the POM version on branch-1 to
> > 1.2.0-SNAPSHOT. I've also updated the pre-commit builds to watch for
> > "branch-1
Done.
On Fri, Apr 17, 2015 at 2:51 PM, Elliott Clark wrote:
> Anyone want to take a quick look at HBASE-13477
>
[1]: https://builds.apache.org/view/All/job/HBase-1.2/1/
On Fri, Apr 17, 2015 at 11:15 AM, Nick Dimiduk wrote:
> On Fri, Apr 17, 2015 at 11:01 AM, Ted Yu wrote:
>
>> In the future, patch applicable to branch-1.1 should be attached to JIRA
>> with branch-1.1 in filename for a QA run
*/Unassigned/*.
- HBASE-13452 just needs some **arithmetic** to verify sizes are accurate
and some pruning of log messages. */Unassigned/*.
Volunteers please form an orderly queue to your nearest JIRA enlistment
office.
Yours,
-n
On Fri, Apr 17, 2015 at 5:50 PM, Nick Dimiduk wrote:
> I'
My mistake Jerry, you're correct. My pre-coffee brain was thinking that by
upgrading Hadoop we'd promote the version of Jackson under us. This is not
the case because we have an explicit dependency (though maybe maven is
promoting this for us for the builds anyway?)
Point is, we have issues that n
The whole feature is frustrating. Makes it hard to track the conversation
without scanning al over the place.
On Wed, Apr 22, 2015 at 2:06 PM, Andrew Purtell wrote:
> Yeah, maybe I had an issue with some assets failing to load. That's messy
>
> On Wed, Apr 22, 2015 at 1:26 PM, Sean Busbey wrote
On Thu, Apr 23, 2015 at 4:13 PM, Stack wrote:
> Does this 'admission' help with the which-hadoop thread too?
>
Right -- "working toward semver".
Are we now at liberty to bump to 2.6 or 2.7 even for branch-1.1? I still
have Karthik's offer to roll a 2.5.3 with the HDFS issue resolved.
What abou
On Thu, Apr 23, 2015 at 3:54 PM, Andrew Purtell wrote:
> Can we ask Hadoop to make a 2.5.3 release with HDFS-7005?
>
I have, and the offer is on the table.
https://issues.apache.org/jira/browse/HDFS-7005?focusedCommentId=14505636&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabp
he API surface area differences between Hadoop 2.5, 2.6 and see
what might crop up for users.
-n
On Thu, Apr 23, 2015 at 5:34 PM, Nick Dimiduk wrote:
>
> > On Thu, Apr 23, 2015 at 4:13 PM, Stack wrote:
> >
> > > Does this 'admission' help with the which-hadoop thr
I'm game for giving it a shot if we can build some confidence it won't
cause other issues. However given we're moving to Hadoop 2.6 I think we've
already relaxed the constraints and this won't buy us much. More trouble
than it's worth?
On Saturday, April 25, 2015, Jerry He wrote:
> This is an i
I spoke with a couple of our HDFS folks on Friday, they sound confident
that 2.7.1 will be considered production-stable. I think we can try bumping
master to 2.7.1 when it's out.
On Fri, Apr 24, 2015 at 10:03 AM, Sean Busbey wrote:
> On Fri, Apr 24, 2015 at 11:53 AM, Elliott Clark wrote:
>
> >
Devs --
Branch-1.1 is officially closed for feature enhancements, with the
following exceptions: HBASE-11339, HBASE-13260, HBASE-13431.
Please limit commits to blocker and critical bug fixes. I also ask that you
please ping me as patches go in, so that I might review them in relation to
the testi
Running {{mvn test -PrunSmallTests}} is running Medium and Large unit tests
as well. Anyone else seeing this behavior? Maybe this is just something
weird about my checkout?
-n
1.994 s
[INFO] Finished at: 2015-04-26T13:24:41-07:00
[INFO] Final Memory: 30M/310M
[INFO]
--------
On Sun, Apr 26, 2015 at 1:12 PM, Sean Busbey wrote:
> Can you run
>
> mvn -PrunSmallTests help:active-profiles
>
> -
ize the decision here so that I can
move forward with an RC?
Thanks,
Nick
On Sun, Apr 26, 2015 at 11:33 AM, Nick Dimiduk wrote:
> I spoke with a couple of our HDFS folks on Friday, they sound confident
> that 2.7.1 will be considered production-stable. I think we can try bumping
> mast
? A new integration test
maybe?
On Mon, Apr 27, 2015 at 9:32 AM, Cody Marcel wrote:
>
> > The port for PHOENIX-1728
> > <https://issues.apache.org/jira/browse/PHOENIX-1728> from master is
> still
> > in progress. I should have the rest of the branches update toda
ld be satisfied
by the above report.
[0]: http://people.apache.org/~ndimiduk/check_compat_hadoop.patch
[1]:
http://people.apache.org/~ndimiduk/release-2.5.1_release-2.6.0_compat_report.html
On Mon, Apr 27, 2015 at 9:53 AM, Nick Dimiduk wrote:
> Seems I misunderstood the conclusion of this dis
To unsubscribe, mail dev-unsubscr...@hbase.apache.org .
On Tue, Apr 28, 2015 at 4:00 AM, wrote:
> Please unsubscribe me from this group
>
>
> Thanks,
>
> Dinesh Kumar P
>
>
>
>
>
>
> Sent from Windows Mail
>
>
>
>
>
> From: Matteo Bertozzi (JIRA)
> Sent: Tuesday, 28 April 2015 04:02
We're pretty late in the game to bring this up, but I want to make sure
we're all on the same page. I believe we want to support rolling upgrades
as there have been blocker tickets opened against the release to this
effect. The two things I'm aware of that cause problems here are table
state in met
es: 0, Errors: 0, Skipped: 0, Time elapsed: 76.163
> sec
> > - in org.apache.hadoop.hbase.thrift.TestThriftServer
> >
> > The above test is a large test.
> >
> > FYI
> >
> > On Sun, Apr 26, 2015 at 12:47 PM, Nick Dimiduk > > wrote:
> >
> > > Running {{mvn test -PrunSm
Please hold on commits to 1.1 while I prepare for RC.
The one exception is HBASE-13260, if folks can come to a consensus. Do keep
me informed.
-n
I'm happy to announce the first release candidate of HBase 1.1.0
(HBase-1.1.0RC0) is available for download at
https://dist.apache.org/repos/dist/dev/hbase/hbase-1.0.1RC2/
Maven artifacts are also available in the staging repository
https://repository.apache.org/content/repositories/orgapachehbase
RC is tagged and posted. You may resume in branch-1.1 -- but remember,
we're bug fixes only.
Thanks,
Nick
On Wed, Apr 29, 2015 at 7:39 AM, Nick Dimiduk wrote:
> Please hold on commits to 1.1 while I prepare for RC.
>
> The one exception is HBASE-13260, if folks can come to a
e.org/repos/dist/dev/hbase/hbase-1.0.1RC2/
> The above url is correct ? from the name it does not seems to be.
>
> -- Ashish
>
> On Thu, Apr 30, 2015 at 11:05 AM, Nick Dimiduk
> wrote:
>
> > I'm happy to announce the first release candidate of HBase 1.1.0
> &g
Hi folks,
I've been struggling to get green test runs on branch-1.1. I believe some
of these apply to 1.0 and 0.98 as well (HBASE-13143, HBASE-13391). I filed
tickets for a couple of these earlier in the week (HBASE-13591,
HBASE-13587, HBASE-13590), and then disabled them in search of build
stabil
SF Jenkins and just use my own resources.
>
> It's also curious that the precommit builds seem to do better than the
> others.
>
>
> On Thu, Apr 30, 2015 at 4:10 PM, Nick Dimiduk wrote:
>
> > Hi folks,
> >
> > I've been struggling to get green
rom 0.98 to any 1.x for as long as we can manage
> > it. Will make life easier for adopters of the 1.x line who come in later.
> >
> >
> >
> > On Tue, Apr 28, 2015 at 10:16 AM, Nick Dimiduk >
> > wrote:
> >
> > > We're pretty late in
pload your keys to MIT servers?
>
> I am not able to verify the sig.
>
> gpg --list-keys
>
> pub 4096R/8644EEB6 2014-03-11 [expires: 2016-04-14]
>
> uid Nick Dimiduk
>
> uid Nick Dimiduk
>
> sub 4096R/D2DCE494 2014-03
e.apache.org
> as far as I remember.
>
> Enis
>
> On Mon, May 4, 2015 at 8:36 PM, Nick Dimiduk wrote:
>
> > I had uploaded to subkeys.pgp.net originally, wasn't sure why
> > people.apache.org wasn't picking up the new sub key. I've just uploaded
> t
g.
Nick
On Wed, Apr 29, 2015 at 10:35 PM, Nick Dimiduk wrote:
> I'm happy to announce the first release candidate of HBase 1.1.0
> (HBase-1.1.0RC0) is available for download at
> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.0.1RC2/
>
> Maven artifacts are also availabl
On Wed, May 6, 2015 at 10:13 AM, Andrew Purtell
wrote:
> I prefer to patch the POMs.
>
Is this a formal -1?
I've opened HBASE-13637 for tracking this issue. Let's get it fixed and
I'll spin a new RC tonight.
> On May 5, 2015, at 4:16 PM, Nick Dimiduk wrote:
> >
perhaps it would be better to spin a RC on
> Friday?
>
> I can take HBASE-13637 but am sitting on a plane at the moment. Won't be
> able to get to it until tonight.
>
> > On May 6, 2015, at 10:43 AM, Nick Dimiduk wrote:
> >
> > On Wed, May 6, 2015 at 10:13 A
On Wednesday, May 6, 2015, lars hofhansl wrote:
> With HBASE-11666 in place, can we now start to use JDK 7 language features
> across the board, starting in 1.0.x?
> I know we had discussion, but it wasn't entirely clear whether that
> allowed for using JDK 7 language features or not.
I believe
because it's marked as
Evolving, though let's discuss. The change came in as part of HBASE-13421:
https://github.com/apache/hbase/commit/408b9161754966af80be5046fea657769b24f6a0#diff-87a7898ef24244574a843648feac86b7
On Wed, May 6, 2015 at 1:07 PM, Nick Dimiduk wrote:
>
> > I&
for 12 days and that RC would contain
an extremely limited set of changes above RC0, I would like to run it
through an abbreviated voting window -- say 48 hours.
On Wed, Apr 29, 2015 at 10:35 PM, Nick Dimiduk wrote:
> I'm happy to announce the first release candidate of HBase 1.1.
l give the new RC a spin.
>
> On Mon, May 11, 2015 at 11:42 AM, Andrew Purtell
> wrote:
>
> > +1 on a new RC
> >
> > FWIW, I have time to check it in an abbreviated voting window.
> >
> > On Mon, May 11, 2015 at 11:40 AM, Nick Dimiduk
> > wrote:
>
Canceling the RC0 vote per discussion above. RC1 to follow.
On Mon, May 11, 2015 at 12:17 PM, Nick Dimiduk wrote:
> Thanks Andrew, Ted.
>
> I'm working on fixing the docs. Would someone mind shepherding through
> HBASE-13637 and HBASE-13661? We also need to start
e this RC has already been open for 12 days and that RC would contain
> > an extremely limited set of changes above RC0, I would like to run it
> > through an abbreviated voting window -- say 48 hours.
> >
> > On Wed, Apr 29, 2015 at 10:35 PM, Nick Dimiduk
> > wr
I'm happy to announce the second release candidate of HBase 1.1.0
(HBase-1.1.0RC1) is available for download at
https://dist.apache.org/repos/dist/dev/hbase/hbase-1.1.0RC1/
Maven artifacts are also available in the staging repository
https://repository.apache.org/content/repositories/orgapachehbas
b.com/ndimiduk/hbase-downstreamer
[1]: http://people.apache.org/~ndimiduk/0.98.0_1.1.0RC1_compat_report.html
[2]: http://people.apache.org/~ndimiduk/1.0.0_1.1.0RC1_compat_report.html
On Mon, May 11, 2015 at 11:04 PM, Nick Dimiduk wrote:
> I'm happy to announce the second release candi
t from master or branch-1.1 for branch-1.1.0? It seems
> that it is missing the HTable change (which is not needed in master).
>
> Enis
>
> On Mon, May 11, 2015 at 11:15 PM, Nick Dimiduk
> wrote:
>
>> Here's my review and +1:
>>
>> [✓] verified tarballs vs
tencies stable after warmup. Some minor issues
> > with log levels (HBASE-13673, HBASE-13674, HBASE-13675), again nothing
> > worth sinking a RC over.
> >
> >
> > On Mon, May 11, 2015 at 11:04 PM, Nick Dimiduk
> > wrote:
> >
> > > I
RC2 on the way.
On Mon, May 11, 2015 at 11:04 PM, Nick Dimiduk wrote:
> I'm happy to announce the second release candidate of HBase 1.1.0
> (HBase-1.1.0RC1) is available for download at
> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.1.0RC1/
>
> Maven artifacts are a
I'm happy to announce the third (time's the charm) release candidate of
HBase 1.1.0 (HBase-1.1.0RC2) is available for download at
https://dist.apache.org/repos/dist/dev/hbase/hbase-1.1.0RC2/
Maven artifacts are also available in the staging repository
https://repository.apache.org/content/reposito
compat_report.html
[1]: http://people.apache.org/~ndimiduk/1.0.0_1.1.0RC2_compat_report.html
On Tue, May 12, 2015 at 2:57 PM, Nick Dimiduk wrote:
> I'm happy to announce the third (time's the charm) release candidate of
> HBase 1.1.0 (HBase-1.1.0RC2) is available for download at
&g
What's the "pending fixed" default for resolving issues now? Was that
change intentional? Is there a new workflow to follow now?
Thanks,
Nick
Thanks Ted.
On Wed, May 13, 2015 at 11:51 AM, Ted Yu wrote:
> See https://issues.apache.org/jira/browse/INFRA-9646
>
> Before the above is resolved, please pick 'Fixed' as resolution.
>
> Cheers
>
> On Wed, May 13, 2015 at 11:42 AM, Nick Dimiduk wrote:
>
>
BASE-13676.)*
> > > - Unpacked bin tarball, layout looks good
> > > - Spot checked docs, looks good*
> > > - Ran LTT with 1M keys, latencies stable after warmup. Some minor
> issues
> > > with log levels (HBASE-13673, HBASE-13674, HBASE-136
The HBase team is happy to announce the availability of HBase 1.1.0!
Download it from an Apache mirror near you,
http://www.apache.org/dyn/closer.cgi/hbase/, or wire up through the maven
repo.
HBase 1.1.0 is the first minor release in the HBase 1.x line, continuing on
the theme of bringing a stabl
Don't delete branch-1.1. Let me explain.
branch-1.1.0 was my use in creating rc1+. I created it from the 1.1.0rc0
tag and spun subsequent RC's as commits on that branch. The idea was to
de-risk further RC's by not bringing in changes that were unrelated to
reviewers' criticisms raised on the VOTE
; > Pardon, that was an unfortunate typo. I meant branch-1.1.0.
> >
> >
> > On Fri, May 22, 2015 at 11:06 AM, Nick Dimiduk
> > wrote:
> >
> >> Don't delete branch-1.1. Let me explain.
> >>
> >> branch-1.1.0 was my use in creating r
the answer appears to be "no".
> Thanks.
> -- Lars
> From: Nick Dimiduk
> To: hbase-dev
> Sent: Friday, May 22, 2015 11:33 AM
> Subject: Re: Git branch-1.1.0?
>
> On Fri, May 22, 2015 at 11:28 AM, Andrew Purtell
> wrote:
>
> > FWIW, I make
Greetings devs,
It's getting to be that time: I plan to spin the first 1.1.1 RC on Monday.
Remember, this is a patch release in accordance with the semantic version
guidelines, so only mutually compatible bug fixes are accepted. Let me know
if you have any doubts.
Thanks,
Nick
Heya,
I noticed this while bisecting HBASE-13822. Seems the shell attempts to
connect to the cluster on startup. Is this new behavior, or have I been
sleeping? Seems like we would want to start the connection lazily.
Thoughts?
Thanks,
Nick
y
> not even delay your plans.
>
> On Tue, Jun 2, 2015 at 3:19 AM, Nick Dimiduk > wrote:
>
> > Greetings devs,
> >
> > It's getting to be that time: I plan to spin the first 1.1.1 RC on
> Monday.
> > Remember, this is a patch release in accordance
I've commented on the ticket; this is new functionality and so is
inappropriate for branch-1.0 and branch-1.1.
On Mon, Jun 1, 2015 at 7:50 PM, Ted Yu wrote:
> Nick:
> Do you think HBASE-13356 has a chance to make this release ?
>
> Cheers
>
> On Mon, Jun 1, 2015 at 10:19
You may want to give a heads-up on user@ and phoenix lists as well so that
folks have a chance to push their open tickets.
On Mon, Jun 8, 2015 at 5:32 PM, Sean Busbey wrote:
> Hi all!
>
> Just a quick reminder that the plan is to branch 1.2 on or about Monday
> June 15th, which is a week from to
I'll take it for a spin, but I need a couple more days. Mind extending
through the weekend?
On Tue, Jun 9, 2015 at 3:15 PM, Andrew Purtell wrote:
> Gentle reminder that this vote closes tomorrow evening. If we need more
> time, I can extend it, just say.
>
>
> On Thu, Jun 4, 2015 at 6:01 AM, And
an to look
into adding a test for HBASE-13329. If someone wants to pick that up before
I get to it, I don't complain :)
Let's aim for an RC0 on Monday June 15.
Thanks,
Nick
On Tue, Jun 2, 2015 at 11:06 AM, Nick Dimiduk wrote:
> I've commented on the ticket; this is
+1
On Sat, Jun 13, 2015 at 6:43 PM, Sean Busbey wrote:
> Hey Folks,
>
> I know we've talked before about going Java 8 for master[1], but it's been
> on my mind again lately[2].
>
> I'm in the process of updating the postcommit builds for master to be a
> matrix build to do java 7 and java 8, lik
Sure, in theory :) Let's give it a spin.
On Mon, Jun 15, 2015 at 8:58 PM, Andrew Purtell
wrote:
> +1
>
>
>
> > On Jun 15, 2015, at 8:34 PM, Sean Busbey wrote:
> >
> > We're still using ASF parent pom version 12. current is 17. There are a
> few
> > updates, mostly around default maven plugins (
201 - 300 of 1144 matches
Mail list logo
