Re: Docker image for impala development

I don't know of a up-to-date docker image or dockerfile. When you say "following the apache site docker image for impala dev steps", I assume you mean this page: https://cwiki.apache.org/confluence/display/IMPALA/Docker+for+Impala+Developers It does take a lot of time and a lot of disk space, wh

thread_local compatible with other threading models?

A quick git grep shows use of both boost::thread and pthread. C++14 has a thread_local keyword: http://eel.is/c++draft/basic.stc.thread Do we know if the semantics of thread_local in C++14 are compatible with thread-locality in pthreads and boost::thread?

Re: Outdated information in the wiki

Jinchul, I changed the admin permissions for you. I think you now have access to editing the wiki. On Mon, Nov 13, 2017 at 4:30 PM, Jin Chul Kim wrote: > Hi, > > It seems the wiki page has not up-to-date information. Please see > https://cwiki.apache.org/confluence/display/IMPALA/How+ > to+load+

Re: Getting started with 'newbie' tasks

https://issues.apache.org/jira/browse/IMPALA-5341 might be a good choice On Sun, Nov 12, 2017 at 12:58 AM, Sagar Batchu wrote: > Hi Impala devs, > > I came across several Impala tasks listed under Apache's help wanted > sections. Do you have any recommendations on which 'newbie' tasks >

Re: Graduation resolution proposal

is a board resolution: > > http://incubator.apache.org/guides/graduation.html# > submission_of_the_resolution_to_the_board > > On Tue, Oct 31, 2017 at 10:36 PM, Todd Lipcon wrote: > >> Thanks Jim! >> >> -Todd >> >> On Tue, Oct 31, 2017 at 10:35 PM,

Experienced Impala Contributors: writing "New Impala Contributors" walk-throughs

If you are an experienced Impala contributor, and you'd like to help with community outreach, you can post a walkthrough of a ticket that a newbie will be able to address in only an hour of your time. Get started by looking through open tickets labelled "newbie" https://issues.apache.org/jira/issu

Re: Graduation resolution proposal

/guides/graduation.html#submission_of_the_resolution_to_the_board On Tue, Oct 31, 2017 at 10:36 PM, Todd Lipcon wrote: > Thanks Jim! > > -Todd > > On Tue, Oct 31, 2017 at 10:35 PM, Jim Apple wrote: > > > I have sent this to general@ for discussion: > > > >

S3 connections

http://impala.apache.org/docs/build/html/topics/impala_s3.html recommends "Set the safety valve fs.s3a.connection.maximum to 1500 for impalad." For best performance, should this be increased for nodes with very high CPU, RAM, or bandwidth? Or decreased for less-beefy nodes?

Re: A question about loading data by functional-query workload

The recommended way to get a development environment set up calls https://github.com/apache/incubator-impala/blob/master/bin/bootstrap_development.sh which calls /buildall.sh -noclean -format -testdata -skiptests. That is the recommended way to load the test data. On Tue, Nov 7, 2017 at 10:17 PM,

Re: Mentoring Programme, was Re: APACHE - IMPALA

seful either way, it would mostly have been for resumes so I can be >> patient. Thank you for your reply. >> >> On Oct 24, 2017 1:14 PM, "Jim Apple" wrote: >> >>> I am glad that you have made a decision to contribute. This is a good >>> mailing

Re: Which instruction set extensions should Impala require?

available on AMD chips until 2015. >> >> It seems less disruptive if we drop support for older processors in a major >> release - i.e. Impala 3.0. I don't think that needs to be a strict policy >> of never dropping hardware support in a minor release but I think it&

Re: IMPALA-5607

My intuition is that this would not be as easy as decimal_v2 to put behind a flag. Is that right? On Wed, Nov 1, 2017 at 2:26 PM, Greg Rahn wrote: > It might not be that simple. > > One side-effect of the return type promotion of EXTRACT and DATE_PART() is > that INSERTs that use either could p

Which instruction set extensions should Impala require?

In a discussion on https://issues.apache.org/jira/browse/IMPALA-6128, we are talking about which instruction sets (available on newer x86-64 processors) we want to require. At this point, I'm not sure how strong the motivation is for requiring certain instruction sets, but it may be worth some eff

New Impala Contributors: IMPALA-3323

If you'd like to contribute a patch to Impala, but aren't sure what you want to work on, you can look at Impala's newbie issues: https://issues.apache.org/jira/issues/?filter=12341668. You can find detailed instructions on submitting patches at https://cwiki.apache.org/confluence/display/IMPALA/Con

Re: Graduation resolution proposal

I have sent this to general@ for discussion: https://lists.apache.org/thread.html/6b8598408f76a472532923c5a7fc510470b21671677ba3486568c57e@%3Cgeneral.incubator.apache.org%3E On Sat, Oct 28, 2017 at 8:12 AM, Jim Apple wrote: > Below is a graduation resolution I would like to send to > g

PMC Chair vote results in detail

In response to a voter query, the detailed vote results are as follows: The final electronic tally was 11-6. However, Marcel and I were both sent two ballots, for technical reasons, and for the same reason, Marcel was unable to vote either time. That makes the final actual tally 10-7.

Graduation resolution proposal

are appointed to serve as the initial members of the Apache Impala Project: * Alex Behm * Bharath Vissapragada * Brock Noland * Carl Steinbach * Casey Ching * Daniel Hecht * Dimitris Tsirogiannis * Henry Robinson * Ishaa

Re: Wiki update no triaging test failures

Nice work, Phil! On Fri, Oct 27, 2017 at 9:39 AM, Philip Zeyliger wrote: > I wrote up some quick notes on how to look at logs on a Jenkins server to > figure out what failed. They're at > https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action? > pageId=65147141&selectedPageVersions=

New Impala Contributors: IMPALA-941

If you'd like to contribute a patch to Impala, but aren't sure what you want to work on, you can look at Impala's newbie issues: https://issues.apache.org/jira/issues/?filter=12341668. You can find detailed instructions on submitting patches at https://cwiki.apache.org/confluence/display/IMPALA/Con

Mentoring Programme, was Re: APACHE - IMPALA

I am glad that you have made a decision to contribute. This is a good mailing list for talking about issues like this. I have changed the subject to make it reflect the topic of conversation - a topic like the original one ("APACHE - IMPALA") applies to all threads on this mailing list. https://co

Re: Will there be a 2.12.0 release?

Do we want to have a 3.0 process, where one person tracks all of the open breaking-change JIRAs and makes sure nothing gets accidentally left out? I ask this because, if the answer is "yes", we might make the 2.12 decision based on scope and quantity of 3.0 JIRAs. On Tue, Oct 24, 2017 at 10:07 AM,

Re: Broken Link

Fxied; thanks for finding this, Kenneth. On Mon, Oct 23, 2017 at 8:04 PM, kenneth mcfarland < kennethpmcfarl...@gmail.com> wrote: > That works great, thank you! > > On Oct 23, 2017 7:57 PM, "Mostafa Mokhtar" wrote: > > > This link should work: > > > > cidrdb.org/cidr2015/Papers/CIDR15_Paper28.pd

Re: Podling Report Reminder - November 2017

d > > > > On Sat, Oct 21, 2017 at 4:34 PM, Jim Apple wrote: > > > > > Please review: > > > > > > Impala is a high-performance C++ and Java SQL query engine for data > > stored > > > in > > > Apache Hadoop-based clusters. > >

Re: Time for graduation?

t; -Todd > > On Mon, Oct 23, 2017 at 11:14 AM, Jim Apple wrote: > > > I have sent out the Chair election ballot via steve.apache.org to people > > who will be listed in our resolution as PMC members, via email addresses > (@ > > apache.org). Please vote. The vote clo

Re: Time for graduation?

I have sent out the Chair election ballot via steve.apache.org to people who will be listed in our resolution as PMC members, via email addresses (@ apache.org). Please vote. The vote closes Friday. On Fri, Oct 20, 2017 at 10:19 PM, Jim Apple wrote: > I have a resolution with a blank space

Re: Podling Report Reminder - November 2017

