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

On Fri, Jan 12, 2018 at 4:04 PM, Jim Apple wrote: > This makes sense to me. > > In this mode, for 2.x-only changes and for changes on 3.0 that don't > apply cleanly, there will be a manual way to do the step labelled "1. > Cherrypick tool", and that way is the same way we

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

This makes sense to me. In this mode, for 2.x-only changes and for changes on 3.0 that don't apply cleanly, there will be a manual way to do the step labelled "1. Cherrypick tool", and that way is the same way we send patches for review now, but pushing to HEAD:refs/for/2.x rather than

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

Often, this list seems to filter out images. Could you post it and send a link? Thanks for taking this on, Phil! On Fri, Jan 12, 2018 at 3:15 PM, Philip Zeyliger wrote: > I think most patches go to Gerrit branch 'master', which happens to > identify itself as 3.0. (Or

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

Which gerrit branch were you thinking most patches would go to? If they go to 3.0, then push_to_asf.py would have to be amended to push to gerrit, bypassing code review. I think that's possible, but I'm not 100%. There is also security to think about, since the push_to_asf.py users can push a

Re: Accumulo Integration [SEC=UNOFFICIAL]

https://www.quora.com/How-do-we-compare-Apache-HBase-vs-Apache-Accumulo HBase and Accumulo are both implementations of BigTable using HDFS as their storage mechanism.They are virtually identical in most regards from both an operational and architectual standpoint; they have different APIs,

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

Hi! > Should we start tagging all candidates with a common label, e.g. include-in-v3? I agree with Lars's suggestion for tagging JIRAs with include-in-v3. I've done so, and the relevant query is https://issues.apache.org/jira/issues/?jql=labels%20%3D%20include-in-v3%20and%20project%3Dimpala . >

Re: .test file format

It is possible to get the test infra to generate .test files based on the actual output. For planner tests, they automatically get written to logs/fe_tests/PlannerTest/. If you're running end-to-end tests with impala-py.test, you can use the --update_results flag to get it to generate similar

Re: .test file format

.test files are written by hand, with the exception of long complex input, which I'm sure authors copy-paste from Impala shell sometimes. The formats are described in https://github.com/apache/impala/blob/master/fe/src/test/java/org/apache/impala/testutil/TestFileParser.java and

Re: Accumulo Integration [SEC=UNOFFICIAL]

I don't know that Impala can scan Accumulo tables. Assuming it can't: Impala can read HBase tables, so that might be a good place for you to start looking on what this could look like. I suspect the most complex piece is going to be the auth integration. On Thu, Jan 11, 2018 at 7:16 PM, Dickson,

.test file format

Hi, Is there a link for how to generate the .test files and what is each part in it? Thanks! Xinran