Re: Fw: Issues with generating testdata for Impala

I'd suggest that it will be easier to address any cluster test issues one-by-one in its own email thread or bug report, since each one may have a different cause. On Wed, Jun 8, 2016 at 5:30 AM, Valencia Serrao wrote: > Hi Casey, > > Data loading issues on ppc are resolved.

Branch model discussion

How should Impala branches be a manged? Today, most of our new development happens on trunk, except when a CDH release is imminent. I propose we move to a time-based release model, where development happens on the "master" branch and every N weeks a commit that is passing all of the tests is

Re: Branch model discussion

Thank you. I think these are good questions. > What would happen if we discover that a tagged release has a critical bug > that was missed by the test cases? Would we have a release branch to > stabilise the release with any critical fixes? I think that is the right choice. What do you think? >

"Impala" is an approved name for Impala now

https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-96 I will be working on getting the legal paperwork in order.

Re: Branch model discussion

> I > don't think we should force the project into a regular every-N-weeks > cadence without being sure that the release process can keep up. That sounds good to me. It is my understanding that the way Kudu does it is that someone generally volunteers to drive the next K releases, anticipating

Apache CWiki access

I cannot seem to edit https://cwiki.apache.org/confluence/display/IMPALA/Impala+Home My wiki username is jbapple/Jim Apple. May I have edit auth? Thanks, Jim

Re: LLVM codegen functionality

LLVM codegen has a significant (and good) effect on performance. https://blog.cloudera.com/blog/2013/02/inside-cloudera-impala-runtime-code-generation/ http://llvm.org/devmtg/2013-11/slides/Wanderman-Milne-Cloudera.pdf As for GCC/altivec problems, you might want to file a bug suggesting that

Re: Branch model discussion

ch merged back into "master". Feature branches can be merged back into "master" by a vote of the PMC. Feature branches that have lost all of their momentum can be closed by a vote of the PMC. +++++ Thoughts? On Thu, Jun 9, 2016 at 10:52 AM, Jim Apple <jba

Re: RFC: Remove thirdparty

