[jira] [Updated] (IMPALA-11421) make idle_session_timeout no overridable in the user session

2022-07-08 Thread Adriano (Jira)
[ https://issues.apache.org/jira/browse/IMPALA-11421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano updated IMPALA-11421: - Description: hi, afaik idle_session_timeout is overridable in the user session, would be a good idea

[jira] [Updated] (IMPALA-11421) make idle_session_timeout no overridable in the user session

2022-07-08 Thread Adriano (Jira)
[ https://issues.apache.org/jira/browse/IMPALA-11421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano updated IMPALA-11421: - Description: hi, afaik idle_session_timeout are overridable in the user session, would be a good idea

[jira] [Updated] (IMPALA-11421) make idle_session_timeout no overridable in the user session

2022-07-08 Thread Adriano (Jira)
[ https://issues.apache.org/jira/browse/IMPALA-11421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano updated IMPALA-11421: - Summary: make idle_session_timeout no overridable in the user session (was: make

[jira] [Created] (IMPALA-11421) make idle_[query|session]_timeout no overridable in the user session

2022-07-08 Thread Adriano (Jira)
Adriano created IMPALA-11421: Summary: make idle_[query|session]_timeout no overridable in the user session Key: IMPALA-11421 URL: https://issues.apache.org/jira/browse/IMPALA-11421 Project: IMPALA

[jira] [Created] (IMPALA-10502) delayed 'Invalidated objects in cache' cause 'Table already exists'

2021-02-12 Thread Adriano (Jira)
Adriano created IMPALA-10502: Summary: delayed 'Invalidated objects in cache' cause 'Table already exists' Key: IMPALA-10502 URL: https://issues.apache.org/jira/browse/IMPALA-10502 Project: IMPALA

[jira] [Created] (IMPALA-10396) DECIMAL_V2=false: exception during analysis after expr substitution

2020-12-15 Thread Adriano (Jira)
Adriano created IMPALA-10396: Summary: DECIMAL_V2=false: exception during analysis after expr substitution Key: IMPALA-10396 URL: https://issues.apache.org/jira/browse/IMPALA-10396 Project: IMPALA

[jira] [Updated] (IMPALA-9055) HDFS Caching with Impala: Expiration 26687997791:19:48:13.951 exceeds the max relative expiration time of

2019-10-16 Thread Adriano (Jira)
[ https://issues.apache.org/jira/browse/IMPALA-9055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano updated IMPALA-9055: Description: HDFS Caching with Impala: If we create a pool specifying the maxTtl with the hdfs command:

[jira] [Updated] (IMPALA-9055) HDFS Caching with Impala: Expiration 26687997791:19:48:13.951 exceeds the max relative expiration time of

2019-10-16 Thread Adriano (Jira)
[ https://issues.apache.org/jira/browse/IMPALA-9055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano updated IMPALA-9055: Description: HDFS Caching with Impala: If we create a pool specifying the maxTtl with the hdfs command:

[jira] [Created] (IMPALA-9055) HDFS Caching with Impala: Expiration 26687997791:19:48:13.951 exceeds the max relative expiration time of

2019-10-16 Thread Adriano (Jira)
Adriano created IMPALA-9055: --- Summary: HDFS Caching with Impala: Expiration 26687997791:19:48:13.951 exceeds the max relative expiration time of Key: IMPALA-9055 URL: https://issues.apache.org/jira/browse/IMPALA-9055

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

2019-08-12 Thread Adriano (JIRA)
[ 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"

2019-08-12 Thread Adriano (JIRA)
[ 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"

2019-08-12 Thread Adriano (JIRA)
[ 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

2019-08-12 Thread Adriano (JIRA)
[ 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

2019-08-12 Thread Adriano (JIRA)
[ 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-:

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

2019-08-09 Thread Adriano (JIRA)
[ https://issues.apache.org/jira/browse/IMPALA-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano updated IMPALA-8852: Priority: Minor (was: Major) > The dfs.domain.socket.path can be nonexistent on coordinator only nodes >

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

2019-08-09 Thread Adriano (JIRA)
[ https://issues.apache.org/jira/browse/IMPALA-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano updated IMPALA-8852: Issue Type: Bug (was: Improvement) > The dfs.domain.socket.path can be nonexistent on coordinator only

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

2019-08-09 Thread Adriano (JIRA)
[ 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/9/19 1:22 PM: - WORKAROUND: Create

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

2019-08-09 Thread Adriano (JIRA)
[ https://issues.apache.org/jira/browse/IMPALA-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano updated IMPALA-8852: Issue Type: Improvement (was: New Feature) > The dfs.domain.socket.path can be nonexistent on

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

2019-08-09 Thread Adriano (JIRA)
[ https://issues.apache.org/jira/browse/IMPALA-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano updated IMPALA-8852: Description: On coordinator only nodes ([typically the edge

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

2019-08-09 Thread Adriano (JIRA)
[ https://issues.apache.org/jira/browse/IMPALA-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16903830#comment-16903830 ] Adriano commented on IMPALA-8852: - WORKAROUND: Create the dfs.domain.socket.path manually with the

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

2019-08-09 Thread Adriano (JIRA)
[ https://issues.apache.org/jira/browse/IMPALA-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano updated IMPALA-8852: Description: On coordinator only nodes (typically the edge nodes), the dfs.domain.socket.path (can be

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

2019-08-09 Thread Adriano (JIRA)
[ https://issues.apache.org/jira/browse/IMPALA-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano updated IMPALA-8852: Description: On coordinator only nodes (typically the edge nodes), the dfs.domain.socket.path (can be

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

2019-08-09 Thread Adriano (JIRA)
Adriano created IMPALA-8852: --- Summary: The dfs.domain.socket.path can be nonexistent on coordinator only nodes Key: IMPALA-8852 URL: https://issues.apache.org/jira/browse/IMPALA-8852 Project: IMPALA

[jira] [Commented] (IMPALA-8403) Possible thread leak in impalad

2019-08-02 Thread Adriano (JIRA)
[ https://issues.apache.org/jira/browse/IMPALA-8403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16898711#comment-16898711 ] Adriano commented on IMPALA-8403: - Thank [~kwho], yes, it will be a good improvement after IMPALA-7984

[jira] [Resolved] (IMPALA-8679) Make the query options set in the dynamic resource pool/admission control un-overridable in the user session

2019-07-29 Thread Adriano (JIRA)
[ https://issues.apache.org/jira/browse/IMPALA-8679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano resolved IMPALA-8679. - Resolution: Fixed Fix Version/s: Impala 3.1.0 IMPALA-7349 is applicable here (specifically for

[jira] [Created] (IMPALA-8679) Make the query options set in the dynamic resource pool/admission control un-overridable in the user session

2019-06-19 Thread Adriano (JIRA)
Adriano created IMPALA-8679: --- Summary: Make the query options set in the dynamic resource pool/admission control un-overridable in the user session Key: IMPALA-8679 URL:

[jira] [Commented] (IMPALA-8403) Possible thread leak in impalad

2019-05-03 Thread Adriano (JIRA)
[ https://issues.apache.org/jira/browse/IMPALA-8403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832467#comment-16832467 ] Adriano commented on IMPALA-8403: - Hi, I would like to add a repro steps [^reproIMPALA-8403.tgz] that i

[jira] [Updated] (IMPALA-8403) Possible thread leak in impalad

2019-05-03 Thread Adriano (JIRA)
[ https://issues.apache.org/jira/browse/IMPALA-8403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano updated IMPALA-8403: Attachment: reproIMPALA-8403.tgz > Possible thread leak in impalad > --- > >

[jira] [Commented] (IMPALA-8087) Evaluate to adapt the serde property values length as per the latest changes on HMS

2019-01-21 Thread Adriano (JIRA)
[ https://issues.apache.org/jira/browse/IMPALA-8087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16747796#comment-16747796 ] Adriano commented on IMPALA-8087: - [~bharathv] thanks to have a look on it. Just a question regarding:

[jira] [Created] (IMPALA-8087) Evaluate to adapt the serde property values length as per the latest changes on HMS

2019-01-15 Thread Adriano (JIRA)
Adriano created IMPALA-8087: --- Summary: Evaluate to adapt the serde property values length as per the latest changes on HMS Key: IMPALA-8087 URL: https://issues.apache.org/jira/browse/IMPALA-8087 Project:

[jira] [Commented] (IMPALA-7496) Schedule query taking in account the mem available on the impalad nodes

2018-08-29 Thread Adriano (JIRA)
[ https://issues.apache.org/jira/browse/IMPALA-7496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16596341#comment-16596341 ] Adriano commented on IMPALA-7496: - The Impala version used during the issue haven't -IMPALA-1575- The

[jira] [Created] (IMPALA-7496) Schedule query taking in account the mem available on the impalad nodes

2018-08-28 Thread Adriano (JIRA)
Adriano created IMPALA-7496: --- Summary: Schedule query taking in account the mem available on the impalad nodes Key: IMPALA-7496 URL: https://issues.apache.org/jira/browse/IMPALA-7496 Project: IMPALA

[jira] [Commented] (IMPALA-7031) Detailed failure reason for clients when a query is cancelled from the WebUi

2018-07-20 Thread Adriano (JIRA)
[ https://issues.apache.org/jira/browse/IMPALA-7031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16550510#comment-16550510 ] Adriano commented on IMPALA-7031: - Hi [~tarmstrong], sorry to answer with delay. I made some tests on

[jira] [Updated] (IMPALA-7031) Detailed failure reason for clients when a query is cancelled from the WebUi

2018-07-20 Thread Adriano (JIRA)
[ https://issues.apache.org/jira/browse/IMPALA-7031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano updated IMPALA-7031: Attachment: Screen Shot 2018-07-20 at 10.19.42.png > Detailed failure reason for clients when a query is