[
https://issues.apache.org/jira/browse/HBASE-18795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ramkrishna.s.vasudevan resolved HBASE-18795.
Resolution: Fixed
Hadoop Flags: Reviewed
Resolved the issue. Thanks f
[
https://issues.apache.org/jira/browse/HBASE-10504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-10504.
---
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.0.0
Marking as 'done' in 2.0.0.
HBASE-
stack created HBASE-18846:
-
Summary: Accommodate the hbase-indexer/lily/SEP consumer
deploy-type
Key: HBASE-18846
URL: https://issues.apache.org/jira/browse/HBASE-18846
Project: HBase
Issue Type: Bu
I'm going to do a monthly cadence with 1.4.
It's a bit delayed getting off the ground sadly because I need to address
Francis' feedback and otherwise get RSGroups in before cutting the first RC,
and I was recently out for two weeks on vacation. Soon, though.
Or, we can start spinning minors o
Heya,
I noticed tonight that I've been remiss in closing tickets after the dust
settles around a release. I think it's something I/we did, once upon a
time. However, I don't see any mention of it in the ref guide around
releases. Is this something that should be done? Can you point me to our
exist
Reviving this thread. I know our interest is around branch-2 right now, but
I think we are close to an actionable resolution here.
I'm a fan of Andrew's proposal of stabilizing our branch-1 for maintenance
releases, getting away from all the minors if we can. Do we have a quorum
of folks able and
Heya folks,
There's slim commits to branch-1.1 over the last month. Looks like nothing
pressing by my eyes, so I'm going to let the branch simmer for another
month, let more changes accumulate. Will check back in with you in early
October.
Reply here if you have strong feeling to the contrary.
K
Duo Zhang created HBASE-18845:
-
Summary: TestReplicationSmallTests fails after HBASE-14004
Key: HBASE-18845
URL: https://issues.apache.org/jira/browse/HBASE-18845
Project: HBase
Issue Type: Bug
stack created HBASE-18844:
-
Summary: Release hbase-2.0.0-alpha-4; Theme "Coprocessor API
Cleanup"
Key: HBASE-18844
URL: https://issues.apache.org/jira/browse/HBASE-18844
Project: HBase
Issue Type: B
[
https://issues.apache.org/jira/browse/HBASE-18767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-18767.
---
Resolution: Fixed
Assignee: stack
Fix Version/s: (was: 2.0.0-alpha-4)
2
Vladimir Rodionov created HBASE-18843:
-
Summary: Add DistCp support to incremental backup with bulk loading
Key: HBASE-18843
URL: https://issues.apache.org/jira/browse/HBASE-18843
Project: HBase
[
https://issues.apache.org/jira/browse/HBASE-14417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu resolved HBASE-14417.
Resolution: Fixed
> Incremental backup and bulk loading
> ---
>
>
[
https://issues.apache.org/jira/browse/HBASE-14417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Rodionov reopened HBASE-14417:
---
Assignee: Vladimir Rodionov (was: Ted Yu)
> Incremental backup and bulk loading
>
Thoralf Gutierrez created HBASE-18842:
-
Summary: The hbase shell clone_snaphost command returns bad error
message
Key: HBASE-18842
URL: https://issues.apache.org/jira/browse/HBASE-18842
Project: H
I think this is a good idea. Having a list documented itself is big plus.
Explicitly listing Required/ Mandatory checks and Optional checks for
release type (e.g. alpha, beta etc) will help too.
On Mon, Sep 18, 2017 at 1:10 PM, Andrew Purtell wrote:
> I also think it's fair to make allowances fo
One thing that I've seen in successful other communities is that when folks
run the long running tests they also document the specifics of the
configuration that they used. Things like your java version, operating
system, EC2 instance type. Then this all gets fed into a table published
with the rel
stack created HBASE-18841:
-
Summary: ./bin/hbase ltt and pe cannot find their classes when in
dev/build context
Key: HBASE-18841
URL: https://issues.apache.org/jira/browse/HBASE-18841
Project: HBase
I also think it's fair to make allowances for folks who want to test the RC
but might be short on personal time. So there should be a list of essential
items (like sigs, sums, shas/tags) and then a list of optional items (ltt,
pe, itbll, etc.)
On Mon, Sep 18, 2017 at 12:52 PM, Stack wrote:
> On
On Mon, Sep 18, 2017 at 11:49 AM, Misty Stanley-Jones
wrote:
> I keep feeling like we need a checklist for all the different things that
> should be tested when people vote on a release candidate. Not everyone
> needs to do all the checks, but probably at least someone should be doing
> each of t
Big +1. I opened HBASE-16559 to start working on this last year, but then
life happened.
-Dima
On Mon, Sep 18, 2017 at 11:53 AM, Ted Yu wrote:
> bq. have some kind of dashboard where people could "sign up" to test
> different things on that checklist
>
> This makes sense.
> +1
>
>
> On Mon, Sep
The HBase team is happy to announce the immediate availability of Apache
HBase
2.0.0-alpha-3.
Apache HBase is an open-source, distributed, versioned, non-relational
database. Apache HBase gives you low latency random access to billions of
rows with millions of columns atop non-specialized hardware
bq. have some kind of dashboard where people could "sign up" to test
different things on that checklist
This makes sense.
+1
On Mon, Sep 18, 2017 at 11:49 AM, Misty Stanley-Jones
wrote:
> I keep feeling like we need a checklist for all the different things that
> should be tested when people v
Zach York created HBASE-18840:
-
Summary: Add functionality to refresh meta table at master startup
Key: HBASE-18840
URL: https://issues.apache.org/jira/browse/HBASE-18840
Project: HBase
Issue Typ
I keep feeling like we need a checklist for all the different things that
should be tested when people vote on a release candidate. Not everyone
needs to do all the checks, but probably at least someone should be doing
each of the following (and maybe things I am forgetting):
- Binary .tar.gz and
With 4 binding +1s and 3 non-binding, the VOTE passes.
Thank you to all who voted, especially the non-PMCers. Them votes look
really pretty.
Let me push out alpha-3.
Alpha-4 with better scripted RM'ing and Coprocessor API cleanup coming
right up!
St.Ack
On Mon, Sep 18, 2017 at 9:31 AM, Josh
Chia-Ping Tsai created HBASE-18839:
--
Summary: Region#getRegionInfo should return Region instead of
HRegion
Key: HBASE-18839
URL: https://issues.apache.org/jira/browse/HBASE-18839
Project: HBase
Speaking on behalf of one HBase deployment, we do rely on custom filters,
though have so far stayed away from more internal customizations such as
co-processors. We've gotten the sense over the years that Filters were
fairly stable and seemed more reliable in that sense. I'd be sad if a
change li
+1 (binding)
* Build from src
* Can run pseudo-dist standalone with built software
* XSums/Sigs OK
- Josh
On 9/15/17 2:03 PM, Stack wrote:
The first release candidate for HBase 2.0.0-alpha-3 is up at:
https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha-3RC0/
Maven artifacts are
+1
Sums and signatures are ok. That's as far as I got.
LTT is my go to test so normally if it fails I'd veto but this is an alpha
release. Also, several unit tests are failing, so I don't get a good build,
but it's an alpha release so I won't veto on that account either
(especially).
> (all of
[
https://issues.apache.org/jira/browse/HBASE-18811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved HBASE-18811.
Resolution: Later
> Introduce the limited private to filter
> -
Sean Busbey created HBASE-18838:
---
Summary: shaded artifacts are incorrect when built against hadoop 3
Key: HBASE-18838
URL: https://issues.apache.org/jira/browse/HBASE-18838
Project: HBase
Issu
On Sun, Sep 17, 2017 at 9:50 PM, Sean Busbey wrote:
> +1
>
> good:
>
> * checksums are all good
> * signatures are all good
> * spot check of LICENSE / NOTICE looks okay (spat of "optional"
> call-outs in NOTICE could be removed)
> * source can build binary tarball that matches convenience
> tarb
Thanks all for the wonderful votes. I need another PMC'er for the vote to
pass...
Thanks,
M
On Fri, Sep 15, 2017 at 11:03 AM, Stack wrote:
> The first release candidate for HBase 2.0.0-alpha-3 is up at:
>
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha-3RC0/
>
> Maven artifact
chausson created HBASE-18837:
Summary: HTableMultiplexer behavior during regions split
Key: HBASE-18837
URL: https://issues.apache.org/jira/browse/HBASE-18837
Project: HBase
Issue Type: Improveme
+1 (non-binding)
- verified signature
- verified checksum
- checked licenses
- built from source on tag 2.0.0-alpha-3RC0.2
- build hbase from src tarball
- checked UI
- basic functionalities of hbase shell
On Mon, Sep 18, 2017 at 1:22 PM, ashish singhi
wrote:
> +1(non-binding)
>
> Built tar fro
Sean Busbey created HBASE-18836:
---
Summary: fix shaded jar for javax.el
Key: HBASE-18836
URL: https://issues.apache.org/jira/browse/HBASE-18836
Project: HBase
Issue Type: Bug
Component
+1(non-binding)
Built tar from source code
Verified few commands on shell and other few from Java API, all looks ok
Verified audit logs
Verified HBase replication on a single node cluster, checked metrics
Checked zk_dump and web UI, looks ok
Regards,
Ashish
-Original Message-
From: saint
Chia-Ping Tsai created HBASE-18835:
--
Summary: The return type of ExtendedCell#deepClone should be
ExtendedCell rather than Cell
Key: HBASE-18835
URL: https://issues.apache.org/jira/browse/HBASE-18835
38 matches
Mail list logo