[jira] [Updated] (IMPALA-8183) TestRPCTimeout.test_reportexecstatus_retry times out

[ https://issues.apache.org/jira/browse/IMPALA-8183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Tauber-Marshall updated IMPALA-8183: --- Fix Version/s: (was: Impala 3.3.0) Impala 3.2.0 >

[jira] [Resolved] (IMPALA-8039) Incorrect selectivity estimate for not-equals predicate

[ https://issues.apache.org/jira/browse/IMPALA-8039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers resolved IMPALA-8039. - Resolution: Duplicate > Incorrect selectivity estimate for not-equals predicate >

[jira] [Commented] (IMPALA-7993) Fix build and scripts to be more useful to developers

[ https://issues.apache.org/jira/browse/IMPALA-7993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767851#comment-16767851 ] Jim Apple commented on IMPALA-7993: --- It might be possible to fix this just in the clang-tidy-ub1604

[jira] [Commented] (IMPALA-7993) Fix build and scripts to be more useful to developers

[ https://issues.apache.org/jira/browse/IMPALA-7993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767806#comment-16767806 ] Jim Apple commented on IMPALA-7993: --- I'm confused - what's the difference between refs/for/master and

[jira] [Commented] (IMPALA-8201) How to generate erver-key.pem and server-cert.pem when executing the impala ssl test cases?

[ https://issues.apache.org/jira/browse/IMPALA-8201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767799#comment-16767799 ] Donghui Xu commented on IMPALA-8201: [~sailesh] Could you answer this question please? Thanks. >

[jira] [Created] (IMPALA-8201) How to generate erver-key.pem and server-cert.pem when executing the impala ssl test cases?

Donghui Xu created IMPALA-8201: -- Summary: How to generate erver-key.pem and server-cert.pem when executing the impala ssl test cases? Key: IMPALA-8201 URL: https://issues.apache.org/jira/browse/IMPALA-8201

[jira] [Work started] (IMPALA-8168) On S3 Sentry HDFS sync should be disabled

[ https://issues.apache.org/jira/browse/IMPALA-8168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-8168 started by Fredy Wijaya. > On S3 Sentry HDFS sync should be disabled >

[jira] [Commented] (IMPALA-7995) Run end-to-end tests against docker in minicluster

[ https://issues.apache.org/jira/browse/IMPALA-7995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767733#comment-16767733 ] Tim Armstrong commented on IMPALA-7995: --- JDBC tests pass. > Run end-to-end tests against docker

[jira] [Commented] (IMPALA-7665) Bringing up stopped statestore causes queries to fail

[ https://issues.apache.org/jira/browse/IMPALA-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767728#comment-16767728 ] Tim Armstrong commented on IMPALA-7665: --- The part I wasn't sure able is whether emulating the

[jira] [Commented] (IMPALA-8187) UDF/UDA samples should explicitly export entry points

[ https://issues.apache.org/jira/browse/IMPALA-8187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767692#comment-16767692 ] ASF subversion and git services commented on IMPALA-8187: - Commit

[jira] [Resolved] (IMPALA-8200) Builds fail using wrong branch of impala-lzo

[ https://issues.apache.org/jira/browse/IMPALA-8200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman resolved IMPALA-8200. Resolution: Fixed Fixed by force-pushing the correct change to upstream as well as

[jira] [Commented] (IMPALA-8200) Builds fail using wrong branch of impala-lzo

[ https://issues.apache.org/jira/browse/IMPALA-8200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767639#comment-16767639 ] Jim Apple commented on IMPALA-8200: --- https://github.com/cloudera/impala-lzo/pull/4#event-2137700935

[jira] [Commented] (IMPALA-8200) Builds fail using wrong branch of impala-lzo

[ https://issues.apache.org/jira/browse/IMPALA-8200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767630#comment-16767630 ] Andrew Sherman commented on IMPALA-8200: [~jbapple] (1) I hit 'enter' too soon (2) yes, that

[jira] [Created] (IMPALA-8200) Builds fail using wrong branch of impala-lzo

Andrew Sherman created IMPALA-8200: -- Summary: Builds fail using wrong branch of impala-lzo Key: IMPALA-8200 URL: https://issues.apache.org/jira/browse/IMPALA-8200 Project: IMPALA Issue

[jira] [Commented] (IMPALA-8200) Builds fail using wrong branch of impala-lzo

[ https://issues.apache.org/jira/browse/IMPALA-8200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767624#comment-16767624 ] Jim Apple commented on IMPALA-8200: --- Maybe somebody force-pushed an old version of the repo. > Builds

[jira] [Updated] (IMPALA-8200) Builds fail using wrong branch of impala-lzo

[ https://issues.apache.org/jira/browse/IMPALA-8200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman updated IMPALA-8200: --- Description: An earlier build succeeded using this commit from the branch 'master' 

[jira] [Updated] (IMPALA-8200) Builds fail using wrong branch of impala-lzo

[ https://issues.apache.org/jira/browse/IMPALA-8200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman updated IMPALA-8200: --- Description: An earlier build succeeded using this commit from the branch 'master' 

[jira] [Commented] (IMPALA-7995) Run end-to-end tests against docker in minicluster

[ https://issues.apache.org/jira/browse/IMPALA-7995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767621#comment-16767621 ] Tim Armstrong commented on IMPALA-7995: --- It turns out many of those failures are because the

[jira] [Commented] (IMPALA-8200) Builds fail using wrong branch of impala-lzo

[ https://issues.apache.org/jira/browse/IMPALA-8200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767620#comment-16767620 ] Jim Apple commented on IMPALA-8200: --- Andrew, when you file a ticket like this, can you please add to

[jira] [Created] (IMPALA-8199) stress test fails: "No module named RuntimeProfile.ttypes"

Thomas Tauber-Marshall created IMPALA-8199: -- Summary: stress test fails: "No module named RuntimeProfile.ttypes" Key: IMPALA-8199 URL: https://issues.apache.org/jira/browse/IMPALA-8199

[jira] [Created] (IMPALA-8198) Add DATE type support to Avro scanner/writer

Attila Jeges created IMPALA-8198: Summary: Add DATE type support to Avro scanner/writer Key: IMPALA-8198 URL: https://issues.apache.org/jira/browse/IMPALA-8198 Project: IMPALA Issue Type:

[jira] [Comment Edited] (IMPALA-7995) Run end-to-end tests against docker in minicluster

[ https://issues.apache.org/jira/browse/IMPALA-7995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767602#comment-16767602 ] Tim Armstrong edited comment on IMPALA-7995 at 2/13/19 9:20 PM: Here are

[jira] [Commented] (IMPALA-7995) Run end-to-end tests against docker in minicluster

[ https://issues.apache.org/jira/browse/IMPALA-7995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767602#comment-16767602 ] Tim Armstrong commented on IMPALA-7995: --- Here are the failing query_tests from a run I just did:

[jira] [Updated] (IMPALA-8198) Add DATE type support to Avro scanner/writer

[ https://issues.apache.org/jira/browse/IMPALA-8198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Jeges updated IMPALA-8198: - Description: Implement Avro DATE type support. > Add DATE type support to Avro scanner/writer >

[jira] [Commented] (IMPALA-7993) Fix build and scripts to be more useful to developers

[ https://issues.apache.org/jira/browse/IMPALA-7993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767569#comment-16767569 ] ASF subversion and git services commented on IMPALA-7993: - Commit

[jira] [Updated] (IMPALA-8194) TestPauseMonitor.test_jvm_pause_monitor_logs_entries needs to wait longer to see output

[ https://issues.apache.org/jira/browse/IMPALA-8194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman updated IMPALA-8194: --- Priority: Critical (was: Minor) > TestPauseMonitor.test_jvm_pause_monitor_logs_entries

[jira] [Updated] (IMPALA-8194) TestPauseMonitor.test_jvm_pause_monitor_logs_entries needs to wait longer to see output

[ https://issues.apache.org/jira/browse/IMPALA-8194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman updated IMPALA-8194: --- Labels: broken-build flaky-test (was: ) >

[jira] [Updated] (IMPALA-8191) TestBreakpadExhaustive.test_minidump_creation fails to kill cluster

[ https://issues.apache.org/jira/browse/IMPALA-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman updated IMPALA-8191: --- Priority: Critical (was: Major) > TestBreakpadExhaustive.test_minidump_creation fails to

[jira] [Created] (IMPALA-8197) Validate Parquet files written by Impala using Parquet-mr

Csaba Ringhofer created IMPALA-8197: --- Summary: Validate Parquet files written by Impala using Parquet-mr Key: IMPALA-8197 URL: https://issues.apache.org/jira/browse/IMPALA-8197 Project: IMPALA

[jira] [Updated] (IMPALA-8193) junitxml_prune_notrun.py fails on Centos6 passing xml_declaration=True to ElementTree

[ https://issues.apache.org/jira/browse/IMPALA-8193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman updated IMPALA-8193: --- Labels: broken-build (was: ) > junitxml_prune_notrun.py fails on Centos6 passing

[jira] [Updated] (IMPALA-8191) TestBreakpadExhaustive.test_minidump_creation fails to kill cluster

[ https://issues.apache.org/jira/browse/IMPALA-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman updated IMPALA-8191: --- Labels: broken-build flaky-test (was: ) > TestBreakpadExhaustive.test_minidump_creation

[jira] [Updated] (IMPALA-8190) Query on kudu table failed with 'Network error: recv error from 0.0.0.0:0: Transport endpoint is not connected (error 107)'

[ https://issues.apache.org/jira/browse/IMPALA-8190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman updated IMPALA-8190: --- Priority: Critical (was: Major) > Query on kudu table failed with 'Network error: recv

[jira] [Updated] (IMPALA-8189) TestParquet.test_resolution_by_name fails on S3 because 'hadoop fs -cp' fails

[ https://issues.apache.org/jira/browse/IMPALA-8189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman updated IMPALA-8189: --- Priority: Critical (was: Major) > TestParquet.test_resolution_by_name fails on S3 because

[jira] [Updated] (IMPALA-8190) Query on kudu table failed with 'Network error: recv error from 0.0.0.0:0: Transport endpoint is not connected (error 107)'

[ https://issues.apache.org/jira/browse/IMPALA-8190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman updated IMPALA-8190: --- Component/s: Backend > Query on kudu table failed with 'Network error: recv error from

[jira] [Updated] (IMPALA-8190) Query on kudu table failed with 'Network error: recv error from 0.0.0.0:0: Transport endpoint is not connected (error 107)'

[ https://issues.apache.org/jira/browse/IMPALA-8190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman updated IMPALA-8190: --- Labels: broken-build flaky-test (was: ) > Query on kudu table failed with 'Network error:

[jira] [Updated] (IMPALA-8189) TestParquet.test_resolution_by_name fails on S3 because 'hadoop fs -cp' fails

[ https://issues.apache.org/jira/browse/IMPALA-8189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman updated IMPALA-8189: --- Component/s: Backend > TestParquet.test_resolution_by_name fails on S3 because 'hadoop fs

[jira] [Updated] (IMPALA-8189) TestParquet.test_resolution_by_name fails on S3 because 'hadoop fs -cp' fails

[ https://issues.apache.org/jira/browse/IMPALA-8189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman updated IMPALA-8189: --- Labels: broken-build flaky-test (was: broken-build) > TestParquet.test_resolution_by_name

[jira] [Updated] (IMPALA-8189) TestParquet.test_resolution_by_name fails on S3 because 'hadoop fs -cp' fails

[ https://issues.apache.org/jira/browse/IMPALA-8189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman updated IMPALA-8189: --- Labels: broken-build (was: ) > TestParquet.test_resolution_by_name fails on S3 because

[jira] [Updated] (IMPALA-8178) Tests failing with “Could not allocate memory while trying to increase reservation” on EC filesystem

[ https://issues.apache.org/jira/browse/IMPALA-8178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman updated IMPALA-8178: --- Component/s: Backend > Tests failing with “Could not allocate memory while trying to

[jira] [Updated] (IMPALA-8178) Tests failing with “Could not allocate memory while trying to increase reservation” on EC filesystem

[ https://issues.apache.org/jira/browse/IMPALA-8178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman updated IMPALA-8178: --- Affects Version/s: Impala 3.2.0 > Tests failing with “Could not allocate memory while

[jira] [Assigned] (IMPALA-8178) Tests failing with “Could not allocate memory while trying to increase reservation” on EC filesystem

[ https://issues.apache.org/jira/browse/IMPALA-8178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman reassigned IMPALA-8178: -- Assignee: Tim Armstrong (was: Andrew Sherman) > Tests failing with “Could not

[jira] [Updated] (IMPALA-8178) Tests failing with “Could not allocate memory while trying to increase reservation” on EC filesystem

[ https://issues.apache.org/jira/browse/IMPALA-8178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman updated IMPALA-8178: --- Priority: Blocker (was: Major) > Tests failing with “Could not allocate memory while

[jira] [Updated] (IMPALA-8178) Tests failing with “Could not allocate memory while trying to increase reservation” on EC filesystem

[ https://issues.apache.org/jira/browse/IMPALA-8178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman updated IMPALA-8178: --- Labels: broken-build (was: ) > Tests failing with “Could not allocate memory while trying

[jira] [Updated] (IMPALA-8196) IR UDFs should not allow importing symbols with hidden visibility

[ https://issues.apache.org/jira/browse/IMPALA-8196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-8196: -- Labels: udf (was: ) > IR UDFs should not allow importing symbols with hidden visibility >

[jira] [Created] (IMPALA-8196) IR UDFs should not allow importing symbols with hidden visibility

Tim Armstrong created IMPALA-8196: - Summary: IR UDFs should not allow importing symbols with hidden visibility Key: IMPALA-8196 URL: https://issues.apache.org/jira/browse/IMPALA-8196 Project: IMPALA