[jira] [Created] (IMPALA-8859) test_shell_commandline.test_global_config_file fails in remote cluster test

Tim Armstrong created IMPALA-8859: - Summary: test_shell_commandline.test_global_config_file fails in remote cluster test Key: IMPALA-8859 URL: https://issues.apache.org/jira/browse/IMPALA-8859

[jira] [Commented] (IMPALA-8766) Change hadoop cloud dependencies to use hadoop-cloud-storage

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

[jira] [Commented] (IMPALA-8766) Change hadoop cloud dependencies to use hadoop-cloud-storage

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

[jira] [Commented] (IMPALA-8791) Handle the case where there is no fragment scheduled on the coordinator for a query

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

[jira] [Assigned] (IMPALA-8790) IllegalStateException: Illegal reference to non-materialized slot

[ https://issues.apache.org/jira/browse/IMPALA-8790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quanlong Huang reassigned IMPALA-8790: -- Assignee: Quanlong Huang > IllegalStateException: Illegal reference to

[jira] [Reopened] (IMPALA-8791) Handle the case where there is no fragment scheduled on the coordinator for a query

[ https://issues.apache.org/jira/browse/IMPALA-8791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reopened IMPALA-8791: --- > Handle the case where there is no fragment scheduled on the coordinator for a > query >

[jira] [Updated] (IMPALA-8791) Handle the case where there is no fragment scheduled on the coordinator for a query

[ https://issues.apache.org/jira/browse/IMPALA-8791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-8791: -- Fix Version/s: (was: Impala 3.3.0) > Handle the case where there is no fragment scheduled

[jira] [Commented] (IMPALA-8791) Handle the case where there is no fragment scheduled on the coordinator for a query

[ https://issues.apache.org/jira/browse/IMPALA-8791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905709#comment-16905709 ] Tim Armstrong commented on IMPALA-8791: --- This hit a DCHECK during data loading: {noformat} F0812

[jira] [Created] (IMPALA-8857) test_kudu_col_not_null_changed may fail because client reads older timestamp

Tim Armstrong created IMPALA-8857: - Summary: test_kudu_col_not_null_changed may fail because client reads older timestamp Key: IMPALA-8857 URL: https://issues.apache.org/jira/browse/IMPALA-8857

[jira] [Created] (IMPALA-8856) TestKuduHMSIntegration.test_drop_managed_kudu_table failed with "the table does not exist"

s.log.INFO.20190812-144934.5595, hive-metastore.log, impalad.impala-ec2-centos74-m5-4xlarge-ondemand-1188.vpc.cloudera.com.jenkins.log.INFO.20190812-144935.5670, impalad.impala-ec2-centos74-m5-4xlarge-ondemand-1188.vpc.cloudera.com.jenkins.log.INFO.20190812-144935.5675, impalad.impala-ec2-c

[jira] [Resolved] (IMPALA-8791) Handle the case where there is no fragment scheduled on the coordinator for a query

[ https://issues.apache.org/jira/browse/IMPALA-8791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig resolved IMPALA-8791. Resolution: Fixed Fix Version/s: Impala 3.3.0 > Handle the case where there is no

[jira] [Commented] (IMPALA-8791) Handle the case where there is no fragment scheduled on the coordinator for a query

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

[jira] [Commented] (IMPALA-8712) Convert ExecQueryFInstance() RPC to become asynchronous

[ https://issues.apache.org/jira/browse/IMPALA-8712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905619#comment-16905619 ] Michael Ho commented on IMPALA-8712: Please also see

[jira] [Commented] (IMPALA-8847) Add partition events may contain empty partition object list

[ https://issues.apache.org/jira/browse/IMPALA-8847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905611#comment-16905611 ] Vihang Karajgaonkar commented on IMPALA-8847: - Patch is in review. > Add partition events

[jira] [Commented] (IMPALA-8845) Close ExecNode tree prior to calling FlushFinal in FragmentInstanceState

[ https://issues.apache.org/jira/browse/IMPALA-8845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905607#comment-16905607 ] Tim Armstrong commented on IMPALA-8845: --- Yeah, I think the issue in IMPALA-3990 should be

[jira] [Commented] (IMPALA-8845) Close ExecNode tree prior to calling FlushFinal in FragmentInstanceState

[ https://issues.apache.org/jira/browse/IMPALA-8845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905597#comment-16905597 ] Michael Ho commented on IMPALA-8845: Oops.. looks like Sahil already updated the JIRA with the same

[jira] [Comment Edited] (IMPALA-8845) Close ExecNode tree prior to calling FlushFinal in FragmentInstanceState

[ https://issues.apache.org/jira/browse/IMPALA-8845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905594#comment-16905594 ] Michael Ho edited comment on IMPALA-8845 at 8/12/19 9:31 PM: - {quote} I

[jira] [Commented] (IMPALA-8845) Close ExecNode tree prior to calling FlushFinal in FragmentInstanceState

[ https://issues.apache.org/jira/browse/IMPALA-8845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905594#comment-16905594 ] Michael Ho commented on IMPALA-8845: {quote} I haven't traced the issue exactly, but what I think is

[jira] [Commented] (IMPALA-8845) Close ExecNode tree prior to calling FlushFinal in FragmentInstanceState

[ https://issues.apache.org/jira/browse/IMPALA-8845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905578#comment-16905578 ] Sahil Takiar commented on IMPALA-8845: -- IMPALA-6984 looks like it might be relevant as well. >

[jira] [Created] (IMPALA-8855) Impala docs do not mention all places VALUES clause can be used

Tim Armstrong created IMPALA-8855: - Summary: Impala docs do not mention all places VALUES clause can be used Key: IMPALA-8855 URL: https://issues.apache.org/jira/browse/IMPALA-8855 Project: IMPALA

[jira] [Commented] (IMPALA-8845) Close ExecNode tree prior to calling FlushFinal in FragmentInstanceState

[ https://issues.apache.org/jira/browse/IMPALA-8845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905564#comment-16905564 ] Sahil Takiar commented on IMPALA-8845: -- As far as I can tell, the issue described in IMPALA-3990 is

[jira] [Closed] (IMPALA-7374) Impala Doc: Doc DATE type

[ https://issues.apache.org/jira/browse/IMPALA-7374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7374. --- Resolution: Fixed Fix Version/s: Impala 3.3.0 > Impala Doc: Doc DATE type >

[jira] [Closed] (IMPALA-8429) Update docs to reflect default join distribution mode change

[ https://issues.apache.org/jira/browse/IMPALA-8429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-8429. --- > Update docs to reflect default join distribution mode change >

[jira] [Resolved] (IMPALA-8429) Update docs to reflect default join distribution mode change

[ https://issues.apache.org/jira/browse/IMPALA-8429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balazs Jeszenszky resolved IMPALA-8429. --- Resolution: Invalid > Update docs to reflect default join distribution mode change

[jira] [Commented] (IMPALA-8429) Update docs to reflect default join distribution mode change

[ https://issues.apache.org/jira/browse/IMPALA-8429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905518#comment-16905518 ] Balazs Jeszenszky commented on IMPALA-8429: --- Sorry for the delay. This took me a while to

[jira] [Commented] (IMPALA-8845) Close ExecNode tree prior to calling FlushFinal in FragmentInstanceState

[ https://issues.apache.org/jira/browse/IMPALA-8845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905493#comment-16905493 ] Sahil Takiar commented on IMPALA-8845: -- CC: [~kwho] Still trying to understand the code here, but

[jira] [Commented] (IMPALA-7374) Impala Doc: Doc DATE type

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

[jira] [Commented] (IMPALA-8837) Impala Doc: Document impersonalization via HTTP and Knox authentication

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

[jira] [Commented] (IMPALA-8846) Undefined behaviour in RleEncoder::Put

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

[jira] [Closed] (IMPALA-8837) Impala Doc: Document impersonalization via HTTP and Knox authentication

[ https://issues.apache.org/jira/browse/IMPALA-8837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-8837. --- Resolution: Fixed Fix Version/s: Impala 3.3.0 > Impala Doc: Document impersonalization via

[jira] [Commented] (IMPALA-8847) Add partition events may contain empty partition object list

[ https://issues.apache.org/jira/browse/IMPALA-8847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905448#comment-16905448 ] Vihang Karajgaonkar commented on IMPALA-8847: - I created a HIVE jira since I believe this

[jira] [Commented] (IMPALA-8845) Close ExecNode tree prior to calling FlushFinal in FragmentInstanceState

[ https://issues.apache.org/jira/browse/IMPALA-8845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905370#comment-16905370 ] Tim Armstrong commented on IMPALA-8845: --- I remember I had some concerns about doing an early close

[jira] [Commented] (IMPALA-8852) ImpalaD fail to start on a non-datanode with "Invalid short-circuit reads configuration"

[ https://issues.apache.org/jira/browse/IMPALA-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905346#comment-16905346 ] Adriano commented on IMPALA-8852: - [~lv] agree, considering we have a solution adding the CM properties.

[jira] [Comment Edited] (IMPALA-8852) ImpalaD fail to start on a non-datanode with "Invalid short-circuit reads configuration"

[ https://issues.apache.org/jira/browse/IMPALA-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16903830#comment-16903830 ] Adriano edited comment on IMPALA-8852 at 8/12/19 4:19 PM: -- WORKAROUND -1-:

[jira] [Updated] (IMPALA-8852) ImpalaD fail to start on a non-datanode with "Invalid short-circuit reads configuration"

[ https://issues.apache.org/jira/browse/IMPALA-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Volker updated IMPALA-8852: Affects Version/s: Impala 3.3.0 > ImpalaD fail to start on a non-datanode with "Invalid

[jira] [Updated] (IMPALA-8852) ImpalaD fail to start on a non-datanode with "Invalid short-circuit reads configuration"

[ https://issues.apache.org/jira/browse/IMPALA-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Volker updated IMPALA-8852: Priority: Major (was: Minor) > ImpalaD fail to start on a non-datanode with "Invalid

[jira] [Commented] (IMPALA-8852) ImpalaD fail to start on a non-datanode with "Invalid short-circuit reads configuration"

[ https://issues.apache.org/jira/browse/IMPALA-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905325#comment-16905325 ] Lars Volker commented on IMPALA-8852: - Thanks for filing this issue. As a permanent solution we

[jira] [Updated] (IMPALA-8852) ImpalaD fail to start on a non-datanode with "Invalid short-circuit reads configuration"

[ https://issues.apache.org/jira/browse/IMPALA-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Volker updated IMPALA-8852: Labels: ramp-up (was: ) > ImpalaD fail to start on a non-datanode with "Invalid short-circuit

[jira] [Updated] (IMPALA-8854) test_acid_insert is failing with "Processor has no capabilities"

[ https://issues.apache.org/jira/browse/IMPALA-8854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-8854: -- Labels: broken-build (was: ) > test_acid_insert is failing with "Processor has no

[jira] [Created] (IMPALA-8854) test_acid_insert is failing with "Processor has no capabilities"

Tim Armstrong created IMPALA-8854: - Summary: test_acid_insert is failing with "Processor has no capabilities" Key: IMPALA-8854 URL: https://issues.apache.org/jira/browse/IMPALA-8854 Project: IMPALA

[jira] [Resolved] (IMPALA-8850) TmpFileMgrTest.TestDirectoryLimitParsing failed in asf-master build with error "Value of: dirs3.size() Actual: 3 Expected: 4"

[ https://issues.apache.org/jira/browse/IMPALA-8850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-8850. --- Resolution: Fixed Fix Version/s: Impala 3.3.0 >

[jira] [Resolved] (IMPALA-8848) Cardinality of UnionNode does not handle missing input cardinality correctly

[ https://issues.apache.org/jira/browse/IMPALA-8848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-8848. --- Resolution: Fixed Fix Version/s: Impala 3.3.0 > Cardinality of UnionNode does not

[jira] [Commented] (IMPALA-2426) COMPUTE INCREMENTAL STATS doesn't compute stats for newly discovered partitions

[ https://issues.apache.org/jira/browse/IMPALA-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905305#comment-16905305 ] Tamas Mate commented on IMPALA-2426: The {{loadTableMetadata}} is parameterized with {{null}} where

[jira] [Commented] (IMPALA-2426) COMPUTE INCREMENTAL STATS doesn't compute stats for newly discovered partitions

[ https://issues.apache.org/jira/browse/IMPALA-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905295#comment-16905295 ] Tamas Mate commented on IMPALA-2426: An alter table {{UPDATE_STATS}} is being called to persist the

[jira] [Updated] (IMPALA-8852) ImpalaD fail to start on a non-datanode with "Invalid short-circuit reads configuration"

[ https://issues.apache.org/jira/browse/IMPALA-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano updated IMPALA-8852: Summary: ImpalaD fail to start on a non-datanode with "Invalid short-circuit reads configuration" (was:

[jira] [Comment Edited] (IMPALA-8852) The dfs.domain.socket.path can be nonexistent on coordinator only nodes

[ https://issues.apache.org/jira/browse/IMPALA-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16903830#comment-16903830 ] Adriano edited comment on IMPALA-8852 at 8/12/19 8:33 AM: -- WORKAROUND -1-:

[jira] [Comment Edited] (IMPALA-8852) The dfs.domain.socket.path can be nonexistent on coordinator only nodes

[ https://issues.apache.org/jira/browse/IMPALA-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16903830#comment-16903830 ] Adriano edited comment on IMPALA-8852 at 8/12/19 8:31 AM: -- WORKAROUND -1-: