Re: Add total number of started threads to /threadz

Thank you for the feedback. I opened IMPALA-5643 to track this and pushed a change here: https://gerrit.cloudera.org/#/c/7390/ On Mon, Jul 10, 2017 at 10:25 AM, Henry Robinson wrote: > This seems valuable to me. > > On 28 June 2017 at 21:26, Lars Volker

Re: Jenkins maintenance in 30 minutes

Hi All, Jenkins maintenance has been completed and the service should be working again. However, some plugins issued a warning that parts of their configuration format have changed and thus jobs may need to be reconfigured. I started a canary job here that is currently still running:

Jenkins maintenance in 30 minutes

Hi All, In about 30 minutes, jenkins.impala.io will become unavailable for maintenance. I expect it to take no more than 30 minutes and will send an additional email to this list once the service is back online. In case your jobs get terminated, please restart them. Thank you, Lars

CVE-2017-5640 Apache Impala (incubating) Information Disclosure

CVE-2017-5640 Apache Impala (incubating) Information Disclosure Severity: High Versions Affected: Apache Impala (incubating) 2.7.0 to 2.8.0 Description: It was noticed that a malicious process impersonating an Impala daemon could cause Impala daemons to skip authentication checks when Kerberos

Re: Can't start minicluster

Using that command and then running a build without -noclean WFM. Thanks! On Sun, Jul 9, 2017 at 9:10 PM, Tim Armstrong wrote: > Maybe the thrift be/generated-sources are out of sync with the source code? > > We had some kind of metastore scheme upgrade that caused the

Re: Add total number of started threads to /threadz

This seems valuable to me. On 28 June 2017 at 21:26, Lars Volker wrote: > Hi All, > > While investigating IMPALA-5598 I added a counter with the total number of > threads to /threadz. See below for what it looks like (I hope the ASF > mailer won't eat the format). Does this

[SECURITY] CVE-2017-5652 Apache Impala (incubating) Information Disclosure

CVE-2017-5652 Apache Impala (incubating) Information Disclosure Severity: High Versions Affected: Apache Impala (incubating) 2.7.0 to 2.8.0 Description: During a routine security analysis, it was found that one of the ports sent data in plaintext even when the cluster was configured to use

Re: Impala Build issue

For #1, I recommend one of the following: 1. Get access to Oracle JDK7 however you would normally do so (legally, of course) 2. OR use OpenJDK7 8. OR use JDK8, either Oracle or OpenJDK On Sun, Jul 9, 2017 at 1:31 PM, Suresh Pujari wrote: > Hi Sir, > >I am

Re: IMPALA-4326 - split() function

That standard 2016 spec did not predate hive's implementation of lateral view On Sunday, July 9, 2017, Greg Rahn wrote: > (also commented on IMPALA-4326) > > For this functionality, I'd prefer to follow what Postgres does and use its > well-named functions like

Impala Build issue

Hi Sir, I am receiving the below issues. 1. the JDK path "*http://download.oracle.com/otn-pub/java/jdk/7u75-b13/jdk-7u75-linux-x64.tar.g z*" in the install.sh is incorrect because of which errors are coming. sudo