> I think we probably need to make a firm decision about whether we're going > to try to support non-toolchain builds. In the past we've said that it would > be nice to allow building Impala with system libraries (even if we don't put > special effort into supporting it), but I don't think we've

Re: RFC: Remove thirdparty

> 5. Update integration jenkins job to copy the snapshots of the components > above to > internal jenkins repo in addition to checking them in to github. Update > bootstrap_toolchain > to point to internal repos. Which Jenkins job(s), exactly? Which internal Jenkins repo?

Re: IMPALA-3223

> > On May 25, 2016, at 2:06 PM, Dan Hecht (Code Review) >>>>> > <ger...@cloudera.org> wrote: >>>>> > >>>>> > Dan Hecht has posted comments on this change. >>>>> > >>>>> > Change subject: IMPALA-3223: Mo

Re: Project name proposal: Impala should be named "Impala"

ing the name search? > > Thanks, > Lenni > > On Fri, May 27, 2016 at 9:57 AM, Jim Apple <jbap...@cloudera.com> wrote: > >> I'm going to start the "suitable name search" next Wednesday (US >> Pacific time) if noone objects to the name "I

Re: Project name proposal: Impala should be named "Impala"

OK; done On Wed, Jun 1, 2016 at 5:39 PM, Henry Robinson <he...@cloudera.com> wrote: > Nope, that jira was as far as I got. > > >> On Jun 1, 2016, at 5:24 PM, Jim Apple <jbap...@cloudera.com> wrote: >> >> It looks like Henry already started this, in Marc

Re: Project name proposal: Impala should be named "Impala"

k the thread > you've already posted should be fine, given no one raised any discussion or > concern that it should be renamed. > > -Todd > > On Fri, May 27, 2016 at 10:49 AM, Jim Apple <jbap...@cloudera.com> wrote: > >> SGTM. Shall we leave this thread open for a few da

Re: Project name proposal: Impala should be named "Impala"

It looks like Henry already started this, in March: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-96 Henry, did you also email tradema...@apache.org? On Wed, Jun 1, 2016 at 3:37 PM, Jim Apple <jbap...@cloudera.com> wrote: > I am going to start the process of doing a suit

Re: Issues with Impala dataloading (power8 gcc4.9.3 Impala2.6)

I haven't seen this before, but data loading is sometimes troublesome. Other Impala developers, have you seen this before? This looks to me like a Hive error from our load-functional-query-exhaustive-hive-generated.sql. You might find some interesting information in

Re: Failed to start hdfs

Oh, and this is after switching to the ASF branch and then switching back On Fri, Jun 24, 2016 at 9:16 AM, Jim Apple <jbap...@cloudera.com> wrote: > I finding the following in testdata/bin/run-all.sh > > Failed to start hdfs-namenode. The end of the log > (/home/jbapple/Impal

Failed to start hdfs

I finding the following in testdata/bin/run-all.sh Failed to start hdfs-namenode. The end of the log (/home/jbapple/Impala/testdata/cluster/cdh5/node-1/var/log/hdfs-namenode.out) is: /home/jbapple/Impala/testdata/cluster/cdh5/node-1/etc/init.d/common: line 22: hdfs: command not found Has anyone

Re: Getting rid of thirdparty

Both #1 and #3 seem reasonable to me. I think #2 should be avoided because the Con you listed will, I think, make contributing to Impala difficult for new contributors, and I think that's more serious than the Cons for #1 and #3. On Thu, Mar 10, 2016 at 10:38 AM, Henry Robinson

Re: Re: About Cooperating For A Better Impala

and (b) whether any changes are sufficiently risky to justify separate branching On Thu, Mar 17, 2016 at 5:29 AM, Jim Apple <jbap...@cloudera.com> wrote: > +cc:dev@impala.incubator.apache.org > > On Wed, Mar 16, 2016 at 10:38 PM, 林言 <...@163.com> wrote: > >> We kn

Re: Re: About Cooperating For A Better Impala

adaption in Impala, would you like to > work with us in a new branch of Impala? > > > ------ > Yan Lin > > > *From:* Jim Apple <jbap...@cloudera.com> > *Date:* 2016-03-17 01:06 > *To:* Impala Dev <impala-...@cloudera.org> > *CC:

Re: Fw: Debugging Impala code

achment size was too big. So, here is the com]Nishidha > Panpaliya---04/01/2016 06:36:24 PM---Sorry, attachment size was too big. > So, here is the compressed log and backend test analysis before > > From: Nishidha Panpaliya/Austin/Contr/IBM > To: "Tim Armstrong" <tarms

Re: docker cloudera impala-dev image

[moved to apache lists] Thanks for looking into and then fixing that, Casey! On Mon, Apr 11, 2016 at 10:52 AM, Casey Ching wrote: > Sorry about the late response. > > Unfortunately due to problems with docker hub I can no longer upload the > complete image. Instead the

Re: Debugging Impala code

I believe Hive is sometimes used for data loading, though I'm not sure. I haven't debugged impala during data loading, but when I do need to debug the backend, I often do sudo gdb -p $(ps -C impalad -o pid | tail -1 | awk '{print $1}') On Thu, Mar 17, 2016 at 8:50 AM, Nishidha Panpaliya

ld internal error while linking impalad

Has anyone seen this one before? I googled around and couldn't find anyone who had a repro, but I've seen this twice today. [100%] Building CXX object be/src/service/CMakeFiles/impalad.dir/daemon-main.cc.o Linking CXX executable ../../build/debug/service/impalad

Re: Fw: Debugging Impala code

chines with at le]Tim > Armstrong ---03/21/2016 09:10:46 PM---We generally run the full test suite > on machines with at least 32GB of memory: it's pretty memory hu > > From: Tim Armstrong <tarmstr...@cloudera.com> > To: Jim Apple <jbap...@cloudera.com> > Cc: dev@impala.

Re: Impala tests and estimate

Here is a copy of part of our internal wiki on how to run tests: You can then run the front-end tests with cd fe; mvn -fae test; cd .. This can be narrowed by passing mvn arguments specifying which test class or test method you want to run, like mvn -fae test -Dtest=AnalyzeStmtsTest mvn -fae

Re: [VOTE] Apache Impala Bylaws

te: > >> +1 (non-binding) >> >> On Sun, Jul 24, 2016 at 5:41 AM, Michael Ho <k...@cloudera.com> wrote: >> >> > +1 (binding) >> > >> > On Fri, Jul 22, 2016 at 12:46 PM, Jim Apple <jbap...@cloudera.com> >> wrote: >> > >>

Re: Re： IMPALA-2428 Support multiple-character string as the field delimiter

On Mon, Jul 25, 2016 at 7:30 AM, Yuanhao Luo <luoyuan...@software.ict.ac.cn> wrote: > > Hello, Jim Apple: > I can't find any tests for case *escape character is the same value as > field delimiter* and case *escape character is the same value as tuple > delimiter *from

Re: IMPALA-2428 Support multiple-character string as the field delimiter

I may be alone in this, but I am finding the long posts, with logs of shell sessions intermixed with paragraphs of regular text, very difficult to read and understand. On Sun, Jul 24, 2016 at 7:53 PM, Yuanhao Luo <luoyuan...@software.ict.ac.cn> wrote: > Hello, Jim Apple, I have test

New instructins for devloping agains the Apache git repo

As you all know, we have now switched to using Apache git as our upstream/source-of-truth. To switch to using it as your source-of-truth: 1. Add a new git remote “apache” that tracks the ASF git repo 1. git remote add apache

Re: New instructins for devloping agains the Apache git repo

e and apply it using the ‘patch’ command. After applying it, git commit. Git push to gerrit as described below 7. Develop as you usually do. When you are ready to push to gerrit: git push --no-thin asf-gerrit HEAD:refs/for/master On Tue, Jul 26, 2016 at 2:41 PM, Jim Apple <jbap...@cloudera.com>

Re: [Important] ASF jira migration

How do I tell what my email address is in a JIRA instance? On Thu, Jul 21, 2016 at 2:01 AM, Bharath Vissapragada wrote: > Hi all, > > I'm working on the Impala jira migration from issues.cloudera.org to > issues.apache.org. To map the content correctly and attribute all

Re: Releases while incubating: looser standards

files or such) then I often see a '+1, please fix the following >> for your next release'. >> >> On Thu, Jul 21, 2016 at 2:50 PM, Jim Apple <jbap...@cloudera.com> wrote: >>> >>> Hello Impala Mentors, >>> >>> I was chatting with Sean Busbey abou

Re: Releases while incubating: looser standards

ould have happened > before a git import) and the release had a suitable disclaimer in the > release notes, I'd be fine with that as an IPMC voter. > > On Fri, Jul 22, 2016 at 11:32 AM, Jim Apple <jbap...@cloudera.com> wrote: >> Specifically, if we are still in the midst

[VOTE] Apache Impala Bylaws

This is a vote on the following proposal for bylaws: https://gerrit.cloudera.org/#/c/3669/2 The vote is to be done by "Lazy Consensus". Active PMC members, according to http://incubator.apache.org/projects/impala.html, may vote. The vote will be open 72 hours and will pass if there are "3

Re: [VOTE] Apache Impala Bylaws

>> On Fri, Jul 22, 2016 at 1:16 PM, Marcel Kornacker <mar...@cloudera.com> >> wrote: >> >> > +1 >> > >> > On Fri, Jul 22, 2016 at 12:46 PM, Jim Apple <jbap...@cloudera.com> >> wrote: >> > > This is a vote on the followi

Re: [VOTE] Apache Impala Bylaws

<mar...@cloudera.com> >> wrote: >> >> > +1 >> > >> > On Fri, Jul 22, 2016 at 12:46 PM, Jim Apple <jbap...@cloudera.com> >> wrote: >> > > This is a vote on the following proposal for bylaws: >> > > >> > >

Re: HBase errors prevent run-all-tests.sh

