Re: Action required - re-bootstrap your toolchain when you have a chance

Nice! On Fri, Sep 20, 2019 at 2:29 PM Tim Armstrong wrote: > https://gerrit.cloudera.org/#/c/14274/ just got merged. This switches to a > native-toolchain version which has the RUNPATH set correctly in the > binaries. This will allow solve some issues with LD_LIBRARY_PATH - most of > the hacks

Re: New Committer: Sahil Takiar

Congrats! On Wed, May 22, 2019 at 8:21 AM Fredy Wijaya wrote: > Congrats! > > On Wed, May 22, 2019 at 10:20 AM Joe McDonnell > wrote: > > > Congrats! > > > > On Wed, May 22, 2019 at 8:11 AM Laszlo Gaal > > wrote: > > > > > Congrats, Sahil! > > > > > > On Wed, May 22, 2019 at 4:56 PM David

Re: You'll need to fetch your Impala-lzo...

I think this one is even trickier! https://jenkins.impala.io/job/ubuntu-16.04-build-only/5395/ doesn't seem to clone Impala-lzo at all! And, though we're trying to do everything in a tempdir, the imapla_lzo dir is IMPALA_LZO = /home/ubuntu/tmp.CCVBRWuYra/../Impala-lzo My best guess

Re: You'll need to fetch your Impala-lzo...

retty=fuller > master > commit dccb1be88a5e237b06ae69cd99b048a38d9f024b (HEAD -> master) > Author: Philip Zeyliger > AuthorDate: Tue Jan 22 14:21:42 2019 -0800 > Commit: Philip Zeyliger > CommitDate: Fri Feb 1 11:04:06 2019 -0800 > > Adapt to new interface for AddDiskIoRange (IMPALA-7980)

Re: You'll need to fetch your Impala-lzo...

; have a look? > > Thanks, > Quanlong > > On Mon, Feb 11, 2019 at 1:32 PM Quanlong Huang > wrote: > > > Then branch-2.x needs this again: https://gerrit.cloudera.org/c/12339/. > > Could anyone have a look at this? I encountered a build error at > > https://

Welcome Paul Rogers as a Committer

The Project Management Committee (PMC) for Apache Impala has invited Paul Rogers to become a committer and we are pleased to announce that they have accepted. Congratulations and welcome, Paul! On behalf of the PMC, -- Philip

You'll need to fetch your Impala-lzo...

Hi folks, I just pushed https://gitbox.apache.org/repos/asf?p=impala.git;a=commit;h=a8e30506aafef14646d95a56fb87cf7c28d259d6 and https://github.com/cloudera/impala-lzo/commit/dccb1be88a5e237b06ae69cd99b048a38d9f024b to tackle IMPALA-7980. If you're working on master, and you have ../Impala-lzo

Re: Jenkins restart

