Re: jenkins.impala.io maintenance

The update has been applied and Jenkins should be available again. Please let me know if you encounter any issues. On Wed, Jan 13, 2021 at 10:47 AM Thomas Tauber-Marshall < tmarsh...@cloudera.com> wrote: > The public Jenkins instance will be taken offline shortly for a security

jenkins.impala.io maintenance

The public Jenkins instance will be taken offline shortly for a security update. There are no jobs running currently, so hopefully the impact will be minimal. An email will be sent when the service is available again. Thank you for your patience, - Thomas

Breaking change in impala-shell

Impala devs, There is a patch that has just gone into master which switches the default protocol for impala-shell from beeswax to hiveserver2, as part of the ongoing process of deprecating and removing beeswax, see https://issues.apache.org/jira/browse/IMPALA-10074 Because this is a breaking

Re: [VOTE] 3.4.0 release candidate 2

+1 (binding) I ran: https://jenkins.impala.io/job/release-test-ub1604/34/ On Fri, Apr 17, 2020 at 10:43 AM Joe McDonnell wrote: > Correction: this is the link: > https://dist.apache.org/repos/dist/dev/impala/3.4.0/RC2/ > > On Fri, Apr 17, 2020 at 10:42 AM Joe McDonnell > wrote: > > > This is

Re: Branching/tagging native-toolchain projects's state for the Impala 3.4.0 branch

Agreed that it's definitely a good idea to branch native-toolchain for the release. We've done this in the past in a way that corresponded with Cloudera releases, since native-toolchain is a Cloudera maintained project and Cloudera has historically always had a close match between Cloudera

Re: [VOTE] 3.3.0 release candidate 1

+1 (binding) https://jenkins.impala.io/view/Utility/job/release-test-ub1604/27/ On Wed, Aug 21, 2019 at 8:55 PM Lars Volker wrote: > +1 (binding) > >- Checked the signature >- Ran buildall.sh >- Ran a handful of queries, created and dropped a table > > > On Wed, Aug 21, 2019 at 1:31

Re: Query status "Session Closed"

6cd83d9dd62f0%7C0%7C0%7C637006495239689446sdata=zT%2BlqH0orz4KiyknWbGD%2FvQUSnESBg7byz9cRefbNrs%3Dreserved=0 > > On Mon, Aug 5, 2019 at 5:15 PM Thomas Tauber-Marshall < > tmarsh...@cloudera.com> wrote: > > > Impala has two client interfaces with slightly different session >

Re: Query status "Session Closed"

Impala has two client interfaces with slightly different session behavior: Beewax (default port 21000) - sessions are created when the client connects Hiveserver2 (default port 21050) - sessions are created when OpenSession() is called In both cases, sessions can be closed either if - the

New Committer - Andrew Sherman

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

Re: [VOTE] 3.2.0 release candidate 1

+1 (binding) Jenkins job: https://jenkins.impala.io/job/release-test-ub1604/23/ On Thu, Mar 21, 2019 at 9:05 AM Jim Apple wrote: > +1. I checked the things in > > https://cwiki.apache.org/confluence/display/IMPALA/How+to+Release#HowtoRelease-HowtoVoteonaReleaseCandidate > , plus a run of the

Re: [DISCUSS] 3.2.0 release

If its not too late, it would be great to include this fix: https://issues.apache.org/jira/browse/IMPALA-8299 On Thu, Mar 14, 2019 at 5:38 AM Gabor Kaszab wrote: > (Sorry, accidentally sent out the mail too early) > - Alex sent in a number of doc commits covering changes that are already > in,

Re: Improving Kudu Build Support

ase_dir = os.environ["IMPALA_KUDU_HOME"] File "/usr/lib/python2.7/UserDict.py", line 40, in __getitem__ raise KeyError(key) KeyError: 'IMPALA_KUDU_HOME' Let me know if you encounter any other issues. On Thu, Aug 30, 2018 at 1:31 PM Thomas Tauber-Marshall < tmarsh...@cloudera.c

Re: Improving Kudu Build Support

Aug 22, 2018 at 11:31 AM Thomas Tauber-Marshall < tmarsh...@cloudera.com> wrote: > So the toolchain binaries are provided for: centos5,6,7, debian7,8, > sles11,12, ubuntu14,16 > The new CDH component binaries will be available for: redhat6,7, debian8, > sles12, ubuntu16 > so we wou

Re: Improving Kudu Build Support

t; 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 > >

Improving Kudu Build Support

Impala community, For years now, Impala has utilized tarballs built by Cloudera and uploaded to S3 for running most of the Hadoop components in the testing minicluster. The one exception to this is Kudu, which is instead provided by the toolchain. This was never ideal - native-toolchain makes

Re: Assign JIRA

s > Add users to a role. Use the > "Contributors" role. > Thanks! > > On Mon, Aug 6, 2018 at 12:54 PM, Thomas Tauber-Marshall < > tmarsh...@cloudera.com.invalid> wrote: > > > I'm trying to assign a JIRA to a new contributor (Andrew Sherman), but > > they're not sho

Assign JIRA

I'm trying to assign a JIRA to a new contributor (Andrew Sherman), but they're not showing up as an option. I guess I need admin privileges on JIRA to add them to the project? Can anyone help me out with that? Thanks

Re: boost::scoped_ptr vs std::unique_ptr

I'm definitely in favor of using more standard c++ to reduce both confusion and our reliance on boost, especially as I suspect a lot of people (eg. me) don't know the subtle difference between scoped_ptr and unique_ptr off the top of their head anyways. Fwiw, I was under the impression from

Re: Does Impala support grouping sets or some other operation

No, Impala does not support grouping sets. There is work ongoing to allow for multiple groupings in a single query (see https://issues.apache.org/jira/browse/IMPALA-110), which will eventually be used to implement grouping sets, but there is no timeline on when that work will be done. We of

Broken/Flaky Tests

s have been addressed. Thanks, Thomas Tauber-Marshall

Re: Statically link Kudu client

There isn't a built in way in buildall to statically link the Kudu client, and I'm not aware of any way to do it. We don't provide any guarantees or do any testing around compatibility of Impala with Kudu clients of different versions other than the versions that correspond, i.e. the value of

Re: [VOTE] 3.0.0 release candidate 1

+1 binding Ran the release test job: https://jenkins.impala.io/job/release-test-ub1604/13/ On Wed, May 2, 2018 at 9:17 PM Jim Apple wrote: > +1, binding > > I looked at the output of the release testing job that Sailesh appears to > have run on jenkins.impala.io. > > On

Native toolchain branching

that for now, most changes to native-toolchain that go into master will also need to be cherry-picked onto 5.x. Given the low frequency of commits to native-toolchain, we will probably not automate this process. Thanks, Thomas Tauber-Marshall

Re: [ANNOUNCE] Apache Impala 2.11.0 release

On Thu, Jan 18, 2018 at 10:43 AM Lars Volker <l...@cloudera.com> wrote: > Done: https://twitter.com/ApacheImpala/status/954061402070704129 Thanks! > > > On Thu, Jan 18, 2018 at 10:31 AM, Thomas Tauber-Marshall < > tmarsh...@cloudera.com> wrote: > > > -eve

[ANNOUNCE] Apache Impala 2.11.0 release

The Apache Impala team is pleased to announce the release of Impala 2.11.0 Impala is a high-performance distributed SQL engine. The release is available at: https://impala.apache.org/downloads.html Thanks, The Apache Impala team

2.11 release progress

Just an update on the 2.11 release progress: 2.11 has effectively been 'released' now, as the artifacts are available on the website: http://impala.apache.org/downloads.html However, the docs are not quite ready yet. Once they are, hopefully in a few days, I'll send out the formal ANNOUNCEMENT,

Re: New Impala Contributors: IMPALA-6296

ow? > Yes, you can just post it as a comment on the review using the "Reply" button > > - Mansi > ​ > > On Tue, Jan 2, 2018 at 3:04 PM, Thomas Tauber-Marshall < > tmarsh...@cloudera.com> wrote: > >> On Fri, Dec 29, 2017 at 11:12 AM Manaswini Mahara

Re: New Impala Contributors: IMPALA-6296

On Fri, Dec 29, 2017 at 11:12 AM Manaswini Maharana wrote: > I've pushed the initial changes to - > https://gerrit.cloudera.org/#/c/8923/ > > Steps that I've followed to make this contribution - As this is my first, > I want to elaborate a little bit to ensure I'm

Re: [RESULT] Vote on Impala 2.11.0 release candidate 1

Also, is there a PMC member that can help me with step #19 (publishing the release artifacts) from https://cwiki.apache.org/confluence/display/IMPALA/How+to+Release# Thanks On Thu, Dec 28, 2017 at 1:03 PM Thomas Tauber-Marshall < tmarsh...@cloudera.com> wrote: > > https://list

[VOTE] 2.11.0 release candidate 1

This is a vote to release Impala 2.11.0 The artifacts for testing can be downloaded from: https://dist.apache.org/repos/dist/dev/impala/2.11.0/RC1/ Git tag: 2.11.0-rc1 Tree hash: 9618d0f833cf826252d2c1b2a720eaabe1bef689 Please vote +1 or -1. -1 votes should be accompanied by an explanation of

Re: Re:Re: Build failure in TestAdmissionController

On Sun, Dec 10, 2017 at 2:38 PM Quanlong Huang wrote: > Hi all, > > > I've fixed all the test failures in my dev environment and here is the > patch: https://gerrit.cloudera.org/#/c/8807/ > It has passed the gerrit-verify-dryrun-external test and here is the link: >

Re: [DISCUSS] 2.11.0 release

k that makes sense. We'll have to go through the fix versions of > > recent JIRAs and make sure that they weren't set to 2.12 though. > > > > On Thu, Dec 7, 2017 at 9:33 AM, Thomas Tauber-Marshall < > > tmarsh...@cloudera.com> wrote: > > > >> Since the resp

[DISCUSS] 2.11.0 release

Folks, It has been over 2 months since we released Apache Impala 2.10.0 and there have been new feature improvements and a good number of bug fixes checked in since then. I propose that we release 2.11.0 soon and I volunteer to be its release manager. Please speak up and let the community know