help to figure out if you somewhere have a spare process > hogging FDs. > > On Sun, Jul 24, 2016 at 8:09 PM Jim Apple <jbap...@cloudera.com> wrote: > >> The NN and DN logs are empty. >> >> I bin/kill-all.sh at the beginning of this, so I assume that nothing

Re: HBase errors prevent run-all-tests.sh

ara...@cloudera.com> wrote: > Do you see something in the HMaster log? From the error it looks like the > Hbase master hasn't started properly for some reason. > > On Mon, Jul 25, 2016 at 6:08 AM, Jim Apple <jbap...@cloudera.com> wrote: > >> I tried reloading the data with >

Re: HBase errors prevent run-all-tests.sh

the locations Here is some help for this command: Start disable of named table: hbase> disable 't1' hbase> disable 'ns1:t1' ERROR: Can't get master address from ZooKeeper; znode data == null On Sun, Jul 24, 2016 at 5:12 PM, Jim Apple <jbap...@cloudera.com> wrote: > I'm having

Re: HBase errors prevent run-all-tests.sh

files > > I'm guessing your hdfs instance might be overloaded (check the NN/DN logs). > HMaster is unable to connect to NN while opening regions and hence throwing > the error. > > On Mon, Jul 25, 2016 at 8:05 AM, Jim Apple <jbap...@cloudera.com> wrote: > >> Several thous

Re: Podling Report Reminder - August 2016

Mentors, committers, PPMC members, community: I am looking for your feedback on this report. My draft is below: Impala Impala is a high-performance C++ and Java SQL query engine for data stored in Apache Hadoop-based clusters. Three most important issues to address in the move towards

Re: Podling Report Reminder - August 2016

ery S3. > > On Wed, Jul 27, 2016 at 9:20 AM, Jim Apple <jbap...@cloudera.com> wrote: > >> Mentors, committers, PPMC members, community: I am looking for your >> feedback on this report. My draft is below: >> >> Impala >> >> Impala is a high-

Re: Podling Report Reminder - August 2016

eel strongly either way, but note that S3 reads and writes are > mediated by an HDFS-compatible connector, so it's still in some sense a > Hadoop-based cluster. > > On 27 July 2016 at 13:35, Tim Armstrong <tarmstr...@cloudera.com> wrote: > >> Works for me >>

Re: IMPALA-2428 Support multiple-character string as the field delimiter

+cc:luoyuan...@software.ict.ac.cn, in case they are not on the list. On Wed, Jul 13, 2016 at 6:19 PM, Jim Apple <jbap...@cloudera.com> wrote: > Can you please put your design here, rather than just telling us where > you pasted it? > > On Tue, Jul 12, 2016 at 4:33 AM, Yuan

Re: Access to the impala apache wiki

Henry, is there a way to grant all PPMC members both access to edit the wiki and access to administer the wiki, allowing any PPMC member to add new people to the wiki? On Thu, Jul 21, 2016 at 12:25 PM, Henry Robinson wrote: > Done. > > On 21 July 2016 at 11:50, Dimitris

HBase errors prevent run-all-tests.sh

I'm having trouble with my HBase environment, and it's preventing me from running bin/run-all-tests.sh. I am on Ubuntu 14.04. I have tried this with a clean build, and I have tried unset LD_LIBRARY_PATH && bin/impala-config.sh, and I have tried ./testdata/bin/run-all.sh Here is the error I get

Re: IMPALA-2428 Support multiple-character string as the field delimiter

We must be very careful about breaking changes. We may want to put this change in Impala 3.0, rather than 2.x, if it breaks existing DDL statements. > Field terminator can't be an empty string How is this different that the current restrictions on field terminators? If field terminators can

Re: Podling Report Reminder - August 2016

yes. On Fri, Jul 29, 2016 at 11:18 AM, Henry Robinson <he...@cloudera.com> wrote: > Is the final version the one you posted earlier in the thread? > > On 28 July 2016 at 10:02, Jim Apple <jbap...@cloudera.com> wrote: > >> I don't seem to have edit rights to that pag

Re: Podling Report Reminder - August 2016

The report is now available on https://wiki.apache.org/incubator/August2016 On Fri, Jul 29, 2016 at 6:31 PM, Jim Apple <jbap...@cloudera.com> wrote: > yes. > > On Fri, Jul 29, 2016 at 11:18 AM, Henry Robinson <he...@cloudera.com> wrote: >> Is the final version

Re: Choosing a Service Provider for Public Build / Test Infrastructure

Thanks for the detailed doc. > Soft / Administrative > > - Anyone employed at Cloudera working on Apache Impala (incubating) can > view or alter the jobs (promotes the idea that everyone can enhance the > jobs and theoretically helps discourage de facto sysadmins or "experts") My understanding

Re: Re: Re： IMPALA-2428 Support multiple-character string as the field delimiter

Also, you asked > I'm wondering whether have you ever test these two cases. I do not know. Can you check and report back what you find? On Tue, Aug 2, 2016 at 3:49 PM, Jim Apple <jbap...@cloudera.com> wrote: >> What's more, in this patch, we can use only standard A

Re: Re: Re： IMPALA-2428 Support multiple-character string as the field delimiter

> What's more, in this patch, we can use only standard ASCII characters(with > decimal value from 0 to 127) in ascii or octal format to set filed > terminator, but not extended ASCII characters(with decimal value from 128 to > 255) or standard ASCII characters in unicode, decimal or hexadecimal

Re: Podling Report Reminder - August 2016

bcc: dev@ Hi John, This is the third reminder we have received to dev@. The report is uploaded and one of our mentors has already signed off. Is there some other thing that needs to be done? Thanks, Jim On Tue, Aug 2, 2016 at 5:07 PM, wrote: > Dear podling, > > This

Re: [Impala-CR](cdh5-trunk) IMPALA-2979: Fix scheduling on remote hosts

For outdated changes, please use the instructions here: http://www.google.com/url?q=http%3A%2F%2Fmail-archives.apache.org%2Fmod_mbox%2Fincubator-impala-dev%2F201607.mbox%2F%253CCAC-pSX2sHyqsoxGCCKrqmQbo-jjWdP6CMGoTU_1snuQVkDVg_w%40mail.gmail.com%253E=D=1=AFQjCNFyYa3BsqALZuEvxDzgAV5l4P_evQ "For

Re: [Impala-CR](cdh5-trunk) IMPALA-2979: Fix scheduling on remote hosts

Please do not commit to the "Impala" gerrit project any more. It is stale and it will remain stale. Use "Impala-ASF" for asf and use private jenkins for private github. Public github (corresponding to public gerrit project "Impala") should be stale at the moment. Please see our branching document

New (to me) linker failures

When linking impalad I get errors like be/build/debug/util/libUtil.so: error: undefined reference to 'BZ2_bzBuffToBuffCompress' This includes with versions of Impala that I have compiled as recently as a couple of hours ago. It is now affecting all recent git hashes. The full list of libraries

Re: New (to me) linker failures

Oh, and I'm on Ubuntu 14.04. I did not upgrade any software on my machine between when this did build and when it did not build. On Thu, Aug 11, 2016 at 1:12 PM, Jim Apple <jbap...@cloudera.com> wrote: > When linking impalad I get errors like > > be/build/debug/util/libUtil.so: e

Re: New (to me) linker failures

Oh, that reminds me: I also tried bin/bootstrap_toolchain.py On Thu, Aug 11, 2016 at 1:34 PM, Matthew Jacobs <m...@cloudera.com> wrote: > Thanks. I didn't see anything wrong there (assuming the toolchain > directories exist), so I'm not sure, sorry :/ > > On Thu, Aug 11, 20

Re: New (to me) linker failures

It works if I don't pass the '-so' flag to buildall. On Thu, Aug 11, 2016 at 1:36 PM, Jim Apple <jbap...@cloudera.com> wrote: > Oh, that reminds me: I also tried bin/bootstrap_toolchain.py > > On Thu, Aug 11, 2016 at 1:34 PM, Matthew Jacobs <m...@cloudera.com> wrote: &g