When I last looked, the issue is that those tests use a Jenkins "pipeline." These have multiple steps (let's call them A, B, C) that run in serial. If A is running when you quiesce jenkins, B will get queued but never start, causing the overall job to hang forever.

Re: Runtime filter publishing from a join node to its cousin

(If folks are interested in a refresher, https://impala.apache.org/docs/build/html/topics/impala_runtime_filtering.html is useful.) I stared at that code for a bit, and I agree with you that it's plausible. I'm also confused by the "bottom-up" comment of generateFilters(): it seems like we walk

Re: Move forward branch-2.x

As for Quanlong's question, I think the answer is however the folks who want to do the work prefer to do it. As you noticed in the CDH changelists, Cloudera's distribution has opted for something more like approach (a), choosing to backport individual features. For a while, we were doing

Re: Does anyone use make_{asan,debug,impala,release}.sh?

+1 to getting rid of them. On Sun, Jan 27, 2019 at 6:49 PM Quanlong Huang wrote: > +1 for making the infra(bash/python scripts) simpler! It's hard for > beginners to make clear of their relationships and use them correctly. > > On Sat, Jan 26, 2019 at 9:45 AM Tim Armstrong > wrote: > > >

Re: Upcoming restart of jenkins.impala.io

Thanks for taking care of this! P On Wed, Jan 9, 2019 at 3:34 PM Pooja Nilangekar < pooja.nilange...@cloudera.com> wrote: > The update completed without any issues. I didn't have to kill any jobs > this time. Please let me know if you come across any issues while > starting/running jobs. > >

Re: New Impala PMC member - Zoltán Borók-Nagy

Congrats! On Sun, Jan 6, 2019 at 10:30 AM Andrew Sherman wrote: > Congratulations Zoltan! > > On Sat, Jan 5, 2019 at 8:49 AM Hubert Sun wrote: > > > Congrats Zoltan! > > > > On Fri, Jan 4, 2019 at 11:14 PM Gabor Kaszab > > wrote: > > > > > wow! congrats, Zoli! > > > > > > On Sat, Jan 5, 2019

Re: jenkins.impala.io DNS expired

Thanks, Jim! On Fri, Nov 16, 2018 at 1:57 PM Jim Apple wrote: > Fixed. > > On Thu, Nov 15, 2018 at 6:51 PM Jim Apple wrote: > > > Please use 35.164.73.121 in the meantime while we get this fixed. > > >

Re: UBSAN in pre-merge testing

ge from them. (Here, you're mutating "build type", and I'm proposing we also mutate "base OS" to get additional coverage.) -- Philip > > On Mon, Nov 12, 2018 at 1:01 PM Philip Zeyliger > wrote: > > > Seems useful to me. > > > > If you're intereste

Re: UBSAN in pre-merge testing

Seems useful to me. If you're interested, we could kill multiple birds with one stone. Specifically, I'm also interested in centos6/rh6 pre-merge testing. There are a variety of ways to do so, including running with test-with-docker stuff. I recognize it's more work, but happy to help if you want

Re: parallel-all-tests update

is is aligned with other test infra stuff I'm > working on. > > On Thu, Oct 11, 2018 at 7:34 PM Philip Zeyliger > wrote: > > > I'm working a little bit (in the background) on getting > > bin/bootstrap_system.sh to work. I'm somewhat optimistic that I can get &

Re: parallel-all-tests update

c tests > to address issues as they come up. > > Thanks, > Pooja > > > On Thu, Sep 27, 2018 at 2:43 PM Philip Zeyliger > wrote: > > > I think the approach to catch that is to just run the tests on the > relevant > > platform. (E.g., with test-with-docker

Re: parallel-all-tests update

, 2018 at 12:59 PM Tim Armstrong > wrote: > > > I also added it to the pre-review tests. Let me know if you see any > issues. > > > > On Thu, Sep 27, 2018 at 12:33 PM Philip Zeyliger > > wrote: > > > >> Hi folks, > >> > >> To address

parallel-all-tests update

Hi folks, To address IMPALA-6543, there's a new test in parallel-all-tests that makes sure that any Python scripts use Python2.6-compatible syntax. Note that this will catch the "try/catch/finally" style of bug, but not the "itertools.count(start=1)" kind of bug (python2.7 changed the signature

Re: Confluence access

I think I granted you access; try now! On Tue, Sep 18, 2018 at 3:04 PM Paul Rogers wrote: > Oh, Wiki user name is “paul-rogers” in case the e-mail is not sufficient. > > Thanks, > > - Paul > > > On Sep 18, 2018, at 3:03 PM, Paul Rogers wrote: > > > > Hi All, > > > > I’m a new Impala developer

Re: FE build failure

Using 'mvn -U' seems to have resolved the issue for Michael. Probably blowing away ~/.m2 would have as well. On Wed, Sep 5, 2018 at 1:33 PM Philip Zeyliger wrote: > > org.apache.hbase:hbase-procedure:jar:2.0.0-cdh6.x-SNAPSHOT > > What command are you trying to build with? > >

Re: FE build failure

ttp:jar:2.0.0-cdh6.x-SNAPSHOT > Found Banned Dependency: > org.apache.hbase:hbase-common:jar:tests:2.0.0-cdh6.x-SNAPSHOT > Use 'mvn dependency:tree' to locate the source of the banned dependencies. > [INFO] > > [INFO] BUIL

Re: FE build failure

Are you seeing this on your own machine? If so, try to add "-X" to the mvn execution and capture the (very large) log. I'd be happy to take a look. -- Philip On Wed, Sep 5, 2018 at 12:34 PM Michael Ho wrote: > Hi all, > > I tried a clean build this morning and kept running into the following >

Re: Adding profile info from Frontend

I'm certainly aware of tools that read TEventSequence and expect it to have certain structures. If we change the profiles significantly, we should insert a version sigil in there so that a client could at least figure out that they're looking at something new. A bigger modeling conversation is

Re: Impalad JVM OOM minutes after restart

Hi Brock, If you want to make Eclipse MAT more usable, set JAVA_TOOL_OPTIONS="-Xmx2g -XX:+HeapDumpOnOutOfMemoryError" and you should see the max heap at 2GB, thereby making Eclipse MAT friendlier. Folks have also been using http://www.jxray.com/. The query itself will also be interesting. If

Re: New Impala committer - Quanlong Huang

Congrats! On Fri, Aug 17, 2018 at 9:29 AM Tim Armstrong wrote: > The Project Management Committee (PMC) for Apache Impala has invited > Quanlong Huang to become a committer and we are pleased to announce that > they have accepted. Congratulations and welcome, Quanlong Huang! >

Re: hadoop.fs.Path impacts on Impala

Hi Barnabas, If I may suggest a way to approach this sort of question, I'd take a heapdump of an impalad and a catalogd (using "jmap") and then use Eclipse MAT or http://www.jxray.com/ to see if we're using Path. You'll want to load some tables and partitions ahead of time. Based on a little

Re: Impala Incident Sharing

Hi Quanlong, Thank you for the incident note! You might be interested in https://gerrit.cloudera.org/#/c/10998/ which is adding some instrumentation to make it easier to notice with monitoring tools that we're running out of memory or having large GC pauses. -- Philip On Tue, Jul 31, 2018 at

Re: impalad running as superuser in tests

Hi Todd, You're right: the current minicluster setup makes it impossible to test some cases. I think your approach of telling Hadoop a different user is sensible, though might be a rabbit hole in terms of getting Hive and HBase and everything happy. I know we are able to run some tests against

Re: Removing IMPALA_MINICLUSTER_PROFILE=2 from master

I'm +1 on removing it. On Wed, Jul 11, 2018 at 9:39 AM Sailesh Mukil wrote: > +1 for removing it. > > I'm all for reduced complexity if not a lot of users are benefitting from > it. > > On Wed, Jul 11, 2018 at 9:29 AM, Fredy Wijaya > > wrote: > > > Hi all, > > > > In the master branch, we

Re: Jenkins scripts in repo?

If it's helpful, I'd be happy to send you, off-list, the XML configuration file (which is Jenkins' serialized format) and/or screenshots of any of our jobs. It's a little bit of work because I have to make sure they're devoid of passwords and such. Thanks! -- Philip On Wed, Jul 11, 2018 at 8:16

Re: Impala OS and Java version support

bin/boostrap_development already only works for Ubuntu 16.04+ because it's painful to get Java8 via apt-get on Ubuntu 14. The "profile=3" configuration in master already requires Java 8 at runtime, but will still compile with "java 7 source". Are you proposing to change

Re: Re: Branch 2.x

Hi Quanlong, If someone wishes to step up and maintain the 2.x branch, they're very welcome to. To be transparent, some of the Cloudera employees are focusing considerably more on the 3.x line and aren't currently planning to release manage additional 2.x releases. On Wed, Jun 20, 2018 at 1:56

Re: Future of unsupported formats?

I'm supportive of removing them. -- Philip On Tue, Jun 19, 2018 at 10:06 AM Tim Armstrong wrote: > Hi Edward, > I was talking about write support, specifically. Reading those formats is > supported without any configuration changes. > > - Tim > > On Tue, Jun 19, 2018 at 9:32 AM, Edward

Re: Branch 2.x

I've not heard anything, so I've removed the "trigger" for job https://jenkins.impala.io/job/cherrypick-2.x-and-test/. It used to "Poll SCM" at an "@hourly" rate, looking for changes in asf/master. Thanks! -- Philip On Fri, Jun 15, 2018 at 11:23 AM Phili

Branch 2.x

Hi folks, As you know, many of us have been maintaining the 2.x branch by having a cherry-pick job (https://jenkins.impala.io/job/cherrypick-2.x-and-test/) and, when it fails, manually pushing through the issues. This has proven to be quite the burden, and I'm planning on disabling the automatic

Configuring Impala to exit on OutOfMemoryError

Hi! Seeing bugs like IMPALA-7168, it leads me to think that we should recommend folks who are running Impala to use -XX:OnOutOfMemoryError="kill -9 %p" or equivalent on their JVMs, to simply crash the process on frontend OOM. Any thoughts on whether this is the right approach? -- Philip

Re: Breaking changes after 3.0, versioning, IMPALA-3307

; > > > > Short > > > > > > > major versions, as both Clang and Firefox have done so. > > > > > > > > > > > > > > I also feel that, both from a semver perspective and as a user > of > > > > other > > > >

Re: Automatically rebase changes before GVO?

Seems fine, especially since we do the rebase as our submission strategy anyway, so we're already accepting/testing something that's likely to get rebased, and we may as well minimize that window. I'd be in favor of the bot also carrying the votes. On Thu, Jun 7, 2018 at 1:24 PM, Tim Armstrong

Re: Breaking changes after 3.0, versioning, IMPALA-3307

Hi Csaba! I would be fine with both proposals, with a slight preference to B. My understanding is that you're going to expose a way to define overrides for time zone definitions, so there will be pretty workable workarounds too. -- Philip On Mon, Jun 4, 2018 at 1:45 PM, Csaba Ringhofer wrote:

Re: jenkins.impala.io's ubuntu-16.04-from-scratch will now have Junit test results

char.xml.[failed-to-read] ><https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/ > 2186/testReport/junit/impala_char/xml/_failed_to_read_/> >- impala_comments.xml.[failed-to-read] ><https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/ > 2186/testReport/junit/impala_co

New message on your code reviews when cherry-picking your change fails.

m> Gerrit-Reviewer: Impala Public Jenkins <impala-public-jenk...@cloudera.com> Gerrit-Reviewer: Michael Brown <mi...@cloudera.com> Gerrit-Reviewer: Philip Zeyliger <phi...@cloudera.com> Gerrit-Comment-Date: Fri, 11 May 2018 18:58:13 + Gerrit-HasComments: No -- You received this m

Re: [VOTE] 3.0.0 release candidate 1

+1 (Binding) I checked the hashes and the GPG signatures. Checked the tree hash. Diffed the tarball with the git RC tag. I also ran tests via docker/test-with-docker successfully. -- Philip On Tue, May 1, 2018 at 4:33 PM, Sailesh Mukil wrote: > This is a vote to

new mailing list: impala-issues-all@

Hey folks, With the help of the Apache INFRA team (INFRA-16440), there's a new mailing list called impala-issues-all. It gets all JIRA notifications, not just JIRA creations and their closures. If you're interested, subscribe by e-mailing issues-all-subscr...@impala.apache.org . Thanks! --

Re: Unsupported major.minor version 52.0

Hi Jim, Are you using JDK7? Hadoop3 supports only JDK8+. -- Philip On Thu, Apr 26, 2018 at 9:35 AM, Jim Apple wrote: > testdata/bin/run-all.sh fails for me with the following error > > Exception in thread "main" java.lang.UnsupportedClassVersionError: >

Re: Bulk Cherry-Pick FGP Commits to 2.x Branch

Yep. Sounds good to me. On Wed, Apr 25, 2018 at 1:13 PM, Bharath Vissapragada wrote: > FGP = "Fine-grained privileges" or something else? > > On Wed, Apr 25, 2018 at 1:09 PM, Fredy Wijaya > wrote: > > > Hi, > > > > Just to give a heads-up, I'll do

Re: Minicluster MR "your endpoint configuration is wrong" error

MWebServices to > GuiceManagedComponentProvider with the scope "PerRequest" > log4j:WARN No appenders could be found for logger > (org.apache.hadoop.mapreduce.v2.app.MRAppMaster). > log4j:WARN Please initialize the log4j system properly. > log4j:WARN See http://logging.apach

Re: New PMC member: Philip Zeyliger

Thanks! On Mon, Apr 23, 2018 at 1:03 PM, Jim Apple <jbap...@cloudera.com> wrote: > The Project Management Committee (PMC) for Apache Impala has invited Philip > Zeyliger to become a PMC member and we are pleased to announce that they > have accepted. > > Congratulations and welcome, Philip! >

Re: Minicluster MR "your endpoint configuration is wrong" error

ip commit 6dc13d933b5ea9a41e584d83e95db72b9e8e19b3 Author: Philip Zeyliger <phi...@cloudera.com> Date: Tue Apr 10 09:21:20 2018 -0700 Remove Yarn from minicluster by default. (2nd try) On Wed, Apr 18, 2018 at 6:25 PM, Tianyi Wang <tw...@cloudera.com> wrote: > I was trying to run tests/com

Re: Maintenance for jenkins.impala.io today

I think https://jenkins.impala.io/job/clang-tidy-ub1604/1330/ has gotten farther than previously, so perhaps upgrading that plugin was sufficient. Please continue to let me know if you see anything else awry! -- Philip On Wed, Apr 11, 2018 at 2:00 PM, Philip Zeyliger <phi...@cloudera.com>

Re: Maintenance for jenkins.impala.io today

, -- Philip On Wed, Apr 11, 2018 at 1:57 PM, Philip Zeyliger <phi...@cloudera.com> wrote: > Yes, so it seems. I'll look into it. > > -- Philip > > On Wed, Apr 11, 2018 at 1:49 PM, Tim Armstrong <tarmstr...@cloudera.com> > wrote: > >> Is it possible that the upgr

Re: Maintenance for jenkins.impala.io today

ava:193)*17:38:46* Caused: > java.io.IOException*17:38:46* at > hudson.XmlFile.write(XmlFile.java:200) > > > > On Wed, Apr 11, 2018 at 12:42 PM, Lars Volker <l...@cloudera.com> wrote: > > > Thank you for doing the maintenance work, Phil! > > > > On Wed, A

Re: [DISCUSS] Apache Impala 2.12.0 and 3.0 releases

Sounds like a good plan to me! -- Philip

Re: Re: Updating your minicluster to Hadoop 3.0...

9:32 PM, Dimitris Tsirogiannis < > >dtsirogian...@cloudera.com> wrote: > > > >> Good point. I used -format that in theory handles both the metastore and > >> the sentry policy dB. The sentry_policy db is created and has some tables > >> but not

Re: Updating your minicluster to Hadoop 3.0...

;> > >> ./buildall.sh -notests -format_metastore -format_sentry_policy_db > >> > >> > >> On Thu, Mar 29, 2018 at 6:15 PM, Dimitris Tsirogiannis < > >> dtsirogian...@cloudera.com> wrote: > >> > >> > I tried rebuilding my min

Re: [jira] [Created] (IMPALA-6767) java.lang.NoSuchMethodError: org.apache.sentry.provider.db.service.thrift.SentryPolicyServiceClient.listAllRoles(Ljava/lang/String;)Ljava/util/Set;

This is a method that changed names between the Hadoop2 and Hadoop3 profiles, and we have a shim in a compat directory in the fe/src. It’s likely you need to rebuild or are talking to the wrong version. P On Thu, Mar 29, 2018 at 12:13 PM Michael Ho (JIRA) wrote: > Michael Ho

Re: accidental push to master

If I had to guess, https://jenkins.impala.io/job/cherrypick-2.x-and-test/ will skip the revert, because it doesn't have a Change-Id. Since it hasn't happened, you can add 25218487533f6bf6959c32ff4ee38b77e0ab30b5 to the ignored commits list of 2.x (in branch 2.x) right now, and both commits will

Re: FE build failure

https://gerrit.cloudera.org/#/c/9841/ is the review to remove "-noclean" from bootstrap_development, which I think will prevent this. -- Philip On Wed, Mar 28, 2018 at 9:58 AM, Philip Zeyliger <phi...@cloudera.com> wrote: > Hi Michael, > > What's going on is that we'r

Re: FE build failure

are unblocked. -- Philip On Wed, Mar 28, 2018 at 9:37 AM, Michael Ho <k...@cloudera.com> wrote: > https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/1748/ > > On Wed, Mar 28, 2018 at 9:34 AM, Philip Zeyliger <phi...@cloudera.com> > wrote: > > > I see.

Re: FE build failure

ome previous GVO ? > > On Wed, Mar 28, 2018 at 9:05 AM, Philip Zeyliger <phi...@cloudera.com> > wrote: > > > Hi Michael, > > > > Most likely this is on account of switching to Hadoop 3 by default ( > > https://github.com/apache/impala/commit/0812f8737a4301e5b5

Re: FE build failure

Hi Michael, Most likely this is on account of switching to Hadoop 3 by default ( https://github.com/apache/impala/commit/0812f8737a4301e5b52cad9dc911589f9e98ecdb). I sent an e-mail out about this yesterday, but I think what you're seeing is a need to re-run buildall, and to possibly clean

Updating your minicluster to Hadoop 3.0...

Hi folks, I just sent off https://gerrit.cloudera.org/#/c/9743/ and https://issues.apache.org/jira/browse/IMPALA-4277 for GVD, which changes the default minicluster to be based on Hadoop 3.0, Hive 2.1, Sentry 2.0, and so on. This change *will not* be back-ported to 2.x. When you pull that change

test_semi_joins_exhaustive error?

Hi folks, I'm curious if the following error looks familiar to folks. I'm running exhaustive tests on a 32 GB machine with a slightly lowered impalad memlimit and am pretty much up to date (commit 623ace0e4c84297606d13f321bd2ceee70a8b9f2 plus the memlimit change). Thanks! -- Philip

Re: Setting up ASF Git Bot?

d posting on JIRAs. E.g. > I had to copy and paste the commit message manually on this one: > https://issues.apache.org/jira/browse/IMPALA-6497 > > On Thu, Feb 1, 2018 at 10:17 AM, Philip Zeyliger <phi...@cloudera.com> > wrote: > > > I filed https://issues.apache.org/jir

Re: IMPALA-3343: impala-shell compatibility with Python 3

I'm not aware of anyone having tried it, so I don't think we know. I'd also check in on Thrift's support for Python3. That seems like the most likely library. You can certainly give removing print a shot! -- Philip On Wed, Feb 14, 2018 at 11:50 AM, Diggs, Asoka wrote: >

Re: TEST_START_CLUSTER_ARGS are not applied in custom cluster tests

It's definitely handy. I've used it for specifying things like --mem_limit when running inside a container. I think Lars' question is more about what the custom cluster tests should do with it. -- Philip On Tue, Feb 13, 2018 at 10:48 AM, Matthew Jacobs wrote: > I had

Re: Setting up ASF Git Bot?

Dan > > On Thu, Feb 1, 2018 at 9:30 AM, Jim Apple <jbap...@cloudera.com> wrote: > > > Nice. Thanks for digging in! > > > > On Thu, Feb 1, 2018 at 8:56 AM, Philip Zeyliger <phi...@cloudera.com> > > wrote: > > > I see similar messages against git

Setting up ASF Git Bot?

Hi folks, Would people be interested in ASF's bot that connects JIRAs to Commits? You can see the "activity stream" of https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jira-bot for an example, and there's a sample below for convenience. Hopefully it will make it more obvious that we

Re: Impala 3.x (and 2.x)

> >> We can at least start off with this policy and then change it if it is > not > >> working well for some reason. > >> > >> On Fri, Jan 19, 2018 at 1:59 PM, Philip Zeyliger <phi...@cloudera.com> > >> wrote: > >> > >&

Re: Impala 3.x (and 2.x)

not > > working well for some reason. > > > > On Fri, Jan 19, 2018 at 1:59 PM, Philip Zeyliger <phi...@cloudera.com> > > wrote: > > > > > An update here! > > > > > > I'm pretty close to pushing the first master-only change (the ver

Re: Impala 3.x (and 2.x)

. Thanks! -- Philip On Wed, Jan 17, 2018 at 9:57 AM, Philip Zeyliger <phi...@cloudera.com> wrote: > It sounds like we've reached consensus, so I'm starting to maneuver this > along. Please don't hesitate if you've got concerns. You can follow along > at https://issues.apache.

Re: Impala 3.x (and 2.x)

Hi folks! It sounds like there haven't been objections to having master be "3.0" and introducing a 2.x branch. Would folks be alright if I started making changes in that direction? Thanks! -- Philip On Fri, Jan 12, 2018 at 4:10 PM, Philip Zeyliger <phi...@cloudera.com> wrot

Re: Impala 3.x (and 2.x)

have the cherrypick tool between gerrit/master and gerrit/2.x do the cherrypicks and run the tests on Jenkins. Do you think that's preferable? -- Philip > > On Fri, Jan 12, 2018 at 3:57 PM, Philip Zeyliger <phi...@cloudera.com> > wrote: > > Picture: > > https://gi

Re: Impala 3.x (and 2.x)

Hi! > Should we start tagging all candidates with a common label, e.g. include-in-v3? I agree with Lars's suggestion for tagging JIRAs with include-in-v3. I've done so, and the relevant query is https://issues.apache.org/jira/issues/?jql=labels%20%3D%20include-in-v3%20and%20project%3Dimpala . >

Impala 3.x (and 2.x)

Hi folks, I'd like to start the conversation around 3.0, spurred in part by some compatibility-challenging issues. I'm leading with a somewhat concrete proposal, but that's meant to start the discussion! Impala's master branch currently self-identifies as version 2.11. (See

Re: Philip Zeyliger is now an Impala committer

Thanks! -- Philip On Tue, Jan 9, 2018 at 12:51 PM, Alexander Behm wrote: > The Project Management Committee (PMC) for Apache Impala has invited Philip > to become a committer and we are pleased to announce that they have > accepted. > > Congratulations and welcome,

Re: Tianyi Wang is now an Impala committer

Congrats! On Fri, Jan 5, 2018 at 1:47 PM, Jim Apple wrote: > The Project Management Committee (PMC) for Apache Impala has invited > Tianyi Wang to become a committer and we are pleased to announce that > they have accepted. > > Congratulations and welcome, Tianyi! >

Re: thrift-server-test

gt; On Tue, Dec 12, 2017 at 3:25 PM, Philip Zeyliger <phi...@cloudera.com> > wrote: > > > Hi folks, > > > > I've been running into issues with thrift-server-test and Kerberos. Below > > is an excerpt of "KRB5_TRACE=/dev/stderr > > be/build/debug/rpc/thri

thrift-server-test

Hi folks, I've been running into issues with thrift-server-test and Kerberos. Below is an excerpt of "KRB5_TRACE=/dev/stderr be/build/debug/rpc/thrift-server-test"; both SslConnectivity/1 and SslConnectivity/2 fail the same way. I'm running Ubuntu16.04. I've seen this both on my host, as well as

Re: Switch gerrit merge strategy to "rebase always"?

Seems like it's the right thing to do. On Mon, Dec 11, 2017 at 11:43 AM, Tim Armstrong wrote: > We recently had a bad merge that was allowed by the cherry-pick merge > strategy merging a simple without its ancestor (since they didn't change > any nearby lines): >

Upgrading Jenkins

I'll be upgrading Jenkins today in response to a security advisory. I'll be putting it in "no new jobs" mode shortly. -- Philip

Re: A test failure at Jenkins build is not reproducible on my local

> > > Regarding guidance of E2E tests in "How to load and run Impala tests > to+load+and+run+Impala+tests>" > wiki page, I wish there are more detailed information. Let me put the > information on the wiki after you answer my question: