Re: [VOTE] Bylaws change: remove incubation reference

+1 (binding) On Nov 20, 2017 10:42, "Alexander Behm" wrote: > +1 (binding) > > On Mon, Nov 20, 2017 at 8:16 AM, Michael Brown wrote: > > > +1 (binding) > > > > On Sat, Nov 18, 2017 at 11:00 AM, Jim Apple > wrote: > > > > > Please vote on this minor bylaws change to remove the incubation link >

Re: Impala minidump dump_breakpad_symbols

Can you post the output of dump_breakpad_symbols.py and stderr of minidump_stackwalk? Cheers, Lars On Mon, Nov 27, 2017 at 10:24 PM, [email protected] < [email protected]> wrote: > > > On 2017-11-28 10:03, Sailesh Mukil wrote: > > Hi Sandish, > > > > Have you tried the steps outlined he

Re: Impala minidump dump_breakpad_symbols

ywhere, can you please describe step-by-step what you did? Cheers, Lars On Nov 27, 2017 22:44, "[email protected]" wrote: > > > On 2017-11-28 12:01, Lars Volker wrote: > > Can you post the output of dump_breakpad_symbols.py and stderr of > > minidump_stackwal

Re: Impala minidump dump_breakpad_symbols

The resolved minidump looks truncated, as does the output of minidump stackwalk. This could indicate that the minidump got corrupted. How did you generate the minidump? On Nov 28, 2017 02:20, "[email protected]" wrote: > > Thank you, Lars Volker, for quick response's &

Re: Impala minidump dump_breakpad_symbols

2017 11:36 PM, "[email protected]" > wrote: > > > > > > > On 2017-11-28 21:01, Lars Volker wrote: > > > The resolved minidump looks truncated, as does the output of minidump > > > stackwalk. This could indicate that the minidump got corrupted.

Re: Impala minidump dump_breakpad_symbols

o not match. > > > > > > > > > > > > > > You can turn the md into a core to see the original binary > > version > > > > that > > > > > > > generated it: > > > > > > > > > > > > > > /bin/minidum

Re: [DISCUSS] 2.11.0 release

+1 Thank you for stepping up, Thomas! It'll be great to have a new release so close after our graduation. On Thu, Nov 30, 2017 at 1:32 PM, Taras Bobrovytsky wrote: > +1 > > I agree. This is a good time to release. Thanks for volunteering! > > On Thu, Nov 30, 2017 at 1:22 PM, Sailesh Mukil > wr

Re: Github

Yes, you'll have to drop the "incubator-" part of your git remotes. You can use "git remote set-url " to do that. Cheers, Lars On Tue, Dec 19, 2017 at 8:25 AM, kenneth mcfarland < [email protected]> wrote: > This is probably a dumb question but is there a new repository or do I need >

Re: [VOTE] 2.11.0 release candidate 1

+1 (binding) Here's what I did: * Read the instructions on the wiki and fixed the link to the KEYs file * Downloaded all files from the RC1 download link * Manually verified md5, sha512 sum, and asc signature * Verified git hashes * Verified tarball contents * Ran ./buildall.sh -skiptests -notest

Re: IMPALA-5440 Request for assignment

Hi Xinran, I added you to the Contributors group and assigned the Jira to you. Thank you for working on Impala. Cheers, Lars On Sun, Jan 7, 2018 at 3:48 AM, Xinran Yu Tinney wrote: > Hi, Impala dev community, >I was wondering if I could get assigned for IMPALA-5440 >

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

Thank you for starting the discussion. It would be great to have a branch to start including non-compatible changes. I would like to propose adding two Jiras that switch default options / behaviors * IMPALA-5037 (Change default Parquet array reso

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

+1 On Tue, Jan 16, 2018 at 1:29 PM, Philip Zeyliger wrote: > 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,

Re: [ANNOUNCE] Apache Impala 2.11.0 release

Done: https://twitter.com/ApacheImpala/status/954061402070704129 On Thu, Jan 18, 2018 at 10:31 AM, Thomas Tauber-Marshall < [email protected]> wrote: > -everyone but dev@ > > Could someone with access to the Impala Twitter account (according to Henry > that should be anyone on the PMC) annou

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

https://git-wip-us.apache.org/repos/asf/impala.git > > >> > > * [new branch] asf-gerrit/2.x -> 2.x > > >> > > > > >> > > # Double-check: > > >> > > $git-ls-remote apache | grep 2.x; git-ls-remote asf-gerrit | grep > > 2.x > > >

Re: Write access to Wiki

Done, thank you for contributing! On Wed, Jan 24, 2018 at 3:15 PM, Adam Holley wrote: > My user id is holleyism. Would someone please grant me write access? > > Thank you. > > Adam. > > -- > > Adam Holley > > Cloudera Software Engineer > > [email protected] > > 515 Congress Ave, Suite 1212 >

Re: Freezing jenkins.impala.io Wed 2018-02-07 (today) at 6pm PST

Thank you for applying these updates, Alex! On Feb 7, 2018 22:57, "Alexander Behm" wrote: Jenkins and a few plugins were updated. The service is back now at jenkins.impala.io Warning: I updated the "Pipeline: Supporting APIs" plugin to version 2.16 due to a severe security vulnerability. The ne

TEST_START_CLUSTER_ARGS are not applied in custom cluster tests

Hi All, Mike noticed in a review that TEST_START_CLUSTER_ARGS are not applied in custom cluster tests and we wondered whether that is on purpose or a bug. Can someone with historic knowledge shed some light on it? The relevant code is here: https://github.com/apache/impala/blob/5f7599687748b1e1ce

Re: Jenkins.impala.io back up

Thank you for applying the updates, Zach! On Wed, Feb 14, 2018 at 11:17 AM, Zachary Amsden wrote: > Everything went as planned and Jenkins is now upgraded. > > - Zach >

Re: Inconsistent float/double sort order in spec and implementations can lead to incorrect results

I think one idea behind the column order fields was that if a reader does not recognize a value there, it needs to ignore the stats. If I remember correctly, that was intended to allow us to add new orderings for collations, but it also seems useful to address gaps in the spec or known broken reade

Re: Inconsistent float/double sort order in spec and implementations can lead to incorrect results

t; just define a special order for floats? Essentially it would be a tag for > writers to say "hey I know about this total order thing". > > On Fri, Feb 16, 2018 at 9:14 AM, Lars Volker wrote: > > > I think one idea behind the column order fields was that if a reader do

Re: TEST_START_CLUSTER_ARGS are not applied in custom cluster tests

gt;> This will enable jenkins jobs to specify custom arguments when > >> starting the mini cluster (via start-impala-cluster.py). This > >> will be used to create a jenkins job that runs tests with RM > >> enabled. > >> > >> Change-Id: I96a2e8d90db448581bbf448f3d

jenkins.impala.io going down for security updates

I'll restart our Jenkins server momentarily to install security updates. No jobs are currently running. I will reply to this email when the update is complete. Cheers, Lars

Re: jenkins.impala.io going down for security updates

The update was successful and Jenkins is back online. Please reach out to me if you encounter any problems. Cheers, Lars On Mon, Feb 26, 2018 at 10:20 AM, Lars Volker wrote: > I'll restart our Jenkins server momentarily to install security updates. > No jobs are currently running. I

Re: Please hold off on merging changes that don't fix builds

Our builds are still in a bad shape, in particular all downstream exhaustive builds are currently failing. Tim will push a change to revert IMPALA-4835 to address some of the issue. Please hold off on any commits that don't address current build issues until our builds are reliably green. Thanks,

Re: Please hold off on merging changes that don't fix builds

A bunch of fixes made it into master and the builds look better. If you are working on a broken-build issue, please keep looking into it. Thank you all for the help. Let's open the branch for commits again. Cheers, Lars On Fri, Mar 2, 2018 at 3:55 PM, Lars Volker wrote: > Our builds a

Re: Alexandra Rodoni is now an Impala committer

Congratulations Alex! On Tue, Apr 10, 2018, 12:50 John Russell wrote: > The Project Management Committee (PMC) for Apache Impala has invited > Alexandra to become a committer and we are pleased to announce that they > have accepted. > > Congratulations and welcome, Alexandra!

Re: Maintenance for jenkins.impala.io today

Thank you for doing the maintenance work, Phil! On Wed, Apr 11, 2018 at 9:52 AM, Philip Zeyliger wrote: > This is completed. There were only two patches being built, so I killed > those builds. > > I restarted GVO for change 9976 ("Move some test_spilling debug actions to > exhaustive"). > > I *

Re: Maintenance for jenkins.impala.io today

Thank you for doing the maintenance work, Vuk! On Mon, Apr 16, 2018 at 11:03 AM, Vuk Ercegovac wrote: > Maintenance done. > > On Mon, Apr 16, 2018 at 10:00 AM, Vuk Ercegovac > wrote: > > > Hi, > > > > Several plugins to be dealt with to address a security advisory. I plan > on > > doing this to

Re: Adding to Apache JIRA as contributor

Done. On Thu, Apr 19, 2018 at 6:00 PM, Adrian Ng wrote: > Hi, > > Can someone please add me as a contributor on Apache JIRA for Impala? > > Thanks, > Adrian >

Re: [VOTE] 2.12.0 release candidate 1

+1 (binding) * Validated that the sha512 file has been fixed * Validated the GPG signature * Ran the release test job on jenkins.impala.io, result is here * Unpacked and compiled the tarball on my development machine, made sure th

Re: Unsupported major.minor version 52.0

This has bitten me before, too. I pushed a change to issue an additional warning if the minicluster fails to start and the environment points to Java 7 and Hadoop 3: https://gerrit.cloudera.org/#/c/10222/ Most people will have seen it by now, but maybe it's not too late to safe someone else from t

Re: [VOTE] 3.0.0 release candidate 1

+1 (binding) * Downloaded the files and validated the sha512 signature and GPG checksum * Built Impala from the tarball on the machine under my desk * Started impala, ran some queries * Observed that the shell reports a valid git hash in its version: Server version: impalad version 3.0.0-RELEASE D

Re: 2.x branch divergence, its implications and what you can do.

Should we add a check to the master GVO that makes sure that a change either applies to 2.x, or has a "not for 2.x" label? On Thu, May 3, 2018 at 12:12 PM, Sailesh Mukil wrote: > It's been a while since we started maintaining 2 active branches, master > and 2.x, and the divergence between them h

Re: Maintaining Impala Documentation Sets for Releases

I'm in favor of #3, too. Ideally we'd have proper pages for both releases, including docs, and downloads. On Mon, May 7, 2018 at 4:14 PM, Jim Apple wrote: > I'd advocate #3, at least until we are no longer regularly making new 2.x > releases. > > On Mon, May 7, 2018 at 3:06 PM, Alexandra Rodoni

New Committer: Csaba Ringhofer

The Project Management Committee (PMC) for Apache Impala has invited Csaba Ringhofer to become a committer and we are pleased to announce that he has accepted. Congratulations and welcome, Csaba!

Re: Broken/Flaky Tests

Hi Thomas, Can you give an update on where we are with the builds? We currently have ~15 changes with a +2: https://gerrit.cloudera.org/#/q/status:open+project:Impala-ASF+branch:master+label:Code-Review%253D2 Thanks, Lars On Fri, May 25, 2018 at 5:20 PM, Henry Robinson wrote: > +1 - thanks fo

Re: Automatically rebase changes before GVO?

This is great, I'm in favor of automatic rebasing. It's be nice to have a flag that turns it off though, since rebases sometimes can clutter a review with many patch sets. On Mon, Jun 11, 2018 at 12:06 PM, Tim Armstrong wrote: > > On nit: as GVD gets more complex, it becomes harder for new peopl

Re: Automatically rebase changes before GVO?

It seems that Jenkins now posted the "Build started" message twice. I removed one of them from the config. Tim, can you verify that I removed the right one? https://jenkins.impala.io/job/gerrit-verify-dryrun/jobConfigHistory/showDiffFiles?timestamp1=2018-06-11_22-09-04×tamp2=2018-06-12_02-47-10 O

Maximum number of concurrent jobs for gerrit-verify-dryrun-external

Hi All, It seems that we intend to have two parallel jobs at most: - Maximum Total Concurrent Builds: 2 - Maximum Concurrent Builds Per Node: 1 However, all jobs run on master and then spawn subsequent jobs on worker nodes. This limits the maximum number of concurrent jobs to 1. If no-one

Re: Maximum number of concurrent jobs for gerrit-verify-dryrun-external

I made this change. On Mon, Jun 11, 2018 at 9:57 PM, Jim Apple wrote: > Lgtm > > On Mon, Jun 11, 2018 at 7:58 PM Lars Volker wrote: > > > Hi All, > > > > It seems that we intend to have two parallel jobs at most: > > > >- Maximum Total Concur

Re: Future of unsupported formats?

I'm in favor of removing unsupported code, especially when doing so makes development of the rest of the codebase easier and saves us cycles for maintaining it. On the other hand it would suck if users had come to rely on it and we break it, even though we recommend against it. We could make a rea

Re: Future of unsupported formats?

would process all the above formats. > > Edward > > On Tue, Jun 19, 2018 at 11:59 AM, Lars Volker > wrote: > > > I'm in favor of removing unsupported code, especially when doing so makes > > development of the rest of the codebase easier and saves us cycles for > &

Re: Future of unsupported formats?

AVRO + Impala but since > >> switched off. > >> > >> I also do not understand what is meant by "behind a query option" since > >> the > >> version of Impala I had (CDH 5+6) would process all the above formats. > >> > >> Edward

Re: Need reviewer for SHUTDOWN patch

I hope to have a look at it today. On Mon, Jul 2, 2018 at 9:29 AM Tim Armstrong wrote: > Does anyone have time to review this patch? It's a pretty big step towards > being able to shrink an Impala cluster without disrupting workloads. > > https://gerrit.cloudera.org/#/c/10744/ >

Impala OS and Java version support

Hi All, With the automatic commit flow to the 2.x branch being disabled, I'd like to suggest that we deprecate support for some older operating systems on the 3.x branch. This would allow us to get rid of almost all the checks in common/config.h.in as well as some workarounds in the code. It would

Re: Impala OS and Java version support

port much older OSes especially since it's becoming > > much more burdensome to special case code for them and have those paths > > tested. > > > > I'll defer to others on the minimum Java version proposal since they may > > have better insight. > > &

IMPORTANT: you will need to re-download orc

tldr; you have to run "rm -rf $IMPALA_TOOLCHAIN/orc-*" This change has just been submitted: https://gerrit.cloudera.org/#/c/10755/ It updates protobuf to version 3 and adds libunwind in preparation for rebasing our KRPC code and to enable porting of more RPCs to KRPC. The new toolchain build has

Re: Impala OS and Java version support

gt; https://github.com/apache/impala/search?q=debian > > On Fri, Jul 6, 2018 at 9:19 AM, Lars Volker > wrote: > > > Hi All, > > > > With the automatic commit flow to the 2.x branch being disabled, I'd like > > to suggest that we deprecate support for some older o

Re: Re: Impala OS and Java version support

enkins.impala.io since I can't login. > > At 2018-07-10 02:34:44, "Lars Volker" wrote: > >Several developers seem to use Ubuntu for their development which makes me > >think that Impala would work on Debian, too. However, I think we should > not > >claim pro

Re: Improving Kudu Build Support

I'm in favor of not spending developer time and effort to maintain compatibility with 14.04. Personally I'm still developing on Ubuntu 14.04 so I'd be happy if we can support it without much pain. On the other hand it EOLs in April 2019, so I might as well go to 18.04 now, should we decide to drop

Re: Breaking change for query hints?

The warning seems to come from SelectList.java:87 which also was in 2.5 (SelectList.java:85

Re: Breaking change for query hints?

We changed query hints from being interpreted as strings to being parsed properly in commit ce9b332e for IMPALA-4163 . Be

Re: Breaking change for query hints?

; > +} else { > > + sb.append(name_); > >sb.append("("); > >sb.append(Joiner.on(",").join(args_)); > >sb.append(")"); > > > > Quanlong Huang 于2018年8月24日周五 下午12:09写道： > >> Unfortunately, the queries

Re: help on permissions on Impala jiras

Hi Yongjun, I added you to the Contributor role in the Jira project. You should be able to assign issues to yourself now. Cheers, Las On Fri, Aug 24, 2018 at 4:14 PM Yongjun Zhang wrote: > Hi, > > May I get help on getting permissions on Impala jiras? > > My apache jira user id is yzhangal > >

Re: Wrong Jira id in commit (IMPALA-7147 vs IMPALA-7417)

+1, thanks for fixing it. On Mon, Sep 3, 2018, 12:16 Brock Noland wrote: > I would do this, it's quite courteous for future devs. > > "Our current idea is to change IMPALA-7417 > to be a duplicate of IMPALA-7147, and create a new Jira with IMPALA-7417's > original contents." > > On Mon, Sep 3, 2

Re: [VOTE] Removing emeritus and activity requirements

+1 (binding) On Sun, Sep 9, 2018, 18:36 Brock Noland wrote: > +1 > > On Sun, Sep 9, 2018 at 8:15 PM, Jim Apple wrote: > > > Please vote on the following diff to the bylaws: > > > > https://gerrit.cloudera.org/#/c/11407/ > > > > The vote will conclude Thursday morning, California time. Only PMC

Re: JSON support: Hive compatibility or ANSI SQL standard

Thanks for the comprehensive summary, Quanlong. I'm in favor of (c) but I don't feel strongly about the order in which we should prioritize them. Being compatible to Hive and following the SQL standard will help users to switch more easily between systems. I'm not worried about the confusing users

Re: The search capability on the Impala documentation site

We could add a search box that links to an external search engine, e.g. like so: https://duckduckgo.com/?q=site%3Aimpala.apache.org+inurl%3Adocs+random+replica&ia=web Would this help? I don't know much about our dita doc generator, there might be much easier ways that I'm not aware of. Cheers, La

Re: Restart jenkins.impala.io

Thank you for taking care of this, Pooja! On Wed, Oct 10, 2018 at 12:24 PM Pooja Nilangekar < [email protected]> wrote: > Done. > > Thanks, > Pooja > > > On Wed, Oct 10, 2018 at 9:56 AM Pooja Nilangekar < > [email protected]> wrote: > > > Hi, > > > > I'm going to restart J

Gerrit Maintenance tonight at 8pm Pacific

Hi All, Cloudera runs the Gerrit instance at gerrit.cloudera.org, which we for our code reviews. Tonight (10/17) at 8pm Pacific time (10/18 3am UTC), their IT team will be upgrading Gerrit from version 2.14.6 to 2.14.15. Details on 2.14.15 can be found here: https://www.gerritcodereview.com/2.14.

Re: New committer: Zoram Thanga

Congratulations Zoram! On Fri, Nov 16, 2018 at 1:23 PM Andrew Sherman wrote: > Congrats! > > On Fri, Nov 16, 2018 at 1:21 PM Jim Apple wrote: > > > The Project Management Committee (PMC) for Apache Impala has invited > Zoram > > Thanga to become a committer and we are pleased to announce that t

jenkins.impala.io maintenance coming up

Hi All, We plan to perform some maintenance on jenkins.impala.io on Wednesday morning PST. In anticipation of this, I will start a backup of the current state shortly. This should not affect the service availability. Please let me know if you experience any issues. I will send another notification

Re: jenkins.impala.io maintenance coming up

Hi All, Maintenance work will start in about an hour. Jenkins will stop accepting new builds momentarily and running builds might be aborted. I will send another update once maintenance has been completed. Cheers, Lars On Tue, Dec 4, 2018 at 11:09 AM Lars Volker wrote: > Hi All, > >

Re: jenkins.impala.io maintenance coming up

Jenkins maintenance has been completed and the service is back up. I had to cancel one build and reached out to the owner directly. Please let me know if you experience any issues. Cheers, Lars On Wed, Dec 5, 2018 at 9:17 AM Lars Volker wrote: > Hi All, > > Maintenance work will start

Re: jenkins.impala.io maintenance coming up

Following this morning's maintenance we have to restart Jenkins again. Apologies for the short notice. I'll send an all-clear when it's back. On Wed, Dec 5, 2018 at 12:04 PM Lars Volker wrote: > Jenkins maintenance has been completed and the service is back up. I had > to

Jenkins issues

Hi All, We are currently experiencing issues with Jenkins not accepting new pre-submit jobs. You can follow along at IMPALA-7938 . Cheers, Lars

Re: Jenkins issues

After a restart Jenkins is accepting jobs again. We'll keep an eye on it for now. On Thu, Dec 6, 2018 at 2:39 PM Lars Volker wrote: > Hi All, > > We are currently experiencing issues with Jenkins not accepting new > pre-submit jobs. You can follow along at IMP

Re: jenkins.impala.io maintenance coming up

t > > can't run GVO. > > > > Cheers, > > Gabor > > > > > > On Thu, Dec 6, 2018 at 12:14 AM Lars Volker wrote: > > > > > Following this morning's maintenance we have to restart Jenkins again. > > > Apologies for the short not

Re: [Patch Ready] Add support for reading ORC complex types

I think it's an excellent idea to have a face-to-face video meeting with the larger community on this mailing list. It might not be convenient to have a regular schedule due to time zone constraints, but a one-off to say "hi", introduce each other, and have a discussion would be helpful. I can star

Impala Video Meeting

Hi All, I would like to pick up Quanlong's and Jim's idea from a different thread and organize a video call for the larger Impala development community. This meeting will be open to all contributors, regardless of being a committer or not. The goal of the first meeting will be that everyone gets t

Re: Jenkins.impala.io preparing for shut down prior to upgrade/restart

Thank you for doing the upgrade, David! On Wed, Jan 16, 2019 at 2:43 PM David Knupp wrote: > Jenkins is back up and running, with version 2.150.2 > > A few jobs did need to be aborted, and these have been restarted: > >- https://gerrit.cloudera.org/c/11575 (Tim Armstrong) >- https://gerr

Re: Impala Video Meeting

Thanks for the feedback. I looked at Beijing and San Francisco timezones and 8am Beijing / 4pm San Francisco look like a good option. How would this date work for you (Link )? Thur

Re: Impala Video Meeting

M Tim Armstrong wrote: > That would work for me too > > On Wed., 6 Feb. 2019, 13:11 Quanlong Huang, > wrote: > > > Thank you, Lars! I'm good for this time. Looking forward to it! > > > > Thanks, > > Quanlong > > > > On Wed, Feb 6, 2019 at 6:3

Re: Impala Video Meeting

ars! > > Should we create a Slack channel? So we can type something in case anyone > has hardware issues, or to paste some resources in need. First time to use > Google meeting. Not sure about this... > > Thanks, > Quanlong > > On Sat, Feb 16, 2019 at 3:03 AM La

Next round of the Impala community meeting

Hi All, I propose to have the next Impala community meetings on Thursday, March 14th, 4pm PST/San Francisco - Friday, March 15th, 8am CST/Beijing. If that time doesn't work for you but you would like to join, please reply to this email with a new time proposal. If there are no objections I wil

Re: Next round of the Impala community meeting

Jose (USA - California) Friday, March 15, 2019 at 8:00:00 am PDT > > On Tue, Mar 5, 2019 at 6:23 AM Tim Armstrong > wrote: > > > WFM. I think we should also consider a future meeting time (not this one) > > that will make it easy for people in Europe to join as well. >

Re: Next round of the Impala community meeting

27;t feel I have much to contribute - probably not > > worth a reschedule by itself. > > > > On Wed, 6 Mar 2019 at 00:21, Lars Volker wrote: > > > > > > I'm good with that time too. However, I have not seen interest from > folks > > > in Europe, nei

Re: Next round of the Impala community meeting

the week after 15. is also not the best for us. > > I am interested in the community meeting, but it is not super important for > me to join. > > On Wed, Mar 6, 2019 at 7:28 PM Lars Volker wrote: > > > When would be a better time for folks in Hungary (i.e. no public > h

Re: Next round of the Impala community meeting

How does it work for the folks in Budapest? On Mon, Mar 11, 2019 at 7:37 AM Quanlong Huang wrote: > I'm ok with the time. Thank you, Lars! > > On Sat, Mar 9, 2019 at 6:18 AM Lars Volker wrote: > > > How would moving Quanlong's proposed schedule to Monday, Marc

Re: CWiki write access

I added you, please have a look to see if it worked. Cheers, Lars On Tue, Mar 12, 2019 at 3:50 PM Joe McDonnell wrote: > Can someone add write access for username "joemcdonnell"? I have some > changes I'd like to make to the Impala wiki. > > Thanks, > Joe >

Re: Add a parameter in Jenkins job cherrypick-2.x-and-test

The Jenkins job uses compare_branches.py to do the cherry picking. That script takes source_branch and target_branch parameters, but they need to be valid keys into the ignored commits file. You'd probably want to amend that script

Re: Next round of the Impala community meeting

wrote: > Works for me as well! > > Thanks, > Zoltan > > > On Mon, Mar 11, 2019 at 4:46 PM Gabor Kaszab > wrote: > > > That seems much better from Budapest's pow! I would also be interested > > joining if this schedule works out for everyone. > > > &

Re: Add a parameter in Jenkins job cherrypick-2.x-and-test

> -- > Quanlong > > On Sat, Mar 16, 2019 at 12:17 AM Lars Volker wrote: > > > The Jenkins job uses compare_branches.py > > <https://github.com/apache/impala/blob/2.x/bin/compare_branches.py> to > do > > the cherry picking. That script takes source_branch an

Re: Next round of the Impala community meeting

like this: > > https://docs.google.com/document/d/166eE52awakVvmyQ0AIT1Y1giZX72mot3V8_37oIjNWc > > For people who will attend the meeting, feel free to write down any topics > of interest :) > > Cheers, > Quanlong > > On Sat, Mar 16, 2019 at 12:34 AM Lars Volker wrote:

New Impala Community Slack Workspace

Hi All, We have created a Slack community for the Impala project. It is public and we welcome everyone to join us. You can do so by clicking on this invite link

Re: Remote read testing in precommit

+1, thanks for working on this! On Fri, Apr 5, 2019 at 11:18 AM Jim Apple wrote: > I'm in favor. Given the importance of remote reads, I would even be in > favor of these if it DID extend the critical path. > > On Fri, Apr 5, 2019 at 10:41 AM Tim Armstrong > wrote: > > > This is really about te

Re: New committer - Pooja Nilangekar

Congratulations Pooja and welcome to our round! On Sat, Apr 13, 2019, 08:59 Tim Armstrong wrote: > The Project Management Committee (PMC) for Apache Impala has invited > Pooja Nilangekar to become a committer and we are pleased to announce that > they have accepted. > Congratulations and welcom

Re: Jenkins security update and server restart (jenkins.impala.io)

Thanks for taking care of the update, Bharath! On Sat, Apr 13, 2019 at 12:56 PM Bharath Vissapragada wrote: > Jenkins is back up and running. Please let me know if something looks off! > > On Wed, Apr 10, 2019 at 9:37 AM Bharath Vissapragada < > [email protected]> > wrote: > > > Currently ru

Re: Remote read testing in precommit

tests/ > > Are there any objections to me modifying parallel-all-tests and therefore > precommit to run this job? I'll wait a couple of days for lazy consensus > then go ahead. > > Thanks, > Tim > > On Fri, Apr 5, 2019 at 3:03 PM Lars Volker wrote: > > > +1,

Re: Please set a Fix Version when you close a JIRA

Thanks for the reminder, Tim. If you are curious whether this affects you, you can use the following Jira query to find out: "assignee = currentUser() and resolution is not empty and fixVersion is empty order by updated desc" https://issues.apache.org/jira/issues/?jql=assignee%20%3D%20currentUser

New Committer: Sahil Takiar

Hi All, The Project Management Committee (PMC) for Apache Impala has invited Sahil Takiar to become a committer and we are pleased to announce that he has accepted. Welcome and congratulations, Sahil!

Re: Maintenance downtime for the Impala public Jenkins server

Thank you for taking care of this, Laszlo! On Wed, May 22, 2019 at 8:31 AM Laszlo Gaal wrote: > The service is up and running again. > > Thank you for your patience. > > On Wed, May 22, 2019 at 5:20 PM Laszlo Gaal > wrote: > > > The server instance has been taken offline and will be restarted s

New PMC Members: Gabor Kaszab and Bikramjeet Vig

The Project Management Committee (PMC) for Apache Impala has invited Gabor Kaszab and Bikramjeet Vig to become PMC members and we are pleased to announce that they have accepted. Congratulations and welcome, Gabor and Bikram!

Jenkins Maintenance today at 4:30pm Pacific

Hi All, This afternoon at 4:30pm Pacific I will briefly shutdown our Jenkins instance to install security updates. I expect this to take less than 30 minutes and will send another email once the work is complete. Apologies for the inconvenience. Cheers, Lars

Re: Jenkins Maintenance today at 4:30pm Pacific

I completed the maintenance work and restarted Jenkins. Please make sure to restart any jobs you had running. Again, apologies for any inconvenience this has caused. Cheers, Lars On Tue, Jun 11, 2019 at 11:52 AM Lars Volker wrote: > Hi All, > > This afternoon at 4:30pm Pacific I wil

New Committer: Laszlo Gaal

Hi All, The Project Management Committee (PMC) for Apache Impala has invited Laszlo Gaal to become a committer and we are pleased to announce that he has accepted. Welcome and congratulations, Laszlo!

Re: Add a parameter in Jenkins job cherrypick-2.x-and-test

send > >> the whole branch for review, which will open a new review for each of > the > >> changes and then submit them manually. > >> > >> Cheers, Lars > >> > >> On Fri, Mar 15, 2019 at 6:09 PM Quanlong Huang > > >> wrote:

Re: Apache JIRA Bug Tracker

Done. Cheers, Lars On Wed, Jul 17, 2019 at 7:40 AM Kurt Deschler wrote: > Hello, > Please add me as a contributor on the Apache JIRA bug tracker for the > Impala project. Thanks, > -Kurt Deschler >

Re: jenkins.impala.io will be restarted for updates

Thank you for doing the maintenance, Sahil! On Thu, Jul 18, 2019 at 9:15 PM Sahil Takiar wrote: > Maintenance is complete, all the killed jobs have been restarted. > > Thanks, > Sahil > > On Thu, Jul 18, 2019 at 8:54 PM Sahil Takiar > wrote: > > > Maintenance is starting now. Unfortunately, som

Re: jenkins.impala.io will be restarted for updates

Thank you for doing the maintenance, Vihang! On Wed, Jul 31, 2019, 23:43 Vihang Karajgaonkar wrote: > Jenkins has been restarted and is back up and running. Jobs related to > following two reviews were aborted and I resubmitted them again. Let me > know if you notice anything wrong. > > https://

  1   2   >