Re: New (to me) linker failures

> Just to be clear: did clear your cmake files _after_ resetting and > resourcing the environment variables? yes > > What's your LD_LIBRARY_PATH and IMPALA_TOOLCHAIN ? (Maybe just post > the output of env.) Attached. XDG_VTNR=7 IMPALA_CYRUS_SASL_VERSION=2.1.23 IMPALA_AVRO_VERSION=1.7.4-p4

Re: IMPALA-2428 Support multiple-character string as the field delimiter

field terminator. > > Escape character can't be the first byte of field terminator. > > Terminators can't not contain '\0' for text file. > > As suggested by Jim Apple, I start this discussion in mailing list to do a > design review. > Are there any problems in my design?

Re: Upstream switch from github to ASF git

> On Wed, Jul 20, 2016 at 11:54 AM, Jim Apple <jbap...@cloudera.com> wrote: > >> Today, Impala's official source is at >> https://github.com/cloudera/Impala/. As of Monday, July 25, it will be >> at >> https://git-wip-us.apache.org/repos/asf?p=incubator-impala.g

Upstream switch from github to ASF git

Today, Impala's official source is at https://github.com/cloudera/Impala/. As of Monday, July 25, it will be at https://git-wip-us.apache.org/repos/asf?p=incubator-impala.git. Unfortunately, for all of your in-progress patches in gerrit, you will either have to (a) Abandon them and reprocue them

Re: Location of developers documentation

ocs, which facilitate >>> commenting, and it would be good to keep it that way. >>> >>> Should we link to those docs from the Apache Impala wiki? >>> >>> On Wed, Jul 20, 2016 at 9:06 AM, Tim Armstrong <tarmstr...@cloudera.com> >>> wrote:

Re: Location of developers documentation

is really for documents where we expect a good amount of > discussion. Design docs and proposals are certainly in that category. > > Is there anything in that category that you would like to exclude? > > On Wed, Jul 20, 2016 at 3:35 PM, Jim Apple <jbap...@cloudera.com> wro

Re: Location of developers documentation

just a minor update to make. On Wed, Jul 20, 2016 at 3:35 PM, Jim Apple <jbap...@cloudera.com> wrote: > I think that's overkill. There are few documents that don't need > comments (I really tried to come up with one. Something written in > Linear A?) > > I also don't think G

Re: Location of developers documentation

loudera.com> wrote: >> >>> I meant this really for documents where we expect a good amount of >>> discussion. Design docs and proposals are certainly in that category. >>> >>> Is there anything in that category that you would like to exclude? >>> >

Apache Impala Bylaws

Please review, comment, and vote: https://gerrit.cloudera.org/#/c/3669/ I have written a draft of some bylaws for Apache Impala. They are mostly copied from Hadoop's bylaws, https://hadoop.apache.org/bylaws.html A number of the issues addressed in the bylaws are items that must be addressed

Re: Apache Impala Bylaws

Thank you for the advice. As Todd suggests, I'll let the gerrit review quiesce, then call for a "VOTE" on this list, dev@. On Mon, Jul 18, 2016 at 4:52 PM, Todd Lipcon <t...@cloudera.com> wrote: > On Mon, Jul 18, 2016 at 1:46 PM, Jim Apple <jbap...@cloudera.com>

Re: Apache Impala Bylaws

e usually 72 hours at the ASF, so you may > want to use that. Hadoop adopted 7 days long ago, but it doesn't > really gain much apart from extra waiting. > > Tom > > On Tue, Jul 19, 2016 at 12:52 AM, Todd Lipcon <t...@cloudera.com> wrote: >> On Mon, Jul 18, 2016 at

Re: Location of developers documentation

I think Tom's points are correct. Another option would be plain text or markdown files inside the git repo. Those would be harder to update, but then would have review for developer docs changes, which might be nice. FWIW, right now getting a wiki login requires asking for one on this mailing

Re: Discussion about IMPALA-889: Add support for ISO-SQL trim()