Please review: Impala is a high-performance C++ and Java SQL query engine for data stored in Apache Hadoop-based clusters. Impala has been incubating since 2015-12-03. Three most important issues to address in the move towards graduation: Our graduation proposal is in the works. Any issues t

Re: Want to contribute

You can subscribe to the list by mailing dev-subscr...@impala.incubator.apache.org. On Wed, Oct 18, 2017 at 1:52 AM, Kapil Jain wrote: > I would like to contribute. Could you please add me to the list. > > Kapil >

Re: Time for graduation?

l PMC members as voters, starting on Monday using https://steve.apache.org/, following examples from other ASF projects. On Thu, Oct 12, 2017 at 3:24 PM, Jim Apple wrote: > I think it would be a good time to graduate. I'm very proud of the > progress the community has made in terms of act

[RESULT] [VOTE] Graduate to a TLP

Mukil, Matthew Jacobs, yu feng, Philip Zeyliger, John Sherman, Joe McDonnell, Anuj Phadke, Daniel Hecht, David Knupp, Zachary Amsden, Quanlong Huang, Jim Apple Other votes: none We haven't graduated yet. The next steps are these: 1. Prepare a charter. 2. Start a discussion on general@incu

Re: Using Gerrit drafts

I'm surprised my edits gave you the impression that I think people should not review their code before asking for peer review. On Thu, Oct 19, 2017 at 1:06 PM, Daniel Hecht wrote: > I think it's a good idea for everyone to review their own code before > asking for a peer review. A lot of style

Re: Using Gerrit drafts

Sorry, didn't mean "workflow", mean "repo". On Thu, Oct 19, 2017 at 11:54 AM, Jim Apple wrote: > In between when I saw the edit and when I saw this email, I re-edited. > Please fell free to re-edit again. Mostly I didn't want "Publish" to sound

Re: Using Gerrit drafts

In between when I saw the edit and when I saw this email, I re-edited. Please fell free to re-edit again. Mostly I didn't want "Publish" to sound like it was going to be part of the workflow, but I also made drafts the second suggestion, because I would expect gerrit newbies to publish there too of

New Impala contributors: IMPALA-5314

If you'd like to contribute a patch to Impala, but aren't sure what you want to work on, you can look at Impala's newbie issues: https://issues.apache.org/jira/issues/?filter=12341668. You can find detailed instructions on submitting patches at https://cwiki.apache.org/confluence/display/IMPALA/Con

Re: New Impala contributors: outreach

I am going to also start adding to https://helpwanted.apache.org/, now that https://issues.apache.org/jira/browse/COMDEV-225 is fixed. Here is the first one: https://helpwanted.apache.org/task.html?3cb146d3a253d0dd1f951c151b37f7e8e8fc97c7 On Wed, Sep 6, 2017 at 3:01 PM, Jim Apple wrote: >

Re: Graduation voting and work agenda

17, 2017 at 7:00 PM, Jim Apple wrote: > Following the community discussion, my observations from general@incubator, > and https://incubator.apache.org/guides/graduation.html#the_ > graduation_process , I will do the following: > > 1. Call for a formal graduation vote on dev@. >

[VOTE] Graduate to a TLP

Following our discussion https://lists.apache.org/thread.html/2f5db4788aff9b0557354b9106c0328a29c1f90c1a74a228163949d2@%3Cdev.impala.apache.org%3E , I propose that we graduate to a TLP. According to https://incubator.apache.org/guides/graduation.html#community_graduation_vote this is not required,

Graduation voting and work agenda

Following the community discussion, my observations from general@incubator, and https://incubator.apache.org/guides/graduation.html#the_graduation_process , I will do the following: 1. Call for a formal graduation vote on dev@. 2. While that is happening, let general@ know we are voting. Should

Re: Impala Version Stability

Impala is a project at the Apache Software Foundation. Various vendors package and distribute Impala, including Cloudera. That being said, this is a mailing list for the Apache Impala community, so the details of that and how to dig into that might be better addressed on a Cloudera forum. On Sun,

Re: Time for graduation?

All of that SGTM

Re: Time for graduation?

I think it would be a good time to graduate. I'm very proud of the progress the community has made in terms of acting in an Apache way. Some logistics: I would be happy to serve as an initial chair. I'll draft a resolution, with a blank space for chair. This doesn't mean we have to agree now is

New Impala contributors: IMPALA-5341

If you'd like to contribute a patch to Impala, but aren't sure what you want to work on, you can look at Impala's newbie issues: https://issues.apache.org/jira/issues/?filter=12341668. You can find detailed instructions on submitting patches at https://cwiki.apache.org/confluence/display/IMPALA/Con

New Impala contributors: IMPALA-5362

If you'd like to contribute a patch to Impala, but aren't sure what you want to work on, you can look at Impala's newbie issues: https://issues.apache.org/jira/issues/?filter=12341668. You can find detailed instructions on submitting patches at https://cwiki.apache.org/confluence/display/IMPALA/Con

New Impala committer: Bikramjeet Vig

The Podling Project Management Committee (PPMC) for Apache Impala (incubating) has invited Bikramjeet Vig to become a committer and we are pleased to announce that they have accepted. Congratulations and welcome, Bikramjeet!

New Impala committer: Zach Amsden

The Podling Project Management Committee (PPMC) for Apache Impala (incubating) has invited Zach Amsden to become a committer and we are pleased to announce that they have accepted. Congratulations and welcome, Zach!

New Impala contributors: IMPALA-5392

If you'd like to contribute a patch to Impala, but aren't sure what you want to work on, you can look at Impala's newbie issues: https://issues.apache.org/jira/issues/?filter=12341668. You can find detailed instructions on submitting patches at https://cwiki.apache.org/confluence/display/IMPALA/Con

New Impala PPMC member: Bharath Vissapragada

The Podling Project Management Committee (PPMC) for Apache Impala (incubating) has invited Bharath Vissapragada to become a PPMC member and we are pleased to announce that they have accepted. Congratulations and welcome, Bharath!

Re: "tests for tests" in gerrit-verify-dryrun?

That would also enable unifying docs pre-merge testing with code pre-merge testing. On Mon, Sep 25, 2017 at 4:41 PM Daniel Hecht wrote: > +1 to branching based on e.g. files in commit. > > On Mon, Sep 25, 2017 at 4:33 PM, Philip Zeyliger > wrote: > > > I'm not entirely familiar with the current

New Impala contributors: IMPALA-5440

If you'd like to contribute a patch to Impala, but aren't sure what you want to work on, you can look at Impala's newbie issues: https://issues.apache.org/jira/issues/?filter=12341668. You can find detailed instructions on submitting patches at https://cwiki.apache.org/confluence/display/IMPALA/Con

Re: jenkins.impala.io pre-existing workspace

Nobody did. On Tue, Sep 19, 2017 at 2:29 PM, Matthew Jacobs wrote: > Did anyone file a JIRA for this? I saw this again. > > On Thu, Aug 31, 2017 at 1:36 PM, Jim Apple wrote: > > Also, to be clear, I don't have the cycles to lead the fix-the-cleanup > > task at the m

Re: [RESULT] Vote on Impala 2.10.0 release candidate 2

I have updated the release instructions at https://cwiki.apache.org/confluence/display/IMPALA/How+to+Release to reflect this addition. On Wed, Sep 13, 2017 at 10:10 AM, sebb wrote: > The summary is easy to read, but has no context. > > Ideally the result mail should either form part of the VOTE

Re: [ANNOUNCE] Apache Impala (incubating) 2.10.0 release

-everyone but dev@ Thank you, Bharath! On Thu, Sep 14, 2017 at 10:41 PM, Bharath Vissapragada wrote: > The Apache Impala (incubating) team is pleased to announce the release of > Impala 2.10.0. > > Impala is a high-performance C++ and Java SQL query engine for data stored > in Apache Hadoop-bas

New Impala contributors: IMPALA-5610

If you'd like to contribute a patch to Impala, but aren't sure what you want to work on, you can look at Impala's newbie issues: https://issues.apache.org/jira/issues/?filter=12341668. You can find detailed instructions on submitting patches at https://cwiki.apache.org/confluence/display/IMPALA/Con

