Hello Devs!
I'm happy to announce the second release candidate of HBase 1.1.2
(HBase-1.1.2RC1) is available for download at
https://dist.apache.org/repos/dist/dev/hbase/hbase-1.1.2RC1/
Maven artifacts are also available in the staging repository
https://repository.apache.org/content/repositories/
sitory.
-1 for this RC. There's probably some way I can force maven to use upstream
artifacts in the build, will add that to my scripts. I'll produce RC2 from
he same RC1 tag.
On Fri, Aug 21, 2015 at 5:51 PM, Nick Dimiduk wrote:
>
> > Hello Devs!
> >
> > I'm hap
Hello again devs,
This "third time's the charm" edition release candidate of HBase 1.1.2
(HBase-1.1.2RC2) is available for download at
https://dist.apache.org/repos/dist/dev/hbase/hbase-1.1.2RC2/
Maven artifacts are also available in the staging repository
https://repository.apache.org/content/re
Sounds good to me. Have at it Matteo!
On Thursday, August 27, 2015, Stack wrote:
> Last night at the HBase dev workshop, during discussion of 2.0.0 (what will
> be in it, when will it come out), it was noted that there is as yet no RM
> for hbase-2.0.0.
>
> A bunch of us suggested Matteo and he
m.issuetabpanels:comment-tabpanel#comment-14692493
On Wed, Aug 26, 2015 at 9:16 PM, Nick Dimiduk wrote:
> Hello again devs,
>
> This "third time's the charm" edition release candidate of HBase 1.1.2
> (HBase-1.1.2RC2) is available for download at
> https://dist.apa
at 3:00 PM, Nick Dimiduk wrote:
> +1
>
> - verify signatures vs KEYS file in dist repo
> - verify src tarball has no 'target' paths, jar, or class files
> - verified none of rej, orig, java, or scala files in the bin tgz
> - verified none of rej, orig, class, jar f
.
>
>
Nick
On Mon, Aug 31, 2015 at 3:00 PM, Nick Dimiduk wrote:
>
>> +1
>>
>> - verify signatures vs KEYS file in dist repo
>> - verify src tarball has no 'target' paths, jar, or class files
>> - verified none of rej, orig, java, or scala files
The HBase team is happy to announce the availability of HBase 1.1.2!
Download it from an Apache mirror near you,
http://www.apache.org/dyn/closer.lua/hbase/, or wire up through the maven
repo.
HBase 1.1.2 is the second patch release in the HBase 1.1 line, continuing
on the theme of bringing a stab
I didn't notice a discuss thread over here, so I wanted to bring it up.
What do folks think about marking 1.1.x as the official "stable" release
line? Looks like the HEADER.html [0] file has updated language. With 1.1.2
out, I'd like to also update the "stable" symlink.
Folks good with this?
-n
Hi folks,
I know we just got through voting periods on three patch releases, but
HBASE-14317 is looking pretty bad by my eye. Given we have a fix on our
end, I'm up for spinning 1.1.3 a couple weeks early. How does the community
feel about it? Users: do you need this patch immediately? PMC: do you
Since no further comments here, I've updated the stable symlink.
lrwxr-xr-x1 ndimiduk staff 5 Sep 8 13:57 stable -> 1.1.2
On Wed, Sep 2, 2015 at 6:19 PM, Andrew Purtell wrote:
> +1
>
>
> On Wed, Sep 2, 2015 at 11:26 AM, Nick Dimiduk wrote:
>
> > I d
This is a nice list already Matteo!
+1, I think rolling upgrade should be supported -- said another way, we
need an *extremely* strong argument to justify NOT supporting rolling
upgrade. Your above approach sounds reasonable, and should allow for early
abort of the upgrade (i.e., before all machin
Heya folks,
It seems our list of contributors in JIRA is so long that I'm unable to add
anyone. The fancy ajax autocomplete requests fail, gives me an error
message. I'd like to add Jianwei so they can take credit for their nice
work on HBASE-14443 but JIRA's not having it.
Any thoughts? Maybe we
BASE-14443 to him.
>
Thanks Ted.
> > On Fri, Sep 18, 2015 at 2:47 PM, Nick Dimiduk
> > wrote:
> > >
> > >> Heya folks,
> > >>
> > >> It seems our list of contributors in JIRA is so long that I'm unable
> to
> > add
> > >&g
#x27;s?
>
> Yes, absolutely, and if you'd also like help making the RCs mail me
> privately.
>
> On Fri, Sep 4, 2015 at 8:11 AM, Nick Dimiduk wrote:
>
> > Hi folks,
> >
> > I know we just got through voting periods on three patch releases, but
> > HBA
2_compat_report.html
[2]: http://hbase.apache.org/book.html#hbase.versioning
[3]:
https://issues.apache.org/jira/browse/HBASE-14394?focusedCommentId=14905429&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14905429
On Mon, Sep 21, 2015 at 3:18 PM, Nick Dimiduk wrot
releases. Ugly, but we can rethrow as RuntimeException or ignore in 1.1 and
> before.
>
> I think this is also a blocker:
> https://issues.apache.org/jira/browse/HBASE-14474
>
> Enis
>
> On Wed, Sep 23, 2015 at 3:50 PM, Nick Dimiduk wrote:
>
>> I&#x
Heya folks,
I noticed the above commit is lacking a subject of the proper format.
What's the JIRA for this change? Mind reverting and re-applying with title
as JIRA and Subject? Should be something like
$ git revert 7885499
$ git cherry-pick 7885499
$ git commit --amend ...
confirm commit, and t
Nice work Misty.
For me, the first link [0] looks a lot better than the second link
[1]. I'm with Andrew in that if we're not prepared to actively receive
PR's from github, we should remove the banner. Do you have your patch
for [0], you can send my way and I'll tweak it to remove the banner.
As
> I think once a day for pre 1.1 could work. That's our current stable mark.
+1
> On Wed, Oct 28, 2015 at 2:27 PM, Stack wrote:
>
>> Sounds good to me Sean.
>> St.Ack
>>
>> On Tue, Oct 27, 2015 at 8:47 PM, Sean Busbey wrote:
>>
>> > Heya Folks,
>> >
>> > Right now our post-commit unit tests for
Hi Eric,
Did you ever get to the bottom of this? Maybe you can pastebin some
jstack's while your scanners are running with the different modes?
-n
On Thu, Oct 15, 2015 at 7:58 AM, Eric Owhadi wrote:
> Hi Hbasers,
>
>
>
> I am experimenting with HBase-9272 (a parallel unordered scanner) to
> pro
Apologies for my absence as of late; making some transitions on this
end. I circled back on 1.1 this week, it's well overdue. Looks like
HBASE-14712 is holding up that show. I haven't looked closely at the
conversation there (it's too late tonight, maybe tomorrow evening?).
On Tue, Nov 3, 2015 at
or November. Then we can do it again for December, January,
> etc. Would a google doc spreadsheet help? Or I can just start a discussion
> thread at the start of every month. Let me know.
>
> For November,
>
> 0.98.16 - Andrew
> 1.0.3 - Andrew (thanks, Enis)
> 1.1.3 - ?
>
Hi Zhe,
This is promising! One question: is it possible to enfore fast-forward
only commits when pushing upstream via the web UI? A history full of merge
commits is not very palatable from our community perspective.
Thanks,
Nick
On Thursday, November 5, 2015, Zhe Zhang wrote:
> Hi HBase contri
Heya devs,
Looks like someone pushed branch-1.1.0 back to our repo. It has only a
single commit, which is already on branch-1.1. I tried to delete it, but
the operation failed as "prohibited". Someone with the correct karma mind
deleting this one?
Thanks,
Nick
$ git push apache-rw :branch-1.1.0
; > On Nov 8, 2015, at 5:00 PM, Nick Dimiduk wrote:
> >
> > Heya devs,
> >
> > Looks like someone pushed branch-1.1.0 back to our repo. It has only a
> > single commit, which is already on branch-1.1. I tried to delete it, but
> > the operation failed as "
I'm happy to announce the first release candidate of HBase 1.1.3 (HBase-1.1.
3RC0) is available for download at
https://dist.apache.org/repos/dist/dev/hbase/hbase-1.1.3RC0/
Maven artifacts are also available in the staging repository
https://repository.apache.org/content/repositories/orgapachehbas
I think reopen and reclose is "how it is done."
On Monday, November 9, 2015, Lars Francke wrote:
> Thanks Nicolas, that's good to know. Probably fixed in some kind of
> workflow then. Let's see if someone else has an idea.
>
> On Mon, Nov 9, 2015 at 10:12 AM, Nicolas Liochon > wrote:
>
> > fwiw
tic, might have just been me.
> * Checked sigs/xsums
> * Checked the compat report (thanks for posting it, Nick)
> * Skimmed release notes looking for anything that might introduce new deps
> for licensing concerns (found none)
>
> Nick Dimiduk wrote:
>
>> I'm happy t
I've verified compilation at least of 1.1.x on 2.6 releases. I'm fine with
upgrading "X" to "NT" for this combination.
While we're in there, we should also clarify the meaning of "Not Supported"
vs "Not Tested". It seems we don't say what we mean by these distinctions.
On Fri, Nov 13, 2015 at 7:1
pp runs
successfully.
Thanks,
Nick
[0]: https://github.com/saintstack/hbase-downstreamer
[1]: https://github.com/dminkovsky/HBASE-13889
On Thu, Nov 12, 2015 at 10:58 PM, Nick Dimiduk wrote:
> Thank you Josh for taking time to evaluate this release candidate. A
> reminder to others
annotate as Public or
> LimitedPrivate. Maybe that's why some changes you are expecting to be
> called out are not present in the report?
>
>
> > On Nov 15, 2015, at 3:07 PM, Nick Dimiduk wrote:
> >
> > For my part, my vote is +0, pending review of compatibility r
I can spend a couple hours on backlog. It'll have to be remote though.
On Sun, Nov 15, 2015 at 9:56 PM, Stack wrote:
> Good idea. I'd be game.
> St.Ack
>
> On Sun, Nov 15, 2015 at 2:30 PM, Andrew Purtell
> wrote:
>
> > Hey HBase developers and committers,
> >
> > By any chance, would there be i
You have my consent for auto-commit backports :)
On Fri, Nov 6, 2015 at 10:35 PM, Andrew Purtell wrote:
> Waiting for reviews by committers for these two issues is holding up the
> 0.98.16 release. Any of yea, nay, or 'needs more work' will suffice.
> (smile)
>
> If there's little interest or av
Your LTT ran vs a cluster, or in standalone mode? My run in standalone is
failing consistently due to GC pause. I suppose it's possible my HDD is
failing, but the same test ran without incident with the the 1.1 RC, and
also with the.0.98 RC. Perhaps there's a perf degradation on 1.0 that's
been res
That is something we discussed a while back. There was probably a JIRA for
it too. I think simply no one was willing to take on the massive
search/replace required. IIRC, Mr Purtell experimented with this and found
migration of configuration files to not work as expected.
It would be good to bite
>
>
> > On Nov 16, 2015, at 10:34 PM, Nick Dimiduk > wrote:
> >
> > Your LTT ran vs a cluster, or in standalone mode? My run in standalone is
> > failing consistently due to GC pause. I suppose it's possible my HDD is
> > failing, but the same test ran withou
The problem with a fixup "rampage" is it will very like introduce conflicts
with any patches that are in review process. We have no issue with general
code cleanup. The problem is introducing more work for
contributors/reviewers while it's happening. The cleanup needs to happen in
tandem with compi
> > On Mon, Nov 16, 2015 at 8:35 PM, Andrew Purtell >
> > wrote:
> >
> >> +1
> >>
> >> Checked signature and sums
> >> Unpacked binary and source tarballs, contents look good
> >> Built from source
> >> RAT check passes
> >&
>>
> > > >> I agree. Sorry if I my message was lost in the boring sunday story,
> > but
> > > >> the proposal is only to enable new checkstyles which are listed in
> the
> > > >> first mail so we can know current state of our codebase and
t; if you can (or want to) only give those out for committers.
> >> > >>
> >> > >> On Mon, Nov 9, 2015 at 7:56 PM, Ted Yu > wrote:
> >> > >>
> >> > >>> Lars:
> >> > >>> Resolved issues for released v
+1 in theory. How will this work with integration of javadoc into the site?
How will RM's manage integrating site docs into their releases?
On Wed, Dec 2, 2015 at 8:56 AM, Sean Busbey wrote:
> Hi Folks!
>
> You may recall the occasional emails dev@ gets from a Jenkins job Misty
> set
> up to mak
pc.RpcExecutor$1.run(RpcExecutor.java:108)
> >>at java.lang.Thread.run(Thread.java:745)
> >>
> >>
> >> On Mon, Nov 16, 2015 at 8:35 PM, Andrew Purtell
> >> wrote:
> >>
> >>> +1
> >>>
> >>> Checked signa
-site branch of the hbase-site repo (or whetever it
> is called) and commit the newly-generated target/stage/* to it and push.
> Does that make sense?
>
> On Thu, Dec 3, 2015 at 6:33 AM, Stack wrote:
>
> > Good by me. Interested in the answers to Nicks questions too.
> > St.
ranch-1.1_compat_report.html#Type_Source_Problems_High
On Wed, Dec 2, 2015 at 1:17 PM, Nick Dimiduk wrote:
> With HBASE-14689 resolved, I plan to spin the next RC this weekend. Let me
> know if you have any concerns.
>
> -n
>
> On Tue, Nov 17, 2015 at 8:33 PM, Andrew Purtell
>
branches 1.0 and 1.1 unfixed. We can revert
> this stuff - these changes are at the end of a cascade of changes stemming
> from bug fixing - but then for sake of correct functioning of security
> features we'd want to move people to 1.2.
>
>
>
> > On Dec 6, 2015, a
Yeah, I'll do the same (move 1.1.4 -> 1.1.3) when I prepare release notes
for the next RC.
On Tuesday, December 8, 2015, Stephen Jiang wrote:
> Nick, since 1.1.3 has not out yet. Should all JIRAs resolves as 1.1.4 be
> marked 1.1.3?
>
> I saw Sean moved a bunch of 1.2.1 to 1.2.0. I just wonder
provide default implementations of the new methods?
>
> We did. The addition of the new methods to the interfaces is what is
> triggering the source compatibility warning.
>
>
> On Mon, Dec 7, 2015 at 1:27 PM, Nick Dimiduk wrote:
>
> >
> > So it's either EO
Happy New Year!
I'd like to pick back up the branch-1.1 release. Since we're already busy
with 1.2 and 0.98 is eminent, I'll let the dust settle on at least one of
those releases before posting RC1; probably next week though possibly the
week following, depending on how the votes go.
As always, l
Should we be pushing RC tags into the rel space as well as release tags?
On Tuesday, January 12, 2016, wrote:
> +1
>
>
> From: Enis Söztutar >
> To: "dev@hbase.apache.org " >
> Sent: Monday, January 11, 2016 11:17 AM
> Subject: Re: ASF git repository policy update
>
> +1 on re-tagging
ACK
On Wednesday, January 13, 2016, Sean Busbey wrote:
> no, definitely not. the "rel" space is reserved for PMC-approved releases.
> There's no foundation-backed need to preserve candidates that didn't get
> approved.
>
> On Wed, Jan 13, 2016 at 9:32 AM, Nic
INFRA-10736 was closed and I have successfully deleted this errant branch.
On Sun, Nov 8, 2015 at 5:27 PM, Nick Dimiduk wrote:
> Rgr that: https://issues.apache.org/jira/browse/INFRA-10736
>
> On Sun, Nov 8, 2015 at 5:05 PM, Andrew Purtell
> wrote:
>
>> Nope. Infra has dis
home.apache.org/~ndimiduk/1.1.3RC0_branch-1.1_compat_report.html
[2]: http://home.apache.org/~ndimiduk/1.1.0_1.1.3RC0_compat_report.html
On Mon, Jan 4, 2016 at 11:26 PM, Nick Dimiduk wrote:
> Happy New Year!
>
> I'd like to pick back up the branch-1.1 release. Since we're already b
Thanks for taking a look Jon.
On Fri, Jan 15, 2016 at 9:05 AM, Jonathan Hsieh wrote:
> Nick,
>
> I looked at the three reports look good to me. Usually I'm most concerned
> about removals but HMaster is LimitedPrivate.
>
> Jon
>
> On Thu, Jan 14, 2016 at 10
After a short hiatus, I'm happy to announce the second release candidate of
HBase 1.1.3 (HBase-1.1.3RC1) is available for download at
https://dist.apache.org/repos/dist/dev/hbase/hbase-1.1.3RC1/
Maven artifacts are also available in the staging repository
https://repository.apache.org/content/repo
Can we do that with pre-commit, but leave all supported java versions based
on the branch's compatibility guarantees?
On Tue, Jan 19, 2016 at 2:31 PM, Stack wrote:
> We are running all unit tests with java 1.7 and then 1.8. This is
> effectively doubling the time it takes for an hadoopqa build t
+1
- verified tarballs vs public key in p.a.o/keys/committers/apurtell.asc.
- extracted hadoop1-bin tgz:
- inspect structure. look good.
- run LoadTestTool against standalone built from src tgz with FAST_DIFF
block encoder and ROWCOL blooms. No issues, logs look good.
- poked around webUI. l
t; >
> > > - checked the book in the bin tar
> > >
> > > - checked versions reported
> > >
> > > - checked the compat report
> > >
> > > - compiled with Hadoop 2.3 to 2.7
> > >
> > > - build with hbase-downstreamer
> > >
vetos to date
> can be interpreted as consensus to move forward. There are 2 +1 votes
> already. If you decide to cast a third positive vote, we can release.
>
>
> On Thu, Jan 21, 2016 at 2:32 PM, Nick Dimiduk > wrote:
>
> > > TestDurability is failing in branch-1.1 w
good.
- poked around webUI. looks good.
- inspected compatibility report. Issues look acceptable as per our
policies.
On Mon, Jan 25, 2016 at 7:16 PM, Nick Dimiduk wrote:
> Yes Andrew, that's my conclusion as well. I will evaluate the bits for
> myself this evening. I'll also d
With 3 +1 votes and no 0 or -1 votes, this vote has passed. I will process
these artifacts for distribution as 1.1.3 momentarily. Thanks again for
everyone who took time to review the candidates this release.
Thanks,
Nick
On Mon, Jan 25, 2016 at 9:40 PM, Nick Dimiduk wrote:
> +1
>
> -
> > =ef23
> > -END PGP SIGNATURE-
> >
> > commit 6c98bff7b719efdb16f71606f3b7d8229445eb81
> > Author: Enis Soztutar
> > Date: Sat Feb 14 19:41:51 2015 -0800
> >
> > SNIP...
> >
> > $ git show 1.1.2
> > tag 1.1.2
> > T
The HBase team is happy to announce the immediate availability of HBase
1.1.3! Download it from an Apache mirror near you,
http://www.apache.org/dyn/closer.lua/hbase/, or wire up through the maven
repo.
HBase 1.1.3 is the third patch release in the HBase 1.1 line, continuing on
the theme of bringi
Hi Daniel,
Thanks again for picking this one up and really working it! I'm not clear
on what new infrastructure is needed. The archetypes would be added as new
modules to our existing maven structure, built when existing code is built,
tests run when existing code tests are run, and deployed the s
Heya folks,
I'm sorry to say branch-1.1 is falling behind in terms of backporting fixes
and performance improvements. Anything that's not a new feature and that
doesn't break our compatibility guidelines is explicitly acceptable and
*should* be backported to the active release branches, 0.98 and b
Does anyone have an interest in participating this year? We had a fruitful
summer last year over on Phoenix.
-- Forwarded message --
From: Ulrich Stärk
Date: Wed, Feb 10, 2016 at 12:16 PM
Subject: Google Summer of Code 2016 is coming
To: ment...@community.apache.org
Hello PMCs (
I appreciate Elliot's voice for conservatism on released branches. However
I don't think we're getting minor releases out the door fast enough,
especially when we have nice "improvements" that apply cleanly. Users
deserve to get as many of the improvements as are compatible for patch
releases, acco
Devs,
How are we handling the retirement of old release lines? ASF policy
now requires all release tags be "permanent/archival", which is enforced by
pushing them to the 'rel' space. From my perspective, that means everything
else that's no longer under active development can be deleted. As a rece
as
> > that we likely could have shipped some of the earlier 1.2.0rcs and fixed
> > the criticals in next point release train.
> >
> > Jon.
> >
> >> On Thu, Feb 11, 2016 at 9:45 PM, Nick Dimiduk > wrote:
> >>
> >> I appreciate Elliot&
On Fri, Feb 12, 2016 at 11:44 AM, Sean Busbey wrote:
> I *could* make 1.2.0 RC3 that just cherry picks HBASE-15252 onto RC2, but
> that's going to make things a bit messy and possibly confusing for folks
> who look for the 1.2.0 tag to be an ancestor of branch-1.2's HEAD.
>
We have no strict req
Hi folks,
Looking for confirmation over in the precommit runs on HBASE-15169, it
looks to me like the rerunning of flakies is no longer happening. Used to
be we had junit running a test 3 or 4 times before it was determined to be
a failure. Any pointers on how to get that back?
Thanks,
Nick
On Fri, Feb 26, 2016 at 12:23 PM, Andrew Purtell
wrote:
> In the meantime those of us running HBase in production would benefit from
> fairly frequent minor releases.
>
+1. Having to look back to 0.98 to get some new feature is problematic.
On Fri, Feb 26, 2016 at 9:50 AM, Elliott Clark wrote:
Hello devs,
It's that time again, time for another patch release from branch-1.1. There
are ~40 issues committed and another 5 criticals still open. I'll be
reviewing open tickets and *ahem* encouraging their resolution over the
coming days. Let's aim for first RC published over the weekend.
Sin
or tomorrow. Meanwhile I
checked the compatibility report vs 1.1.3 and everything looks in order.
Thanks,
Nick
On Wednesday, March 2, 2016, Nick Dimiduk wrote:
> Hello devs,
>
> It's that time again, time for another patch release from branch-1.1.
> There are ~40 issues committed a
Sean is looking close on HBASE-14845, HBASE-14844. Anoop is wrapping
up HBASE-15322.
Enis has a patch for HBASE-15295 but could use some review help.
We're nearly there.
On Tue, Mar 8, 2016 at 7:42 AM, Nick Dimiduk wrote:
> A quick update. There's just a couple more issues to r
I'm happy to announce the first release candidate of HBase 1.1.4 (HBase-1.1.
4RC0) is available for download at
https://dist.apache.org/repos/dist/dev/hbase/hbase-1.1.4RC0/
Maven artifacts are also available in the staging repository
https://repository.apache.org/content/repositories/orgapachehbas
On behalf of the Apache HBase PMC, I am pleased to announce that Yu Li
has accepted the PMC's invitation to become a committer on the
project. We appreciate all of Yu's generous contributions thus far and
look forward to his continued involvement.
Congratulations and welcome, Yu!
-n
This is a gentle reminder that the voting window is scheduled to close in
~36 hours.
On Wed, Mar 16, 2016 at 10:13 PM, Nick Dimiduk wrote:
> I'm happy to announce the first release candidate of HBase 1.1.4 (HBase-
> 1.1.4RC0) is available for download at
> https://dist.apache.org/
y next
> week if we can extend the deadline.
>
> > On Mar 19, 2016, at 12:33 PM, Nick Dimiduk wrote:
> >
> > This is a gentle reminder that the voting window is scheduled to close in
> > ~36 hours.
> >
> >> On Wed, Mar 16, 2016 at 10:13 PM, Nick Dim
I think you guys missed enrolling as mentors. From my experience last year,
Goog is very strict about their deadlines, but you'd need to ask over on
the Apache Mentors list.
On Tuesday, March 22, 2016, Enis Söztutar wrote:
> >
> > I didn't sign up for GSOC Talat. Not sure anyone else did either.
from src tgz with GZ
compression and ROWCOL blooms. No issues, logs look good (modulo the usual
GZ codec spew on this platform).
- poked around webUI. looks good.
- inspected compatibility report. Issues look acceptable as per our
policies.
+1
On Wed, Mar 16, 2016 at 10:13 PM, Nick Dimiduk wrote
It would be great to get one more pair of eyes on this before we mint it. I
know we have the required number of votes, but still...
On Wednesday, March 23, 2016, Nick Dimiduk wrote:
> For my own review:
>
> - verified tarballs vs public key in p.a.o/keys/committers/ndimiduk.asc.
>
This vote passes with 4 binding +1's and no other votes cast.
Thanks to all who took the time to review this RC.
On Wed, Mar 16, 2016 at 10:13 PM, Nick Dimiduk wrote:
> I'm happy to announce the first release candidate of HBase 1.1.4 (HBase-
> 1.1.4RC0) is available for dow
The HBase team is happy to announce the immediate availability of HBase
1.1.4! Download it from an Apache mirror near you,
http://www.apache.org/dyn/closer.lua/hbase/, or wire up through the maven
repo.
HBase 1.1.4 is the fourth patch release in the HBase 1.1 line, continuing
on the theme of bring
Nice work Francis, congrats!
On Thursday, April 7, 2016, Stack wrote:
> Francis has been around forever looking after one of the biggest HBase
> deploys. He has contributed a bunch of big features during this time --
> namespacing and grouping to mention a few -- and has more coming down the
> p
+1
On Thursday, April 7, 2016, Stack wrote:
> Any objection?
>
> jdk7 is dead, EOL'd.
>
> You all good w/ this?
>
> St.Ack
>
Thanks for all the contributions Ashish!
On Thursday, April 7, 2016, Stack wrote:
> Ashish has contributed loads of stuff starting out basic doing rakes of
> simple fixes but then ramping up to take on the hard stuff going out of his
> way to land the 'best' fix. He's been doing great work. Keep
I'm good with it, though I'll also ask the question if there's anything
goofy to be aware of re: HBase as someone upgrades their Hadoop? Probably
nothing, but I've been surprised before; would be good to leave some
breadcrumbs in our book.
On Thursday, April 7, 2016, Stack wrote:
> Currently 1.2
Hey guys,
Looks like the last site update missed something. Grammar, Functions, and
Data Types pages are all empty. Mind taking a look?
Thanks,
Nick
http://phoenix.apache.org/language/index.html
http://phoenix.apache.org/language/functions.html
http://phoenix.apache.org/language/datatypes.html
On Tue, Apr 19, 2016 at 1:24 PM, Stack wrote:
> Which pages Nick?
> St.Ack
>
> On Tue, Apr 19, 2016 at 1:00 PM, Nick Dimiduk wrote:
&g
Oh bother. Wrong dev list. Sorry guys.
On Tue, Apr 19, 2016 at 1:25 PM, Nick Dimiduk wrote:
> http://phoenix.apache.org/language/index.html
> http://phoenix.apache.org/language/functions.html
> http://phoenix.apache.org/language/datatypes.html
>
> On Tue, Apr 19, 2016 at 1:24 P
Heya folks,
It's getting to be time for the next patch release on 1.1. Are there any
tickets you're actively tracking specifically for this release? Please let
me know. In the mean time, I'll be doing my issues sweep and compatibility
testing.
Thanks,
Nick
Compat report is looking nice and clean this time around:
http://home.apache.org/~ndimiduk/1.1.4_branch-1.1_compat_report.html
On Mon, Apr 25, 2016 at 10:10 AM, Stack wrote:
> Thanks Nick,
> St.Ack
>
> On Thu, Apr 21, 2016 at 4:00 PM, Nick Dimiduk wrote:
>
> > Heya folks,
I'm not such a huge slack fan, but I'm also becoming curmudgeonly. Sure,
why not? If that's where people want to gather. You creating a room? How to
make it "official"?
On Mon, Apr 25, 2016 at 4:22 PM, Stack wrote:
> On Mon, Apr 25, 2016 at 4:05 PM, Apekshit Sharma
> wrote:
>
> > "Committers sh
; Which should we choose going forward?
>
> The main goal is to hangout in a room so that it's easy to ping people for
> short discussions/clarifications.
>
>
> On Mon, May 2, 2016 at 8:57 PM, Nick Dimiduk wrote:
>
> > I'm not such a huge slack fan, but I'
As of 0.96 hbase has become a multi-module project. The artifact to which
you're referring is now the parent pom. You'll need to update your projects
to consume the new structure, and perhaps the new APIs as well.
There's also work on adding maven archetypes in progress. I believe we have
a mapred
What's up with this branch-2? Seems like it's back after Sean's HBASE-15006.
local
> instance of phoenix and attached a debugger to see why we needed the
> constant rebuild of meta data.
>
> Sorry, I wish I could help more, but if you can share your table
> definition, I can keep an eye in the next few weeks when I play with
> PHOENIX-2607.
>
> Thanks
&
se/commits/branch-2
>
> Matteo
>
>
> On Sun, May 8, 2016 at 6:08 PM, Nick Dimiduk wrote:
>
> > What's up with this branch-2? Seems like it's back after Sean's
> > HBASE-15006.
> >
>
*** Please note that my key expired since the previous release. I have
updated its expiration, pushed to pgp.mit.edu, updated the KEYS file linked
below, and attempted to force an update on id.apache.org. I don't know how
long it will take for people.apache.org to refresh. ***
*** Please note that
701 - 800 of 1799 matches
Mail list logo
