On 6/6/18 9:25 AM, Chia-Ping Tsai wrote:
Happy to roll RC1 if folks prefer having that info.
I'm ok with the unknown revision since it won't burn out our cluster.
Ditto. Missed that in my testing; "Unknown" is fine to me too
rc0 passes with 3 binding +1's and one non-binding +1
Thanks to all who have voted!
On 6/2/18 5:26 PM, Josh Elser wrote:
Hi,
Please vote to approve the following as Apache HBase 1.3.2.1
https://dist.apache.org/repos/dist/dev/hbase/1.3.2.1RC0/
Per usual, there is a source release as well
+1 (binding)
On 6/2/18 5:26 PM, Josh Elser wrote:
Hi,
Please vote to approve the following as Apache HBase 1.3.2.1
https://dist.apache.org/repos/dist/dev/hbase/1.3.2.1RC0/
Per usual, there is a source release as well as a convenience binary
This is built with JDK7 from the commit:
https
On 6/4/18 12:16 AM, Stack wrote:
On Sun, Jun 3, 2018 at 8:54 PM, 张铎(Duo Zhang) wrote:
What;s your plan sir? Branch branch-2.1 from branch-2.0?
Its a suggestion.
I like Andrew's notion that we left-shift how we have been thinking about
version numbers; that we releases tend toward minor
Josh Elser created HBASE-20681:
--
Summary: IntegrationTestDriver fails after HADOOP-15406 due to
missing hamcrest-core
Key: HBASE-20681
URL: https://issues.apache.org/jira/browse/HBASE-20681
Project
On 6/4/18 2:45 PM, Stack wrote:
On Mon, Jun 4, 2018 at 11:35 AM, Josh Elser wrote:
Hrm, isn't that a good question!
I just ran the make_rc.sh script, I didn't realize that it didn't also
push a staged repository to Nexus. I assume that means I need to do that by
hand (just a `mvn deploy
with?
On Sat, Jun 2, 2018 at 4:26 PM, Josh Elser wrote:
Hi,
Please vote to approve the following as Apache HBase 1.3.2.1
https://dist.apache.org/repos/dist/dev/hbase/1.3.2.1RC0/
Per usual, there is a source release as well as a convenience binary
This is built with JDK7 from the commit:
https://git-wip
release.
2018-05-17 14:19 GMT+08:00 张铎(Duo Zhang) :
Plan to cut branch-2.1 at the end of May. Will consider the status of
the
new features at that time to determine what will be released with 2.1.x
release line.
2018-05-08 10:16 GMT+08:00 Josh Elser :
Big big big +1
(Came in to say just
[
https://issues.apache.org/jira/browse/HBASE-20579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser reopened HBASE-20579:
If the chown/chgrp fail, the real exception is now not propagated for the user
to see.
{code:java
Hi,
Please vote to approve the following as Apache HBase 1.3.2.1
https://dist.apache.org/repos/dist/dev/hbase/1.3.2.1RC0/
Per usual, there is a source release as well as a convenience binary
This is built with JDK7 from the commit:
Josh Elser created HBASE-20671:
--
Summary: Merged region brought back to life causing RS to be
killed by Master
Key: HBASE-20671
URL: https://issues.apache.org/jira/browse/HBASE-20671
Project: HBase
On 5/31/18 3:57 PM, Sean Busbey wrote:
On Thu, May 31, 2018 at 2:56 PM, Josh Elser wrote:
On 5/24/18 11:16 AM, Sean Busbey wrote:
On Thu, May 24, 2018 at 9:41 AM, Mike Drob wrote:
Are the two issues (HBASE-20615 and HBASE-19735) conflicting, redundant,
or
orthogonal?
I think
On 5/24/18 11:16 AM, Sean Busbey wrote:
On Thu, May 24, 2018 at 9:41 AM, Mike Drob wrote:
Are the two issues (HBASE-20615 and HBASE-19735) conflicting, redundant, or
orthogonal?
I think they're orthogonal, at least as they stand. I think the fact
that HBASE-19735 doesn't e.g. remove the
On 5/24/18 11:16 AM, Sean Busbey wrote:
If we have a minimal client tarball that includes the shaded client and
shaded mapreduce modules (and nothing else?) then are we good to go?
I think if we have a client tarball that includes the shaded client
modules (and other things they need like
Josh Elser created HBASE-20664:
--
Summary: Variable shared across multiple threads
Key: HBASE-20664
URL: https://issues.apache.org/jira/browse/HBASE-20664
Project: HBase
Issue Type: Bug
Josh Elser created HBASE-20640:
--
Summary: TestQuotaGlobalsSettingsBypass missing test category
Key: HBASE-20640
URL: https://issues.apache.org/jira/browse/HBASE-20640
Project: HBase
Issue Type
That seems to be the right semantics to me. If a user doesn't have
permission to make a call, we wouldn't want to call any pre-hook. However...
I'm looking at RSRpcServices to compare and it looks to me that having
the authz check outside of the AccessController CP is weird. For the
methods
Josh Elser created HBASE-20605:
--
Summary: Exclude new Azure Storage FileSystem from
SecureBulkLoadEndpoint permission check
Key: HBASE-20605
URL: https://issues.apache.org/jira/browse/HBASE-20605
[
https://issues.apache.org/jira/browse/HBASE-20599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved HBASE-20599.
Resolution: Duplicate
Fix Version/s: (was: 3.0.0)
Yeesh, I'm striking out today. Dupe
Josh Elser created HBASE-20599:
--
Summary: NPE in HRegionServer.reportFileArchivalForQuotas
Key: HBASE-20599
URL: https://issues.apache.org/jira/browse/HBASE-20599
Project: HBase
Issue Type: Bug
Josh Elser created HBASE-20598:
--
Summary: Upgrade to JRuby 9.2
Key: HBASE-20598
URL: https://issues.apache.org/jira/browse/HBASE-20598
Project: HBase
Issue Type: Bug
Components
Josh Elser created HBASE-20587:
--
Summary: Remove client-side Jackson dependency
Key: HBASE-20587
URL: https://issues.apache.org/jira/browse/HBASE-20587
Project: HBase
Issue Type: Bug
Josh Elser created HBASE-20581:
--
Summary: HBase book documentation wrong for REST operations on
schema endpoints
Key: HBASE-20581
URL: https://issues.apache.org/jira/browse/HBASE-20581
Project: HBase
+1
On 5/9/18 11:58 AM, Andrew Purtell wrote:
Sure, we could try adding a 'Reviewer' assignment field to our issues. That
would be a neat improvement.
On Wed, May 9, 2018 at 8:42 AM, Sean Busbey wrote:
Hi folks!
I was chatting with Umesh yesterday about reviews here in
PM, 张铎(Duo Zhang) wrote:
How do we deal with replication? It is file based...
2018-05-08 10:12 GMT+08:00 Josh Elser <els...@apache.org>:
On 5/7/18 2:53 PM, Stack wrote:
On Thu, May 3, 2018 at 9:04 AM, Josh Elser <els...@apache.org> wrote:
Hi,
... I'm happy to delve some more i
Big big big +1
(Came in to say just this but you beat me to it :D)
On 5/7/18 12:07 AM, 张铎(Duo Zhang) wrote:
Let's do big features in 3.0.0 only.
Ideally there will no big new features for a minor release, so that we can
move the stable pointer to newer minor versions quickly and retire the
On 5/7/18 2:53 PM, Stack wrote:
On Thu, May 3, 2018 at 9:04 AM, Josh Elser <els...@apache.org> wrote:
Hi,
... I'm happy to delve some more into how I think we can implement this.
I'd be interested in this part.
St.Ack
You got it, boss. Let me find the time to get that document ex
services more easily in the
future as well.
This is a minor detail and I'm no expert here (and definitely haven't
thought through all ramifications) but do you still plan on having the WAL
hand out sequenceids or shall that be moved out of that implementation as
well?
Cheers,
Lars
On Thu, May 3, 2
- remove the dependency to hdfs from hbase's write path?
Best Regard,
Chia-Ping
On 2018/05/03 16:04:00, Josh Elser <els...@apache.org> wrote:
Hi,
I'm pleased to finally be able to share this design document with you
all. It's the result of internal review from half a dozen or so from
with
ClayB was telling me last week that he had folks having a hard time
getting to the "current" HBaseCon 2018 page on our site via Google
(apparently they kept sending people to the previous site
hbase.apache.org/www.hbasecon.com)
I just pushed a couple of changes:
1. JS redirect of
Hi,
I'm pleased to finally be able to share this design document with you
all. It's the result of internal review from half a dozen or so from
within our community (Enis, Devaraj, Artem, and Clay easily come to
mind) after multiple months of review and iteration.
Abstract:
Infrastructure
I might be wrong, but I don't think the HFileLink is used in the case
that you're asking about.
I think for your situation (file no longer exists in data/, but is now
in archive/), HBase knows how to find this file purely by knowing
tableName, colfam, region, and file name and checking in
FYI, the mailing list strips images.
There is only one BlockCache per RS. Not sure if that answers your Q1 in
entirety though.
Q2. The "Block" in "BlockCache" are the blocks that make up the HBase
HFiles in HDFS. Data in the Memstore does not yet exist in HFiles on
HDFS. Additionally,
Xu,
Can you be more specific about what you're asking for in a "clientID" or
"clientName"?
Or even better, look at the static methods on the class
org.apache.hadoop.hbase.ipc.RpcServer. There are a number of getters
which use ThreadLocal variables to provide context about the user who
+1 no objections here.
On 4/24/18 11:37 PM, Andrew Purtell wrote:
Let's consider branching for HBase 1.5.
The new feature justifying a minor increment is storage class aware
placement (HBASE-19858), and a required update in Hadoop minimum version.
It would be marked experimental. However,
+1 for the -0 ;)
On 4/25/18 1:32 PM, Stack wrote:
Agree.
If we want to torture a contributor, we can set them on fixing all
complaints.
St.Ack
On Wed, Apr 25, 2018 at 7:28 AM, Sean Busbey wrote:
Hi folks!
Given how often I see us ignoring ruby-lint feedback in
+1 (binding)
On 4/23/18 1:10 AM, Stack wrote:
The third release candidate for Apache HBase 2.0.0 is available for
downloading and testing.
Artifacts are available here:
https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC2/
Maven artifacts are available in the staging repository at:
Josh Elser created HBASE-20468:
--
Summary: RPC quota requests ineffective due to not counting
multi-actions
Key: HBASE-20468
URL: https://issues.apache.org/jira/browse/HBASE-20468
Project: HBase
I like that plan. I'll try to dig into what a "better" fix might be for
the random ports stuff tonight.
On 4/18/18 5:35 PM, Stack wrote:
On Wed, Apr 18, 2018 at 12:58 PM, Josh Elser <els...@apache.org> wrote:
+1 (binding)
There are rough edges, of course, but I think t
+1 (binding)
There are rough edges, of course, but I think this is more than enough
quality for a 2.0.0. Putting a line in the sand for 2.0 will help us
continue to make changes that improve the product going forward with
more focus and get those changes into the hands of folks downstream.
We've received some requests to extend the CFP a few more days. The new
day of closing will be this Friday 2018/04/20, end of day.
Please keep them coming in!
On 4/15/18 9:23 PM, Josh Elser wrote:
The HBaseCon 2018 call for proposals is scheduled to close Monday, April
16th. If you have
The HBaseCon 2018 call for proposals is scheduled to close Monday, April
16th. If you have an idea for a talk, make sure you get it submitted ASAP!
Submit your talks at https://easychair.org/conferences/?conf=hbasecon2018
If you need more information, please see
Was poking around with PE on a few nodes (I forget the exact
circumstances, need to look back at this), and ran into a case where ~35
regions were left as RIT
2018-04-12 22:05:24,431 ERROR
[master/ctr-e138-1518143905142-221855-01-02:16000]
procedure2.ProcedureExecutor: Corrupt pid=3580,
(-to dev, +bcc dev, +to user)
Hi Stefano,
Moving your question over to the user@ mailing list as it's not so much
about development of HBase, instead development when using HBase.
Q1: what do you mean by the "latest field"? Are you talking about the
latest version of a Cell for a column
Oh, and the most important part:
Submit your talks here: https://easychair.org/conferences/?conf=hbasecon2018
On 4/9/18 10:26 PM, Josh Elser wrote:
Hi folks!
A gentle reminder that the HBaseCon 2018 call for proposals remains open
for just one more week -- until April 16th. The event is held
Hi folks!
A gentle reminder that the HBaseCon 2018 call for proposals remains open
for just one more week -- until April 16th. The event is held in San
Jose, CA on June 18th.
We've have some great proposals already submitted, but we look forward
to many, many more. All levels of complexity,
+1 ditto -- this one is better to revert and ask forgiveness on from
users, IMO.
On 4/3/18 3:27 PM, Apekshit Sharma wrote:
+1 on going back to old behavior, i.e. returning values, in branch-1 and
2.0 release.
bq. Open question: should we also revert this change in branch-1.4, even though
it
On 4/3/18 10:38 AM, Sean Busbey wrote:
Over in HBASE-15317 ("document release announcement template
") I had proposed a brief description of our project that sought to
update things to avoid talking about other projects.
at the time (a little over two years ago), stack mentioned that he
liked
No complaints requiring 3.0.5 instead of 3.0.4 (pretty ancient versions
at this point).
A table tracking minVers would be nice as Sean says.
On 4/3/18 9:55 AM, Sean Busbey wrote:
a table listing would be nice, if we end up using different versions
of maven on different release lines.
, Sean Busbey wrote:
-announce, -user
I thought we only announced hbase thirdparty releases on the dev@
list, because it's an artifact that's solely for use internal to the
project?
On Wed, Mar 28, 2018 at 5:27 PM, Josh Elser <els...@apache.org> wrote:
All,
It's my pleasure to announce the
All,
It's my pleasure to announce the 2.1.0 release of the Apache HBase
Thirdparty project. This project is used by the Apache HBase project to
encapsulate a number of dependencies that HBase relies upon and ensure
that they are properly isolated from HBase users, e.g. Google Protocol
Josh Elser created HBASE-20304:
--
Summary: Flip default "return-values" in shell from false to true
Key: HBASE-20304
URL: https://issues.apache.org/jira/browse/HBASE-20304
Project: HBase
Coming full circle: https://github.com/google/protobuf/pull/4411
I got some traction from some acquaintances who actually know ppc64le.
Hopefully we can just drag our feet long enough and will require nothing
from our end :)
On 3/16/18 1:27 PM, Josh Elser wrote:
Hey Duo,
Yeah, that's #1
All,
I'm pleased to announce HBaseCon 2018 which is to be held in San Jose,
CA on June 18th.
A call for proposals is available now[1], and we encourage all HBase
users and developers to contribute a talk and plan to attend the event
(however, event registration is not yet available).
going to publish these and send whatever announcements I can via
available mechanisms :)
Please reach out for any future concerns/suggestions.
On 3/22/18 2:40 PM, Josh Elser wrote:
Thanks Josh for doing this.
Do they have to be conflated so? Each community is doing their own
conference. This page
This passes with 3 binding +1's and 2 non-binding +1's
Thanks everyone!
On 3/19/18 7:15 PM, Josh Elser wrote:
Hi,
Please consider the following as the 2.1.0 release of Apache HBase
Thirdparty.
Source artifact, signatures, and checksums are available at
https://dist.apache.org/repos/dist
Thanks Josh for doing this.
Do they have to be conflated so? Each community is doing their own
conference. This page/announcement makes it look like they have been
squashed together.
Thanks,
S
You have any concrete suggestions I can change?
You have hbasecon+phoenixcon which to me reads as
Thanks.
2018-03-22 0:29 GMT+08:00 Josh Elser <els...@apache.org>:
Hey Duo,
Thanks for digging into this. I am not surprised by it -- last I talked
to
the folks in charge of the website, they mentioned that they would
cross-advertise for us as well. Seems like their web-staff is a bit
fa
On 3/21/18 12:44 PM, Stack wrote:
On Wed, Mar 21, 2018 at 9:26 AM, Josh Elser<els...@apache.org> wrote:
On 3/21/18 2:59 AM, Stack wrote:
On Tue, Mar 20, 2018 at 7:51 PM, Josh Elser<els...@apache.org> wrote:
Hi all,
I've published a new website for the upcoming e
ng
8:30 AM - 5:00 PM
HBaseCon and PhoenixCon
12:00 PM – 7:00 PM
Registration
6:00 PM – 8:00 PM
Meetups
Is this intentional?
2018-03-21 14:59 GMT+08:00 Stack <st...@duboce.net>:
On Tue, Mar 20, 2018 at 7:51 PM, Josh Elser <els...@apache.org> wrote:
Hi all,
I've published a ne
On 3/21/18 2:59 AM, Stack wrote:
On Tue, Mar 20, 2018 at 7:51 PM, Josh Elser <els...@apache.org> wrote:
Hi all,
I've published a new website for the upcoming event in June in California
at [1][2] for the HBase and Phoenix websites, respectively. 1 & 2 are
identical.
I've not y
vent's call for proposals is
available *on on* EasyChair", the double "on" should be merged (smile)
Best Regards,
Yu
On 21 March 2018 at 10:51, Josh Elser <els...@apache.org> wrote:
Hi all,
I've published a new website for the upcoming event in June in California
at [1][2] fo
smile)
Best Regards,
Yu
On 21 March 2018 at 10:51, Josh Elser <els...@apache.org> wrote:
Hi all,
I've published a new website for the upcoming event in June in California
at [1][2] for the HBase and Phoenix websites, respectively. 1 & 2 are
identical.
I've not yet updated any l
Hi all,
I've published a new website for the upcoming event in June in
California at [1][2] for the HBase and Phoenix websites, respectively. 1
& 2 are identical.
I've not yet updated any links on either website to link to the new
page. I'd appreciate if folks can give their feedback on
result.
Thanks
On Mon, Mar 19, 2018 at 4:15 PM, Josh Elser <els...@apache.org> wrote:
Hi,
Please consider the following as the 2.1.0 release of Apache HBase
Thirdparty.
Source artifact, signatures, and checksums are available at
https://dist.apache.org/repos/dist/dev/hbase/hbase-third
Hi,
Please consider the following as the 2.1.0 release of Apache HBase
Thirdparty.
Source artifact, signatures, and checksums are available at
https://dist.apache.org/repos/dist/dev/hbase/hbase-thirdparty/hbase-thirdparty-2.1.0RC0/
Git commit for the release candidate available at
[
https://issues.apache.org/jira/browse/HBASE-19584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved HBASE-19584.
Resolution: Fixed
Assignee: Josh Elser
Hadoop Flags: Reviewed
Thanks, Mike!
> hb
[
https://issues.apache.org/jira/browse/HBASE-19560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved HBASE-19560.
Resolution: Fixed
Hadoop Flags: Reviewed
Pushed. Thanks for the review, Mike!
> create m
On 3/19/18 11:02 AM, Josh Elser wrote:
On 3/16/18 8:06 PM, Stack wrote:
On Fri, Mar 16, 2018 at 3:48 PM, Josh Elser <els...@apache.org> wrote:
No qualms from me. 3.5.1 the desired version?
Yeah. Hopefully just a pom version bump.
The reason that brought me here was nothing that
[
https://issues.apache.org/jira/browse/HBASE-20201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved HBASE-20201.
Resolution: Done
Marking as "Done" – the actual fix will come with the upgrade
Josh Elser created HBASE-20223:
--
Summary: Use hbase-thirdparty 2.1.0
Key: HBASE-20223
URL: https://issues.apache.org/jira/browse/HBASE-20223
Project: HBase
Issue Type: Task
Components
nd Guava
is 24.1 now. We're on 22.
St.Ack
1. https://github.com/google/protobuf/releases
On Fri, Mar 16, 2018 at 1:47 PM, Josh Elser <els...@apache.org> wrote:
Give a shout if there's anything that you all think would be good to
include in a new hbase-thirdparty release for HBase 2.0.
[
https://issues.apache.org/jira/browse/HBASE-20216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved HBASE-20216.
Resolution: Fixed
Hadoop Flags: Reviewed
> [thirdparty] Bundle commons-
Josh Elser created HBASE-20222:
--
Summary: Bundle commons-collections
Key: HBASE-20222
URL: https://issues.apache.org/jira/browse/HBASE-20222
Project: HBase
Issue Type: Task
Components
Josh Elser created HBASE-20221:
--
Summary: Upgrade protobuf to 3.5.1
Key: HBASE-20221
URL: https://issues.apache.org/jira/browse/HBASE-20221
Project: HBase
Issue Type: Task
Components
4.2 or something like that, and I really hope that we don't have to redo
our import statements for each minor release.
On Fri, Mar 16, 2018 at 5:58 PM, Josh Elser <els...@apache.org> wrote:
Yeah, all of the commons-* projects worry me.
Recently, commons-math and commons-collections intr
On 3/16/18 8:06 PM, Stack wrote:
On Fri, Mar 16, 2018 at 3:48 PM, Josh Elser <els...@apache.org> wrote:
No qualms from me. 3.5.1 the desired version?
Yeah. Hopefully just a pom version bump.
The reason that brought me here was nothing that we do in our build
(running MR jo
Josh Elser created HBASE-20216:
--
Summary: [thirdparty] Bundle commons-cli
Key: HBASE-20216
URL: https://issues.apache.org/jira/browse/HBASE-20216
Project: HBase
Issue Type: Improvement
We're on 22.
St.Ack
1. https://github.com/google/protobuf/releases
On Fri, Mar 16, 2018 at 1:47 PM, Josh Elser <els...@apache.org> wrote:
Give a shout if there's anything that you all think would be good to
include in a new hbase-thirdparty release for HBase 2.0.
I'm pulling
on 22.
St.Ack
1. https://github.com/google/protobuf/releases
On Fri, Mar 16, 2018 at 1:47 PM, Josh Elser <els...@apache.org> wrote:
Give a shout if there's anything that you all think would be good to
include in a new hbase-thirdparty release for HBase 2.0.
I'm pulling in co
Give a shout if there's anything that you all think would be good to
include in a new hbase-thirdparty release for HBase 2.0.
I'm pulling in commons-cli as per
https://issues.apache.org/jira/browse/HBASE-20201.
If there's more that should come in, please let me know!
there is a pre complied binary for arm64
available in the central maven repo...
http://central.maven.org/maven2/com/google/protobuf/protoc/3.5.1-1/
There is a 'protoc-3.5.1-1-linux-aarch_64.exe'
So is it possible to do the same thing for ppc?
2018-03-16 4:09 GMT+08:00 Josh Elser <
On 3/15/18 3:45 PM, Stack wrote:
On Thu, Mar 15, 2018 at 12:03 PM, Josh Elser <els...@apache.org> wrote:
I'm faced with what I think is a tricky issue. I'm trying to help folks to
compile HBase on PPC. The protobuf community does not publish a PPC binary
for protoc which means that the
I'm faced with what I think is a tricky issue. I'm trying to help folks
to compile HBase on PPC. The protobuf community does not publish a PPC
binary for protoc which means that the HBase build can't generate our
protobuf files. Protobuf supports: x86/x86_64 for linux, windows, and
osx in
Sent.
On 3/15/18 6:32 AM, Rotem Tamir wrote:
hi
can i get an invite to the hbase slack org?
thx
Josh Elser created HBASE-20201:
--
Summary: HBase must provide commons-cli-1.4 for mapreduce jobs
with H3
Key: HBASE-20201
URL: https://issues.apache.org/jira/browse/HBASE-20201
Project: HBase
No, the principal should definitely get pulled from DNS. Remember that
you must consistently use the same naming to refer to a service when
Kerberos in the mix. This is why the FQDN (and DNS) is so important for
services.
Your issue seems to be that you have multiple different names for a
Josh Elser created HBASE-20199:
--
Summary: Add test to prevent further permission regression around
table flush and snapshot
Key: HBASE-20199
URL: https://issues.apache.org/jira/browse/HBASE-20199
sible for us to require
different permissions for them.
Please open an issue for this, maybe we need to push down the permission
check for execProcedure/execProcedureWithRet down to a place where we
know
the actual type of the procedure.
Thanks.
2018-03-13 3:52 GMT+08:00 Josh Elser <els...@apache
s (ideally, until GA
+ 2-3 weeks) which will give community (whoever interested, at least
me..smile) a decent change to review it.
Thanks
-- Appy
On Tue, Mar 13, 2018 at 1:02 AM, Josh Elser <els...@apache.org> wrote:
(Sorry for something other than just a vote)
I worry seeing a "bi
/Global Admin sounds fine to me.
On Mon, Mar 12, 2018 at 2:21 PM, Josh Elser <els...@apache.org> wrote:
Hi,
In some $dayjob testing, we've noticed that flushing a table requires
ADMIN permission by virtue of submitting the FlushProcedure (not
consciously about the flush operation itself).
ing, summary, etc) - seems rather very large to
get
into
2.0
now. Needs good justification why it has to be 2.1 instead of
2.0.
-- Appy
On Mon, Jan 8, 2018 at 8:34 AM, Josh Elser <els...@apache.org>
wrote:
-0 From a general project planning point-of-view (not based on
the tec
Hi,
In some $dayjob testing, we've noticed that flushing a table requires
ADMIN permission by virtue of submitting the FlushProcedure (not
consciously about the flush operation itself).
I can see this going both ways, but I felt like ADMIN at the table level
is more appropriate than
Sounds beneficial to me and worth the time to run it. Thanks for the
heavy lifting and the head's up!
On 3/9/18 5:07 PM, Mike Drob wrote:
Hi devs,
Over on HBASE-20153[1] I put up a patch to include error-prone[2] compiler
checks on precommit. Wanted to send out a note to the dev list to make
Sounds like a plan to me.
On 3/8/18 9:40 PM, Sean Busbey wrote:
Hi folks!
I've been working to get the test suite back to green on branch-1.2;
we have a lot of branches to track backport for and a non-trivial
amount of tech debt across all of them from the nightlies being
offline.
After the
+1
I would also be supportive of ripping it all out for the reasons that
Andrew already stated.
On 3/6/18 3:22 PM, Stack wrote:
Thanks lads. Let me look at purge of non-user javadocs and at building a
javadoc-only artifiact (then could purge all javadoc as per Andy).
S
On Tue, Mar 6, 2018
Oof, more to do, but I think the list you put together is a good plan to
start. Dropping all but LTS on major version sounds good as well.
Thanks for thinking about this already.
On 3/6/18 12:20 PM, Sean Busbey wrote:
Hi folks!
Our ref guide section on Java versions[1] is starting to look
+1 (binding)
* src release OK
* xsums/sigs OK
* Can build and run from src OK
* Loaded some data locally
On 3/2/18 6:40 PM, Stack wrote:
The first release candidate for HBase 2.0.0-beta-2 is up at
https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-2.RC0/
Maven artifacts are
On 3/5/18 2:40 PM, Stack wrote:
On Mon, Mar 5, 2018 at 6:56 AM, Chia-Ping Tsai wrote:
+1 (binding) with some questions
unit test (oracle jdk-8u161) - all pass
deploy binary (3 nodes) - ok
browse master/regionserver web - LGTM
put/delete/get/scan 500W rows - ok
Josh Elser created HBASE-20131:
--
Summary: NPE in MoveRegionProcedure via
IntegrationTestLoadAndVerify with CM
Key: HBASE-20131
URL: https://issues.apache.org/jira/browse/HBASE-20131
Project: HBase
401 - 500 of 864 matches
Mail list logo