Re: Using Github for Contributions & Reviews

2019-02-06 Thread Brock Noland
I assume if we used Github PR's we configure merges to occur without merge commits? I find them very confusing. On Wed, Feb 6, 2019 at 9:57 AM Grant Henke wrote: > Hello Kudu Developers, > > Now that Apache is integrated more closely with Github via Gitbox > I wanted

KUDU-1563 - Add support for INSERT IGNORE

2018-12-04 Thread Brock Noland
Hi all, There is renewed effort on the INSERT IGNORE feature. I have just proposed a new description of how it will work on the JIRA. https://issues.apache.org/jira/browse/KUDU-1563 If you have an interest in this feature, please share the feedback in that JIRA so we can get a consensus around t

Re: RFC: dropping Python 2.6 support

2018-08-07 Thread Brock Noland
+1 Even if it wasn't easy to install, for our part, our customer based is heavily RH7, at least 80%, which is likely part of a broader trend. On Tue, Aug 7, 2018 at 6:42 PM, Adar Lieber-Dembo wrote: > While working on yet another Python 2.6 compatibility fix for the Kudu > Python wrapper, I sta

Re: Growing the Kudu community

2018-07-23 Thread Brock Noland
On Mon, Jul 23, 2018 at 1:06 PM Mike Percy wrote: > On Mon, Jul 23, 2018 at 10:46 AM Sailesh Mukil > > wrote: > > > On Tue, Jul 17, 2018 at 7:37 PM, Mike Percy wrote: > > Once backup and restore has stabilized we could push some example data sets > to S3 and allow people to restore locally from

Re: [VOTE] Apache Kudu 1.5.0 RC3

2017-09-07 Thread Brock Noland
+1 (non-binding) sigs/checksums, release build on centos 6.6, all tests passed On Wed, Sep 6, 2017 at 1:28 PM, Andrew Wong wrote: > +1 (non-binding) > > Built and ran in release mode on macOS 10.12.4 (kudu-tool-test failed, > mentioned > above to be a known issue) and with TSAN on CentOS 6.6 (a

Re: Allow user spoofing in insecure clusters?

2017-06-21 Thread Brock Noland
+1 - really useful in Hadoop for non-secure clusters. On Wed, Jun 21, 2017 at 1:00 PM, Jean-Daniel Cryans wrote: > +1, might as well allow it. > > On Wed, Jun 21, 2017 at 10:52 AM, Todd Lipcon wrote: > >> Hey folks, >> >> I had the occasion yesterday of trying to run an admin tool from my laptop

Re: [VOTE] Apache Kudu 1.4.0 RC2

2017-06-12 Thread Brock Noland
+1 (non-binding) Built and ran tests On Mon, Jun 12, 2017 at 9:49 AM, Jean-Daniel Cryans wrote: > Err sorry I meant to vote on Friday but then Happy Hour happened :) > > +1, ran the same verifications as for RC1. > > FWIW one of my test clusters hit the issue that killed RC1 after I had > voted

Re: The problem of show tables

2017-05-27 Thread Brock Noland
Hi, Cross-posting lists is generally frowned up. I'd suggest you email only one list at a time in the future. Sounds like you created it in Kudu but not impala. Impala needs a pointer to the table. You should create an external table in Impala: https://www.cloudera.com/documentation/enterprise/5-1

Re: [VOTE] Apache Kudu 1.2.0 RC1

2017-01-18 Thread Brock Noland
+1 (non-binding) build and ran tests on el6 On Wed, Jan 18, 2017 at 12:27 PM, Dan Burkert wrote: > Little bit late to the party, but release LGTM. Compiled and passed all > tests on OS X 10.10. > > - Dan > > On Wed, Jan 18, 2017 at 8:48 AM, William Berkeley > wrote: > > > Yeah I'm ok with pas

Re: Adding some guard rails to Kudu

2016-11-30 Thread Brock Noland
+1 Very reasonable approach and like that there is a semi-hard to use safety valve. On Wednesday, November 30, 2016, Todd Lipcon wrote: > BTW I filed a JIRA here and started linking related issues to it: > https://issues.apache.org/jira/browse/KUDU-1775 > > > On Wed, Nov 30, 2016 at 3:25 PM, To

Re: [VOTE] Apache Kudu 1.1.0 RC1

2016-11-17 Thread Brock Noland
+1 (non-binding) Built on 7.2 and ran tests On Monday, November 14, 2016, Todd Lipcon wrote: > Hi, > > The Apache Kudu team is happy to announce the first release candidate for > Apache Kudu 1.1.0. > > Apache Kudu 1.1 is a minor release which adds various new features, > improvements, bug fixes

Re: [ANNOUNCE] Jordan Birdsell joining the Kudu PMC

2016-11-07 Thread Brock Noland
Congratulations and thanks for your hard work!! On Monday, November 7, 2016, Todd Lipcon wrote: > Hi Kudu community, > > Today I'm very pleased to announce that the PMC has voted to add Jordan > Birdsell as a committer and PMC member on the Apache Kudu project! > > Jordan began contributing to K

Re: Internal daemon-to-daemon authorization

2016-11-01 Thread Brock Noland
This looks really straightforward IMO. I think as a dev if you are modifying the wire protocol, understanding this should be no sweat. On Mon, Oct 31, 2016 at 9:24 PM, Todd Lipcon wrote: > I whipped up a patch for something somewhat like option 3 here: > http://gerrit.cloudera.org:8080/4897 > >

Re: [VOTE] Apache Kudu 1.0.1 RC1

2016-10-10 Thread Brock Noland
+1 non-binding * Checked hashes and sig * Built from source * Ran tests, which passed On Fri, Oct 7, 2016 at 4:00 PM, Dan Burkert wrote: > Hi, > > We're happy to announce the first release candidate for Apache Kudu 1.0.1. > > This release includes bug fixes and documentation updates since the 1

Re: [ANNOUNCE] Two new Kudu committer/PMC members

2016-09-12 Thread Brock Noland
Congratulations!! On Mon, Sep 12, 2016 at 6:06 PM, David Alves wrote: > Congrats Alexey and Will!! > > On Mon, Sep 12, 2016 at 3:55 PM, Todd Lipcon wrote: > > > Hi Kudu community, > > > > It's my great pleasure to announce that the PMC has voted to add both > > Alexey Serbin and Will Berkeley a

Re: Kudu filesystem-access

2016-08-31 Thread Brock Noland
With regards to consistency, I would start with concepts and terms and then architecture: http://kudu.apache.org/docs/#_concepts_and_terms that will cover how Kudu ensures consistency using Raft. On Wed, Aug 31, 2016 at 1:46 AM, Maxim Smyatkin wrote: > Hello, the file IO implementation is in e

Re: Want to contribute

2016-08-02 Thread Brock Noland
Hi, Great to hear you are interested! :) There are many ways to contribute, covered here: http://kudu.apache.org/community.html#contributions If you have an engineering background, I can suggest my personal approach: 1. Get the build to work 2. Look through JIRA at minor/trivial changes to get s