Re: Impala entry on Encyclopedia of Big Data

I'd be happy to join a team to do this. Anybody else? On Tue, Sep 12, 2017 at 10:22 AM, Dimitris Tsirogiannis < dtsirogian...@cloudera.com> wrote: > I've been contacted by the members of the editorial board of the new > Encyclopedia of Big Data asking if we can contribute an entry for Impala. > H

New Impala contributors: IMPALA-5614

If you'd like to contribute a patch to Impala, but aren't sure what you want to work on, you can look at Impala's newbie issues: https://issues.apache.org/jira/issues/?filter=12341668. You can find detailed instructions on submitting patches at https://cwiki.apache.org/confluence/display/IMPALA/Con

Re: expr-test stuck in getJNIEnv

. make fe && . bin/set-classpath.sh > 2. bin/create-test-configuration.sh > > Sailesh knows about the upstream HDFS bug which I think has been fixed but > not incorporated into Impala's dependencies. > > On Sun, Sep 10, 2017 at 1:42 PM Jim Apple wrote: > >> When I run

expr-test stuck in getJNIEnv

When I run expr-test, it gets stuck in getJNIEnv(). Here's the full stack trace: #0 __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 #1 0x74885dbd in __GI___pthread_mutex_lock (mutex=0x45fe5a0 ) at ../nptl/pthread_mutex_lock.c:80 #2 0x02cf79f6 in mutexL

Re: Encountering failure during build on docker

t;> /etc/sudoers* > root@ea385187b032:/#* su - impdev* > impdev@ea385187b032:~$ *sudo apt-get --yes install git* > impdev@ea385187b032:~$* git clone > https://git-wip-us.apache.org/repos/asf/incubator-impala.git > <https://git-wip-us.apache.org/repos/asf/incubator-impala.git>

Re: Encountering failure during build on docker

Can you provide: 1. The command you used to start the docker container 2. The output of gcc --version inside your docker container 3. The output of lsb_release -a both in the host and inside the docker container 4. The commands you ran inside the container Thank you! On Fri, Sep 8, 2017 at 7:

New Impala contributors: IMPALA-5886

If you'd like to contribute a patch to Impala, but aren't sure what you want to work on, you can look at Impala's newbie issues: https://issues.apache.org/jira/issues/?filter=12341668. You can find detailed instructions on submitting patches at https://cwiki.apache.org/confluence/display/IMPALA/Con

Re: New Impala contributors: outreach

OK, done: https://github.com/yourfirstpr/yourfirstpr.github.io/issues/86 https://github.com/up-for-grabs/up-for-grabs.net/pull/717 Can whoever runs the Apache Impala twitter account tweet at https://twitter.com/yourfirstpr?lang=en? On Sun, Sep 3, 2017 at 7:27 PM, Jim Apple wrote: > I

Re: New Impala contributors: IMPALA-5754

ives are harder to bring up in google results) > > On Wed, Sep 6, 2017 at 10:05 AM, Jim Apple wrote: > >> If you'd like to contribute a patch to Impala, but aren't sure what >> you want to work on, you can look at Impala's newbie issues: >> https://

New Impala contributors: IMPALA-5754

If you'd like to contribute a patch to Impala, but aren't sure what you want to work on, you can look at Impala's newbie issues: https://issues.apache.org/jira/issues/?filter=12341668. You can find detailed instructions on submitting patches at https://cwiki.apache.org/confluence/display/IMPALA/Con

New Impala contributors: getting started

If you are new to Impala and would like to contribute, you can start by setting up an Impala development environment. For this you'll need an Ubuntu 14.04 or 16.04 machine. Then just: git clone https://git-wip-us.apache.org/repos/asf/incubator-impala.git ~/Impala source ~/Impala/bin/bootstrap_deve

New Impala contributors: outreach

I'd like to encourage people who haven't contributed to Impala before to get started making patches. One way to do that would be to engage with communities where people for reaching out to new contributors. It appears that Your First PR has a mechanism to invite new contributors to the project by

Re: [VOTE] 2.10.0 release candidate 2 (RC2)

