stack created HBASE-20936:
-
Summary: BaseLoadBalancer throws ArrayIndexOutOfBoundsException
Key: HBASE-20936
URL: https://issues.apache.org/jira/browse/HBASE-20936
Project: HBase
Issue Type: Bug
I like the idea of a separate connectors repo/release vehicle, but I'm a
little concerned about the need to release all together to update just one
of the connectors. How would that work? What kind of compatibility
guarantees are we signing up for?
On Tue, Jul 24, 2018, 9:41 PM Stack wrote:
>
Vishal Khandelwal created HBASE-20935:
-
Summary: HStore.removeCompactedfiles should log incase it unable
to delete a file
Key: HBASE-20935
URL: https://issues.apache.org/jira/browse/HBASE-20935
Grand. I filed https://issues.apache.org/jira/browse/HBASE-20934. Let me
have a go at making the easy one work first (the kafka proxy). Lets see how
it goes. I'll report back here.
S
On Tue, Jul 24, 2018 at 2:43 PM Sean Busbey wrote:
> Key functionality for the project's adoption should be in
stack created HBASE-20934:
-
Summary: Create an hbase-connectors repository; commit new kafka
connect here
Key: HBASE-20934
URL: https://issues.apache.org/jira/browse/HBASE-20934
Project: HBase
Vishal Khandelwal created HBASE-20933:
-
Summary: multiple splits may result into forever uncleaned split
region
Key: HBASE-20933
URL: https://issues.apache.org/jira/browse/HBASE-20933
Project:
Better mention the release manager when you want to commit to the branch.
If no response in a day or so then just go head. At least for 2.1 you can
follow this rule.
2018-07-25 11:06 GMT+08:00 Guanghao Zhang :
> So only branch-2.0 need RM's approval. For other release
> branchs(1.2/1.3/1.4/2.1),
So only branch-2.0 need RM's approval. For other release
branchs(1.2/1.3/1.4/2.1), they are same with trunk branch and only need one
+1 from a committer, right?
2018-07-24 7:37 GMT+08:00 Stack :
> On Mon, Jul 23, 2018 at 3:44 PM Josh Elser wrote:
>
> > I've been operating under the "get
Mingliang Liu created HBASE-20932:
-
Summary: Effective MemStoreSize::hashCode()
Key: HBASE-20932
URL: https://issues.apache.org/jira/browse/HBASE-20932
Project: HBase
Issue Type: Bug
Hi Andrew,
On Wed, Jul 25, 2018 at 3:21 AM Andrew Purtell wrote:
> Thanks for this note.
>
> I'm release managing the 1.4 release. I have been running the unit test
> suite on reasonably endowed EC2 instances and there are no observed always
> failing tests. A few can be flaky. In comparison
[
https://issues.apache.org/jira/browse/HBASE-20931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell resolved HBASE-20931.
Resolution: Fixed
> [branch-1] Add -Dhttps.protocols=TLSv1.2 to Maven command line in
Andrew Purtell created HBASE-20931:
--
Summary: [branch-1] Add -Dhttps.protocols=TLSv1.2 to Maven command
line in make_rc.sh
Key: HBASE-20931
URL: https://issues.apache.org/jira/browse/HBASE-20931
Thanks Stack, Josh and Andrew for your suggestions and concerns.
I share Stack's suggestions. This would be similar to hbase-thirdparty. The
new repo could be hbase-hbck/hbase-hbck2. As this tool will be used by
hbase users/ developers, hbase JIRA can be used for hbck issues.
bq. How often does
Key functionality for the project's adoption should be in the project.
Please do not suggest we donate things to Bahir.
I apologize if this is brisk. I have had previous negative experiences
with folks that span our communities trying to move work I spent a lot
of time contributing to within
Why not just donating the connector to http://bahir.apache.org/ ?
On Tue, Jul 24, 2018, 12:51 PM Lars Francke wrote:
> I'd love to have the Kafka Connector included.
>
> @Mike thanks so much for the contribution (and your planned ones)
>
> I'm +1 on adding it to the core but I'm also +1 on
Hey Krish, please subscribe using instructions below
https://hbase.apache.org/mail-lists.html
On Tue, Jul 24, 2018 at 2:18 PM Krish Dey wrote:
> Please send me an invite and let me join.
>
[
https://issues.apache.org/jira/browse/HBASE-20928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xu Cang reopened HBASE-20928:
-
> Rewrite calculation of midpoint in binarySearch functions to prevent overflow
>
Please send me an invite and let me join.
If we do this can we also move out hbck version 1? It would be really weird
in my opinion to have v2 in a separate repo but v1 shipping with the 1.x
releases. That would be a source of understandable confusion.
I believe our compatibility guidelines allow us to upgrade interface
annotations from
Thanks for this note.
I'm release managing the 1.4 release. I have been running the unit test
suite on reasonably endowed EC2 instances and there are no observed always
failing tests. A few can be flaky. In comparison the Apache test resources
have been heavily resource constrained for years and
I'd love to have the Kafka Connector included.
@Mike thanks so much for the contribution (and your planned ones)
I'm +1 on adding it to the core but I'm also +1 on having a separate
repository under Apache governance
On Tue, Jul 24, 2018 at 6:01 PM, Josh Elser wrote:
> +1 to the great point
-builds@
this is perhaps good incentive for us to move forward on
branch-specific flaky tests so that we can move these out of the
nightly build automagically. (which is getting tracked in HBASE-20387)
Maybe in a week or three I'd have time to do it myself (and I gotta
get HBASE-20834 done
I suspect the bigger issue is that the hbase tests are running on the
‘ubuntu’ machines. Since they only have ~300GB for workspaces, the hbase tests
are eating a significant majority of it and likely could be dying randomly due
to space issues. [All the hbase workspace directories +
+1 to the great point by Duo about use of non-IA.Public classes
+1 for Apache for the governance (although, I wouldn't care if we use
Github PRs to try to encourage more folks to contribute), a repo with
the theme of "connectors" (to include Thrift, REST, and the like). Spark
too -- I think
Yep, sadly this is a very long tent-pole for us. There are many involved
who have invested countless hours in making this better.
Specific to that job you linked earlier, 3 test failures out of our
total 4958 tests (0.06% failure rate) is all but "green" in my mind. I
would ask that you keep
(-cc user as this I'm getting purely into code development topics)
First off, thanks for working on an hbck2, Umesh!
I like the idea of having a separate repository for tracking HBCK and
the flexibility it gives us for making releases at a cadence of our
choosing.
There are two worries that
Hi everyone,
I'm the author of the patch. A separate repo for all the connectors is a
great idea! I can make whatever changes necessary to the patch to help.
I have several other integration type projects like this planned.
Mike
On Tue, Jul 24, 2018, 00:03 Mike Drob wrote:
> I would be ok
[
https://issues.apache.org/jira/browse/HBASE-20861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pankaj Kumar resolved HBASE-20861.
--
Resolution: Duplicate
Closing this Jira as duplicate now, will handle this issue in
Ok, good enough, will wait, please also note 'master' branch and a few
others have been failing for over a month also.
I will check in again next month to see how things are progressing
Thanks
Gav...
On Tue, Jul 24, 2018 at 1:19 AM Josh Elser wrote:
> Hi Gav,
>
> Looking at the most recent
Vishal Khandelwal created HBASE-20930:
-
Summary: MetaScanner.metaScan should use passed variable for meta
table name rather than TableName.META_TABLE_NAME
Key: HBASE-20930
URL:
Vishal Khandelwal created HBASE-20929:
-
Summary: IncreasingToUpperBoundRegionSplitPolicy -> shouldSplit ->
Log.debug should be enclosed inside LOG.isdebugEnabled()
Key: HBASE-20929
URL:
31 matches
Mail list logo