My feeling is that Impala should implement the standard, including the additional syntax. On Thu, Jul 7, 2016 at 5:56 PM, Wang, Youwei A wrote: > Greetings everyone. > I am working on the JIRA IMPALA-889: Add support for ISO-SQL trim(). > Corresponding JIRA link:

Re: Special case for partition DDL related predicates regarding to NULL partition.

Let me try to explain what is going on here. Currently, if a user wants to specify a null partition for a DDL operation, they write something like compute incremental stats incremental_null_part_key partition(p = NULL); For an empty string, they could write: alter table t_part drop partition

Re: Special case for partition DDL related predicates regarding to NULL partition.

lt;mar...@cloudera.com> wrote: > On Wed, Jul 6, 2016 at 10:20 AM, Jim Apple <jbap...@cloudera.com> wrote: >> Let me try to explain what is going on here. >> >> Currently, if a user wants to specify a null partition for a DDL >> operation, they write something like &

Re: HBase errors prevent run-all-tests.sh

/MasterProcWALs/state-3172.log, block=BP-1490185442-127.0.0.1-1456935654337:blk_1073764629_23805): error creating ShortCircuitReplica. java.io.IOException: Illegal seek On Mon, Jul 25, 2016 at 6:31 AM, Jim Apple <jbap...@cloudera.com> wrote: > The NN and DNs have 600-800 f

Re: HBase errors prevent run-all-tests.sh

I added the following lines to my /etc/security/limits.conf, then restarted: * hardnofile 1048576 * softnofile 1048576 That seems to have fixed the problem. On Fri, Aug 5, 2016 at 1:10 PM, Jim Apple <jbap...@cloudera.com> wrot

Re: Re: Re： IMPALA-2428 Support multiple-character string as the field delimiter

.cn> wrote: > > Hello, Jim Apple. > > For now in my commit, field terminators can not be set to extended ASCIII > characters. > After using statement "create table text_thorn_ecirc_newline(col1 string, > col2 string, col3 int, col4 int) row format delimited fields ter

[DISCUSS] Criteria for becoming a committer

I'd like to make a wiki page on what the criteria are for becoming an official Impala committer. Before doing so, I thought we could talk about what should go in that page. I went to a talk by some experienced ASF people on other projects (Spark, Hadoop, etc.) who said: 1. Every committer should

Re: [DISCUSS] Criteria for becoming a committer

lid history of >> docs contributions and ability to work with the review process. >> >> Outside of that, we could also look at history of contributing to project >> discussions and giving constructive feedback on JIRAs, code reviews, and >> other project decision-mak

Re: [DISCUSS] Criteria for becoming a committer

IMO we don't want to restrict committership to this subset of > people. > > On Mon, Aug 8, 2016 at 10:49 AM, Jim Apple <jbap...@cloudera.com> wrote: > >> Does anyone have thoughts about how, exactly, to evaluate non-code >> contributions? >> >> Wha

Re: Apache Impala Bylaws

a lazy PPMC majority, "3 binding +1 votes and more binding +1 votes than -1 votes". Your vote is binding if you are on the PPMC, http://incubator.apache.org/projects/impala.html On Tue, Jul 19, 2016 at 5:38 AM, Jim Apple <jbap...@cloudera.com> wrote: > Thank you for the advice. I

Re: Upstream switch from github to ASF git

. Once we have all the details completely ironed out, I will send out a new list of instructions. On Wed, Jul 20, 2016 at 12:14 PM, Jim Apple <jbap...@cloudera.com> wrote: > We have got to fix the second one, since gerrit is what our "First > Steps" document said to name the

Re: Code formatting with clang-format

Oh, and I should note that this file, right now, only handles C++. clang-format also works with Java, but that's future research. On Tue, Aug 16, 2016 at 10:09 AM, Jim Apple <jbap...@cloudera.com> wrote: > I support incremental reformat, not bulk reformat. > > I think we shoul

Re: New (to me) linker failures