uild environment. > > On Thu, Aug 31, 2017 at 11:23 PM, Jim Apple wrote: > >> I think ASAN doesn't work with FE tests - I mistakenly left them in >> for this run. >> >> We have never before seen two jobs on the same worker in jenkins.impala.io >> .

Re: [VOTE] 2.10.0 release candidate 2 (RC2)

ean workspace leading to problems? This smells like an infra problem to > me, > Maybe do another run? > > > > > > On Thu, Aug 31, 2017 at 8:02 PM, Jim Apple wrote: > >> This ASAN testing failed: >> >> https://jenkins.impala.io/view/Utility/j

Re: [VOTE] 2.10.0 release candidate 2 (RC2)

e_node_rows_threshold': 0, 'enable_expr_rewrites': False} | table_format: text/none]. Looks like a crash to me. I didn't see a corresponding bug. Has anyone else seen something like this before? On Thu, Aug 31, 2017 at 1:15 PM, Jim Apple wrote: > BTW, this Jenkins job inc

Re: jenkins.impala.io pre-existing workspace

Also, to be clear, I don't have the cycles to lead the fix-the-cleanup task at the moment. On Wed, Aug 30, 2017 at 4:45 PM, Jim Apple wrote: > The workspace cleanup isn't working - see the last bit of any recent > ub1604 job: > https://jenkins.impala.io/view/Utility/jo

Re: [VOTE] 2.10.0 release candidate 2 (RC2)

https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/, builds 218-220 (once the instances come up). I tested with ImpalaLZO at this commit: https://github.com/cloudera/impala-lzo/tree/62c4b94ed6e89f0ce2068280864546ebccfb0729 On Thu, Aug 31, 2017 at 6:19 AM, Jim Apple wrote: > +1 > > https://jenkins

Re: [VOTE] 2.10.0 release candidate 2 (RC2)

Clarification: +1 (binding) As a reminder, binding votes in the PPMC vote are not binding in the IPMC vote unless the voter is also an IPMC member. Since I am not, this is a PPMC "+1 (binding)" only. On Thu, Aug 31, 2017 at 6:19 AM, Jim Apple wrote: > +1 > > https://je

Re: [VOTE] 2.10.0 release candidate 2 (RC2)

+1 https://jenkins.impala.io/job/release-test/20/console This tested following https://cwiki.apache.org/confluence/display/IMPALA/How+to+load+and+run+Impala+tests and https://cwiki.apache.org/confluence/display/IMPALA/How+to+Release#HowtoRelease-HowtoVoteonaReleaseCandidate. On Wed, Aug 30, 201

Re: jenkins.impala.io pre-existing workspace

The workspace cleanup isn't working - see the last bit of any recent ub1604 job: https://jenkins.impala.io/view/Utility/job/ubuntu-16.04-from-scratch/206/console 03:56:40.920 [WS-CLEANUP] Deleting project workspace...Cannot delete workspace :remote file operation failed: /home/ubuntu at hudson.re

Re: [VOTE] 2.10.0 release candidate 1 (RC1)

I ran some release tests following the instructions https://cwiki.apache.org/confluence/display/IMPALA/How+to+Release#HowtoRelease-HowtoVoteonaReleaseCandidate and https://cwiki.apache.org/confluence/display/IMPALA/How+to+load+and+run+Impala+tests. Everything passed. I would +1, but I notice down

Re: IGFS (Ignite FS) support

Doesn't look like there is a JIRA yet: https://issues.apache.org/jira/issues/?jql=project%20%3D%20IMPALA%20AND%20text%20~%20%22ignite%22 https://issues.apache.org/jira/issues/?jql=project%20%3D%20IMPALA%20AND%20text%20~%20%22igfs%22 You might want to file one as a single point of coordination for

Re: Re: Re: Re: Load Data from HDFS to Parquet

d data from > hdfs to parquet table not via external table or internal table？ > > > > > > > At 2017-08-15 10:53:55, "Jim Apple" wrote: >>http://impala.apache.org/docs/build/html/topics/impala_create_table.html#create_table >> >>I think you can

Re: Re: Re: Load Data from HDFS to Parquet

