(+1 non-Binding)
1. Checksums and signatures(both src and bin): OK
2. Rat Check: OK
3. Built from source: OK
4. Unit Tests: OK
5. Basic Shell commands: OK
6. Web UI: OK
7. LTT with 10^5 rows: OK
Thanks stack.
On Wed, Mar 20, 2019 at 10:44 PM Stack wrote:
> Please vote on
stack created HBASE-22076:
-
Summary: Move version on from 2.2.0 to 2.2.1-SNAPSHOT
Key: HBASE-22076
URL: https://issues.apache.org/jira/browse/HBASE-22076
Project: HBase
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/HBASE-22076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-22076.
---
Resolution: Fixed
Assignee: stack
Resolving.
Did this:
$ mvn versions:set
Vladimir Rodionov created HBASE-22075:
-
Summary: Potential data loss when MOB compaction fails
Key: HBASE-22075
URL: https://issues.apache.org/jira/browse/HBASE-22075
Project: HBase
The motivation for contributing opensource work sometimes affected by
projects' popularity. And open source as a whole is hugely impacted by
public cloud companies since their profit-driven mindset. One of the
biggest public cloud provider even discourages employees from contributing
to open
I think the complexities of actually using HBase is a fairly large
impediment since it limits our user base (where most of the contributors
are likely coming from). HBase is a complex machine and requires someone to
have a significant amount of knowledge of the internal workings to manage.
I think
Ok, that said, given these conditions the best thing we can do is lower
friction so contributors can solve problems for themselves. Things like
github PRs can help. That is the wide part of the funnel.
However a project like hbase has inherent complexity of the code and it’s
enviroment.
I don’t think it is realistic, unfortunately. If you remember our OWNERS
initiative, which failed, the idea there was for various functional areas
or components there would in effect be a mentor, someone you could
at-mention for advice and review. This failed because if this isn’t your
full time
[
https://issues.apache.org/jira/browse/HBASE-21955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-21955.
---
Resolution: Duplicate
Marking as duplicate. The parent script does this.
> Auto insert release changes and
Another open source project I’m on is exploring the idea of a mentoring
rotation where each mentor serves for a week and especially looks out for
and provides practical assistance and review to new contributors for that
week, on an office-hours type of basis. Many hands make light work. WDYT?
I’d
+1 one for the mentoring if one existing member who knows the feature plan
and is willing to create tasks for pickup.
my current barrier is to find a continuous topic/component and focus on it,
but I'm a bit too random with my approach.
Currently, not sure this is the right way, I lookup JIRAs
Please vote on this Apache HBase release candidate (RC), 2.1.4.
The VOTE will remain open for at least 72 hours.
[ ] +1 Release this package as Apache HBase 2.1.4
[ ] -1 Do not release this package because ...
The tag to be voted on is 2.1.4RC1:
https://github.com/apache/hbase/tree/2.1.4RC1
Duo Zhang created HBASE-22074:
-
Summary: Should use procedure store to persist the state in
reportRegionStateTransition
Key: HBASE-22074
URL: https://issues.apache.org/jira/browse/HBASE-22074
Project:
Balazs Meszaros created HBASE-22073:
---
Summary: /rits.jsp throws an exception if no procedure
Key: HBASE-22073
URL: https://issues.apache.org/jira/browse/HBASE-22073
Project: HBase
Issue
+1 for hbase-native-client repo.
You can create a new gitbox repository on https://gitbox.apache.org/ by
filling out a simple form.
On Wed, Mar 20, 2019 at 8:48 AM Guanghao Zhang wrote:
> I am +1 to push the hbase-native-client to a new git repo. One more
> question, how to create a new repo in
Pavel created HBASE-22072:
-
Summary: High read/write intensive regions may cause long crash
recovery
Key: HBASE-22072
URL: https://issues.apache.org/jira/browse/HBASE-22072
Project: HBase
Issue
Guanghao Zhang created HBASE-22071:
--
Summary: Create an hbase-native-client repository and commit the
native client code to it
Key: HBASE-22071
URL: https://issues.apache.org/jira/browse/HBASE-22071
I am +1 to push the hbase-native-client to a new git repo. One more
question, how to create a new repo in gitbox? Do we have some ref guide for
this? Thanks.
Sean Busbey 于2019年3月14日周四 下午9:58写道：
> I'd also like to see the native client in its own repo. Dealing with a
> new build system for C++
Would be great to have mentors. Ted used to review my patches and provide
feedback on timely basis, understand everyone is busy but would be nice to
have a point person (per feature, bug, branch, module, etc). I have cycles
to burn but currently it feels a bit overwhelming as community may feel
19 matches
Mail list logo