David Knupp and Tim Armstrong saw this, too: https://issues.cloudera.org/browse/IMPALA-3979 On Thu, Aug 11, 2016 at 2:08 PM, Jim Apple <jbap...@cloudera.com> wrote: > It works if I don't pass the '-so' flag to buildall. > > On Thu, Aug 11, 2016 at 1:36 PM, Jim Apple <jbap...@c

Re: Contributions to Cloudera Impala

> I'm glad to tell you that we are able to build and test Impala on Ubuntu > linux ppc64le with the great support from the Cloudera Community. Excellent! > Our next action is to upstream all our changes to Cloudera Impala. Great! Cloudera has donated Impala to the Apache Software Foundation

Re: Python string formatting

that nothing else will. That leaves the risk > that a change made by autopep8 disables a test so we don't notice the > breakage. Other than manually reviewing the code I don't have an idea how > to prevent that. > > Thoughts? > > On Tue, Jan 31, 2017 at 8:29 PM, Jim Apple <jbap...@cloud

Gerrit down for an hour Wednesday

Hello Impala developers, >From 7pm to 8pm California time on Wednesday, gerrit.cloudera.org will be down for maintenance.

Re: Podling Report Reminder - February 2017

..@gmail.com> wrote: > >> +1 >> >> >> On Wed, Jan 25, 2017 at 9:31 PM, Brock Noland <br...@phdata.io> wrote: >> >>> +1 >>> >>> On Wed, Jan 25, 2017 at 11:08 PM, Jim Apple <jbap...@cloudera.com> wrote: >>> > Dear dev@ a

Re: Standards for committers and PPMC members

> Would it help to have examples of candidates L, M, N, O, and P who focus on >> testing tools and infrastructure? > > Yes. > > On Wed, Jan 11, 2017 at 1:50 PM, Jim Apple <jbap...@cloudera.com> wrote: >> Do you have any thoughts about what specific type or format of &g

Re: [GitHub] incubator-impala pull request #1: Branch 2.8.0

Have you reached out to the author with suggestions for how to contribute > their patch? Looks like a patch we might want to consider. > > On 31 January 2017 at 09:34, Jim Apple <jbap...@cloudera.com> wrote: > > After replying, I asked on http://infra.chat about how to

Re: [GitHub] incubator-impala pull request #1: Branch 2.8.0

After replying, I asked on http://infra.chat about how to close this. The right answer is apparently to ask in infra.chat or file an Apache infra ticket. On Tue, Jan 31, 2017 at 9:33 AM, Humbedooh wrote: > Github user Humbedooh closed the pull request at: > >

Re: Python string formatting

Will you use autopep8? If so, how will you check that it doesn't break something on an infrequently-used codepath? On Tue, Jan 31, 2017 at 11:12 AM, Michael Brown wrote: > I agree. > > On Tue, Jan 31, 2017 at 10:44 AM, Lars Volker wrote: >> Thanks for the

Re: Could a committer...

done On Mon, Feb 6, 2017 at 8:05 AM, Thomas Tauber-Marshall wrote: > carry forward the +2 and submit a gvm: > https://gerrit.cloudera.org/#/c/5389/ > > Thanks, > Thomas

Restarting jenkins.impala.io

No jobs are running

Restarting Jenkins now

Jenkins upgrade needed, so Lars and I are restarting Jenkins now. No jobs are running at the moment.

[ANNOUNCE] Apache Impala (incubating) 2.8.0 release

The Apache Impala (incubating) team is pleased to announce the release of Impala 2.8.0. Impala is a high-performance C++ and Java SQL query engine for data stored in Apache Hadoop-based clusters. The release is available at: https://impala.incubator.apache.org/downloads.html Thanks, The Apache

Tweet about 2.8.0 release?

2.8.0 was just released. Can someone tweet it from ?

Re: Standards for committers and PPMC members

t;t...@cloudera.com> wrote: > On Fri, Jan 6, 2017 at 8:53 AM, Jim Apple <jbap...@cloudera.com> wrote: > >> My feeling is similar to Tim's: >> >> It's the PPMC's responsibility, but a contributor is welcome to plead >> their case, ask for a mentor, and so on

  1   2   3   4   5   6   7   8   9   10   >