on the HDFS. > > > > > > > > At 2017-08-15 10:42:13, "Jim Apple" wrote: >>Is the data in a format that Impala can read? >> >>On Mon, Aug 14, 2017 at 7:31 PM, sky wrote: >>> Thank you, >>> I read the document.But it only des

Re: Re: Load Data from HDFS to Parquet

e? Thank You ! > > > > > > > > At 2017-08-15 03:25:43, "Jim Apple" wrote: >>Maybe this will help: >> >>http://impala.apache.org/docs/build/html/topics/impala_create_table.html#create_table >> >>"Although the EXTERNAL and LOCATION clauses

Re: Load Data from HDFS to Parquet

Maybe this will help: http://impala.apache.org/docs/build/html/topics/impala_create_table.html#create_table "Although the EXTERNAL and LOCATION clauses are often specified together, LOCATION is optional for external tables, and you can also specify LOCATION for internal tables. The difference is

Re: [DISCUSS] 2.10.0 release

This sounds like a good idea to me. Thank you for volunteering! On Mon, Aug 14, 2017 at 12:37 AM, Bharath Vissapragada wrote: > Folks, > > It has been almost 2 months since we released Apache Impala (incubating) > 2.9.0 and there have been new feature improvements and a good number of bug > fixes

Re: Small change to all-build-options job

