[jira] [Created] (IMPALA-7309) Prevent the addition of Avro schemas to non-Avro tables with incompatible schema

Todd Lipcon created IMPALA-7309: --- Summary: Prevent the addition of Avro schemas to non-Avro tables with incompatible schema Key: IMPALA-7309 URL: https://issues.apache.org/jira/browse/IMPALA-7309

[jira] [Created] (IMPALA-7308) Support Avro tables in LocalCatalog

Todd Lipcon created IMPALA-7308: --- Summary: Support Avro tables in LocalCatalog Key: IMPALA-7308 URL: https://issues.apache.org/jira/browse/IMPALA-7308 Project: IMPALA Issue Type: Sub-task

[jira] [Assigned] (IMPALA-7308) Support Avro tables in LocalCatalog

[ https://issues.apache.org/jira/browse/IMPALA-7308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon reassigned IMPALA-7308: --- Assignee: Todd Lipcon > Support Avro tables in LocalCatalog >

[jira] [Work started] (IMPALA-7132) run_clang_tidy.sh produces unrelated output

[ https://issues.apache.org/jira/browse/IMPALA-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-7132 started by Joe McDonnell. - > run_clang_tidy.sh produces unrelated output >

[jira] [Work started] (IMPALA-7238) test_kudu.TestCreateExternalTable sees unique database already exists

[ https://issues.apache.org/jira/browse/IMPALA-7238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-7238 started by Joe McDonnell. - > test_kudu.TestCreateExternalTable sees unique database already exists >

[jira] [Work started] (IMPALA-7199) Need to have scripts to generate coverage

[ https://issues.apache.org/jira/browse/IMPALA-7199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-7199 started by Joe McDonnell. - > Need to have scripts to generate coverage >

[jira] [Created] (IMPALA-7307) Support TABLESAMPLE and stats extrapolation in LocalCatalog

Todd Lipcon created IMPALA-7307: --- Summary: Support TABLESAMPLE and stats extrapolation in LocalCatalog Key: IMPALA-7307 URL: https://issues.apache.org/jira/browse/IMPALA-7307 Project: IMPALA

[jira] [Commented] (IMPALA-7298) Don't pass resolved IP address as hostname when creating proxy

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

[jira] [Commented] (IMPALA-7299) Impala fails to work with the krb5 config 'rdns=false' in Impala 2.12.0/3.0

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

[jira] [Comment Edited] (IMPALA-6994) Avoid reloading a table's HMS data for file-only operations

[ https://issues.apache.org/jira/browse/IMPALA-6994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545825#comment-16545825 ] Pranay Singh edited comment on IMPALA-6994 at 7/16/18 10:46 PM: Here is

[jira] [Commented] (IMPALA-6994) Avoid reloading a table's HMS data for file-only operations

[ https://issues.apache.org/jira/browse/IMPALA-6994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545825#comment-16545825 ] Pranay Singh commented on IMPALA-6994: -- Here is a description of the problem which this jira aims

[jira] [Commented] (IMPALA-7252) Backport rate limiting of fadvise calls into toolchain glog

[ https://issues.apache.org/jira/browse/IMPALA-7252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545801#comment-16545801 ] Bikramjeet Vig commented on IMPALA-7252: [~tlipcon] I see a commit to native-toolchain repo, is

[jira] [Work started] (IMPALA-7096) Ensure no memory limit exceeded regressions from IMPALA-4835 because of non-reserved memory

[ https://issues.apache.org/jira/browse/IMPALA-7096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-7096 started by Tim Armstrong. - > Ensure no memory limit exceeded regressions from IMPALA-4835 because of >

[jira] [Updated] (IMPALA-7305) membership entry for failed impalad gets stuck in statestore due to race between failure detection and update processing

[ https://issues.apache.org/jira/browse/IMPALA-7305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7305: -- Priority: Critical (was: Major) > membership entry for failed impalad gets stuck in

[jira] [Commented] (IMPALA-7305) membership entry for failed impalad gets stuck in statestore due to race between failure detection and update processing

[ https://issues.apache.org/jira/browse/IMPALA-7305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545764#comment-16545764 ] Tim Armstrong commented on IMPALA-7305: --- Note that the only workaround is to restart the

[jira] [Created] (IMPALA-7306) Add regression test for IMPALA-7305

Tim Armstrong created IMPALA-7306: - Summary: Add regression test for IMPALA-7305 Key: IMPALA-7306 URL: https://issues.apache.org/jira/browse/IMPALA-7306 Project: IMPALA Issue Type: Bug

[jira] [Resolved] (IMPALA-7305) membership entry for failed impalad gets stuck in statestore due to race between failure detection and update processing

[ https://issues.apache.org/jira/browse/IMPALA-7305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-7305. --- Resolution: Fixed Fixed by this commit, specifically the below part: {code} - Topic*

[jira] [Updated] (IMPALA-7305) membership entry for failed impalad gets stuck in statestore due to race between failure detection and update processing

[ https://issues.apache.org/jira/browse/IMPALA-7305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7305: -- Fix Version/s: Impala 2.12.0 Impala 3.1.0 > membership entry for failed

[jira] [Created] (IMPALA-7305) membership entry for failed impalad gets stuck in statestore due to race between failure detection and update processing

Tim Armstrong created IMPALA-7305: - Summary: membership entry for failed impalad gets stuck in statestore due to race between failure detection and update processing Key: IMPALA-7305 URL:

[jira] [Resolved] (IMPALA-6086) Use of permanent function should require SELECT privilege on DB

[ https://issues.apache.org/jira/browse/IMPALA-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoram Thanga resolved IMPALA-6086. -- Resolution: Fixed Fix Version/s: Impala 3.1.0 > Use of permanent function should

[jira] [Commented] (IMPALA-7299) Impala fails to work with the krb5 config 'rdns=false' in Impala 2.12.0/3.0

[ https://issues.apache.org/jira/browse/IMPALA-7299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545599#comment-16545599 ] Alex Rodoni commented on IMPALA-7299: - https://gerrit.cloudera.org/#/c/10952/ > Impala fails to

[jira] [Resolved] (IMPALA-7288) Codegen crash in FinalizeModule()

[ https://issues.apache.org/jira/browse/IMPALA-7288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig resolved IMPALA-7288. Resolution: Fixed Fix Version/s: Impala 3.1.0 > Codegen crash in FinalizeModule()

[jira] [Commented] (IMPALA-7163) Implement a state machine for the QueryState class

[ https://issues.apache.org/jira/browse/IMPALA-7163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545533#comment-16545533 ] Michael Ho commented on IMPALA-7163: Didn't mean to change the assignee. > Implement a state

[jira] [Assigned] (IMPALA-7163) Implement a state machine for the QueryState class

[ https://issues.apache.org/jira/browse/IMPALA-7163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho reassigned IMPALA-7163: -- Assignee: Sailesh Mukil (was: Michael Ho) > Implement a state machine for the QueryState

[jira] [Commented] (IMPALA-7295) Remove IMPALA_MINICLUSTER_PROFILE=2

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

[jira] [Commented] (IMPALA-7288) Codegen crash in FinalizeModule()

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

[jira] [Commented] (IMPALA-6988) Statement to allow setting ownership for table/view

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

[jira] [Commented] (IMPALA-7288) Codegen crash in FinalizeModule()

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

[jira] [Updated] (IMPALA-7304) Impala shouldn't write column indexes for float columns until PARQUET-1222 is resolved

[ https://issues.apache.org/jira/browse/IMPALA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoltán Borók-Nagy updated IMPALA-7304: -- Description: Impala master branch can already write the [Parquet page

[jira] [Updated] (IMPALA-7304) Impala shouldn't write column indexes for float columns until PARQUET-1222 is resolved

[ https://issues.apache.org/jira/browse/IMPALA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoltán Borók-Nagy updated IMPALA-7304: -- Description: Impala master branch can already writes the [Parquet page

[jira] [Assigned] (IMPALA-7304) Impala shouldn't write column indexes for float columns until PARQUET-1222 is resolved

[ https://issues.apache.org/jira/browse/IMPALA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoltán Borók-Nagy reassigned IMPALA-7304: - Assignee: Zoltán Borók-Nagy > Impala shouldn't write column indexes for float