Thanks, Henry! On Fri, Aug 11, 2017 at 11:08 PM, Henry Robinson wrote: > [You can probably skip this mail unless you're interested. TLDR: I slightly > changed the all-build-options job in a very minor way; let me know if you > see issues with it] > > Impala will shortly have a dependency on libkb

Making a new development environment from scratch

bin/bootstrap_development.sh now no longer references the chef repo < https://github.com/awleblang/impala-setup>. My hope is that this makes it easier to maintain and extend to new Linux distributions. It now also supports Ubuntu 16.04 and 14.04. I have tested it in EC2, Google Compute Engine, and

Re: Unable to start catalog, but with no error message?

I can no longer repro this. ¯\_(ツ)_/¯ On Sun, Jul 30, 2017 at 11:48 AM, Bharath Vissapragada wrote: > How about attaching 'strace' to the catalogd startup and see where it > crashes (if its reproducible on demand) ? May be others have better ideas. > > On Sat, Jul 29, 2017

Re: [DRAFT] Incubator PMC Board Report - August 2017

> * Podlings missing sign off, will be moved to failed to report This is new, right? I don't see it in my email archives that "will be moved to failed to report" has appeared previously.

Re: Loading tpc-ds

om org.apache.hadoop.hive.ql.exec.mr.MapRedTask > > 2017-07-31 23:55:38,641 INFO log.PerfLogger > > (PerfLogger.java:PerfLogEnd(168)) - > start=1501545305365 end=1501545338641 duration=33276 > > from=org.apache.hadoop.hive.ql.Driver> > > > > > > O

Re: Reminder: "newbie" label on tickets

seen a few new contributors pick up JIRAs with the newbie that > > sounded easy but were actually tricky to get right - that's not a great > > experience. > > > > > > > > On Sun, Jul 30, 2017 at 1:30 PM, Jim Apple wrote: > > > > > As a re

Reminder: "newbie" label on tickets

As a reminder, when you file a ticket, you can label tickets that could be completed by a first-time Impala contributor "newbie". This can be a tool to help grow the community.

Re: Unable to start catalog, but with no error message?

at line 48: LOAD_DATA_ARGS="" + cleanup + rm -rf /tmp/tmp.Yfeh8QGfi1 On Sat, Jul 29, 2017 at 12:47 AM, Jim Apple wrote: > I'm seeing https://issues.apache.org/jira/browse/IMPALA-5700 when trying > to bootstrap a new development environment on an EC2 machine with Ubuntu > 14.04,

Re: Podling Report Reminder - August 2017

Done. On Sun, Jul 23, 2017 at 6:29 PM, Jim Apple wrote: > Here is my draft report. Any comments? > > Impala is a high-performance C++ and Java SQL query engine for data stored > in > Apache Hadoop-based clusters. > > Impala has been incubating since 2015-12-03. > >

Unable to start catalog, but with no error message?

I'm seeing https://issues.apache.org/jira/browse/IMPALA-5700 when trying to bootstrap a new development environment on an EC2 machine with Ubuntu 14.04, 250GB of free disk space and over 60GB of free memory. I've seen this with and without the -so flag. I'm running the below script, which I though

Re: IMPALA-5702 - disable shared linking on jenkins?

ly on > https://jenkins.impala.io/. > > On 24 July 2017 at 17:42, Jim Apple wrote: > > > Yes, ASAN in the current 1404 job fails with something about linking. I > > haven't got around to investigating in detail. > > > > On Mon, Jul 24, 2017 at 1:39 PM, Todd Lipcon

Re: IMPALA-5702 - disable shared linking on jenkins?

at it is hard to know what is to blame if your pre-merge job fails. On Mon, Jul 24, 2017 at 5:46 PM, Henry Robinson wrote: > On 24 July 2017 at 17:43, Jim Apple wrote: > > > On Mon, Jul 24, 2017 at 5:08 PM, Henry Robinson > wrote: > > > > > On 24 July 2017 at 17:04

Re: IMPALA-5702 - disable shared linking on jenkins?

Yes, ASAN in the current 1404 job fails with something about linking. I haven't got around to investigating in detail. On Mon, Jul 24, 2017 at 1:39 PM, Todd Lipcon wrote: > Is it possible that the issue here is due to a "one definition rule" > violation? eg something like > https://github.com/go

Re: IMPALA-5702 - disable shared linking on jenkins?

On Mon, Jul 24, 2017 at 5:08 PM, Henry Robinson wrote: > On 24 July 2017 at 17:04, Jim Apple wrote: > > > I had anticipated that shared linking would save time and disk space, but > > it sounds like, from your testing, it doesn't save much time. Does it > save > &g

Re: IMPALA-5702 - disable shared linking on jenkins?

I had anticipated that shared linking would save time and disk space, but it sounds like, from your testing, it doesn't save much time. Does it save disk space? Does static linking save time when compiling incremental changes? On Mon, Jul 24, 2017 at 4:51 PM, Henry Robinson wrote: > :) I agree

Re: Podling Report Reminder - August 2017

Here is my draft report. Any comments? Impala is a high-performance C++ and Java SQL query engine for data stored in Apache Hadoop-based clusters. Impala has been incubating since 2015-12-03. Three most important issues to address in the move towards graduation: 1. Growth of the developer comm

To code is human, to review divine.

To newer Impala contributors out there: Thank you for contributing! I hope you continue contributing! To increase your understanding of Impala and make your next contribution easier, you could consider investing time in code reviews! You can watch existing reviews at http://mail-archives.apache.o

New Impala PPMC member: Michael Brown

The Podling Project Management Committee (PPMC) for Apache Impala (incubating) has invited Michael Brown to become a PPMC member and we are pleased to announce that they have accepted. Congratulations and welcome, Michael!

Re: Loading tpc-ds

I also see this with the Oracle JDK. I have also now checked I am not running out of memory. Oracle JDK7 is harder to get one's hands on, and OpenJDK7 isn't packaged by canonical for Ubuntu 16.04. On Wed, Jul 12, 2017 at 11:20 PM, Jim Apple wrote: > I'm getting data loadin

Loading tpc-ds

I'm getting data loading errors on Ubuntu 16.04 in TPC-DS. The terminal shows: ERROR : FAILED: Execution Error, return code 2 from org.apache.hadoop.hive.ql.exec.mr.MapRedTask logs/cluster/hive/hive.log shows the error below, which previous bugs have called an issue with the disk being out of spa

Re: Disabling all clang-tidy checks

wrote: > That does not, for whatever reason, actually disable clang-diagnostic-*. I > don't know why either :/ > > On 12 July 2017 at 17:15, Jim Apple wrote: > > > What about "diagnostic-henry-thinks-will-never-fire,-*,-clang-diagnosti > > c-*"? >

  1   2   3   4   5   6   7   8   9   10   >