[jira] [Updated] (IMPALA-7944) count(*) correctly has NDV=1 via being labeled as constant
[
https://issues.apache.org/jira/browse/IMPALA-7944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Rogers updated IMPALA-7944:
Description:
The {{count\(*)}} function has an NDV of 1: the function always returns a
single value.
Presently, {{count\(*)}} has an NDV of 1 via a broken process, but {{sum(id)}}
incorrectly has the NDV of {{id}}, but should be 1.
This is important because it tells us that the query:
{code:sql}
SELECT COUNT(*) FROM foo
{code}
Returns just one row. All good.
In the analyzer, we set a value of NDV=1 via an incorrect process: by labeling
{{count\(*)}} as constant:
* For historical reasons, NDV calculations occur before a node is analyzed.
* We use the default NDV calc: if the node is constant, set NDV = 1, else
compute it.
* Since the function node for {{count\(*)}} is not analyzed, we determine
constant-ness from an inspection.
* All checks for non-constantness fail, leaving the final check: a function is
constant if either a) it has no arguments, or b) all its arguments are constant.
* Since {{count\(*)}} has no expression arguments, and is not marked as
non-deterministic, we infer it must be costant.
* Therefore, it's NDV is set to 1.
This, of course, highly unstable for multiple reasons:
* NDV calculations are done before the node is analyzed. This means, NDV
calculations for a {{SlotRef}} would fail because the ref has not yet been
resolved to a column. (The {{SlotRef}} has special code to work around this
fact.)
* The "treat zero-argument functions as constants and so use NDV=1" rule works
for {{count\(*)}}, but not for {{count(c)}}, nor or {{sum(c)}}, both of which
should have NDV=1.
* {{count\(*)}} is not really a constant; its NDV=1 setting should not really
on (benignly) assuming it is.
* The NDV check const-ness is temporary; once the node is analyzed, it is
correctly marked as non-const. So, the calcs rely on one path saying the the
function is const, another path saying it is not const.
The current NDV for a {{sum(id)}} function is the NDV of {{id}}, which is 7300
in this particular query. The NDV of {{sum(id)}} should be 1.
This should be cleaned up to provide a more reliable, understandable way of
achieving the goal of NDV=1.
As it turns out, this seemed to have been a known issue in the code:
{code:java}
// TODO: we can't correctly determine const-ness before analyzing 'fn_'. We
should
// rework logic so that we do not call this function on unanalyzed exprs.
// Aggregate functions are never constant.
{code}
This defect affects memory estimates. With the correct NDV estimates, several
{{PlannerTest}} cases change to include a lower memory reservation.
was:
The {{count\(*)}} function has an NDV of 1: the function always returns a
single value.
Presently, {{count\(*)}} has an NDV of 1 via a broken process, but {{sum(id)}}
incorrectly has the NDV of {{id}}, but should be 1.
This is important because it tells us that the query:
{code:sql}
SELECT COUNT(*) FROM foo
{code}
Returns just one row. All good.
In the analyzer, we set a value of NDV=1 via an incorrect process: by labeling
{{count\(*)}} as constant:
* For historical reasons, NDV calculations occur before a node is analyzed.
* We use the default NDV calc: if the node is constant, set NDV = 1, else
compute it.
* Since the function node for {{count\(*)}} is not analyzed, we determine
constant-ness from an inspection.
* All checks for non-constantness fail, leaving the final check: a function is
constant if either a) it has no arguments, or b) all its arguments are constant.
* Since {{count\(*)}} has no expression arguments, and is not marked as
non-deterministic, we infer it must be costant.
* Therefore, it's NDV is set to 1.
This, of course, highly unstable for multiple reasons:
* NDV calculations are done before the node is analyzed. This means, NDV
calculations for a {{SlotRef}} would fail because the ref has not yet been
resolved to a column. (The {{SlotRef}} has special code to work around this
fact.)
* The "treat zero-argument functions as constants and so use NDV=1" rule works
for {{count\(*)}}, but not for {{count(c)}}, nor or {{sum(c)}}, both of which
should have NDV=1.
* {{count\(*)}} is not really a constant; its NDV=1 setting should not really
on (benignly) assuming it is.
* The NDV check const-ness is temporary; once the node is analyzed, it is
correctly marked as non-const. So, the calcs rely on one path saying the the
function is const, another path saying it is not const.
The current NDV for a {{sum(id)}} function is the NDV of {{id}}, which is 7300
in this particular query. The NDV of {{sum(id)}} should be 1.
This should be cleaned up to provide a more reliable, understandable way of
achieving the goal of NDV=1.
As it turns out, this seemed to have been a known issue in the
[jira] [Resolved] (IMPALA-7659) Collect count of nulls when collecting stats
[
https://issues.apache.org/jira/browse/IMPALA-7659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v resolved IMPALA-7659.
---
Resolution: Fixed
Assignee: bharath v
Fix Version/s: Impala 3.2.0
> Collect count of nulls when collecting stats
>
>
> Key: IMPALA-7659
> URL: https://issues.apache.org/jira/browse/IMPALA-7659
> Project: IMPALA
> Issue Type: Bug
> Components: Backend, Frontend
>Affects Versions: Impala 3.0, Impala 2.12.0, Impala 3.1.0
>Reporter: Piotr Findeisen
>Assignee: bharath v
>Priority: Major
> Fix For: Impala 3.2.0
>
>
> When Impala calculates table stats, NULL count gets overridden with -1.
> Number of NULLs in a table is a useful information. Even if Impala does not
> benefit from this information, some other tools do. Thus, not collecting this
> information may pose a problem for Impala users (potentially forcing them to
> run COMPUTE STATS elsewhere).
> Now, counting NULLs should be an operation that is cheaper than counting
> NDVs. However, code comment in {{ComputeStatsStmt.java}} suggests otherwise
> ([~tarmstrong] suggested this is because of IMPALA-7655).
> My suggestion would be to
> - improve expression used to collect NULL count
> - collect NULL count during COMPUTE STATS
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Created] (IMPALA-7944) count(*) correctly has NDV=1 via being labeled as constant
Paul Rogers created IMPALA-7944:
---
Summary: count(*) correctly has NDV=1 via being labeled as constant
Key: IMPALA-7944
URL: https://issues.apache.org/jira/browse/IMPALA-7944
Project: IMPALA
Issue Type: Bug
Components: Frontend
Affects Versions: Impala 3.0
Reporter: Paul Rogers
Assignee: Paul Rogers
The {{count\(*)}} function has an NDV of 1: the function always returns a
single value. This is important because it tells us that the query:
{code:sql}
SELECT COUNT(*) FROM foo
{code}
Returns just one row. All good.
In the analyzer, we set a value of NDV=1 via an incorrect process: by labeling
{{count\(*)}} as constant:
* For historical reasons, NDV calculations occur before a node is analyzed.
* We use the default NDV calc: if the node is constant, set NDV = 1, else
compute it.
* Since the function node for {{count\(*)}} is not analyzed, we determine
constant-ness from an inspection.
* All checks for non-constantness fail, leaving the final check: a function is
constant if either a) it has no arguments, or b) all its arguments are constant.
* Since {{count\(*)}} has no expression arguments, and is not marked as
non-deterministic, we infer it must be costant.
* Therefore, it's NDV is set to 1.
This, of course, highly unstable for multiple reasons:
* NDV calculations are done before the node is analyzed. This means, NDV
calculations for a {{SlotRef}} would fail because the ref has not yet been
resolved to a column. (The {{SlotRef}} has special code to work around this
fact.)
* The "treat zero-argument functions as constants and so use NDV=1" rule works
for {{count\(*)}}, but not for {{count(c)}}, nor or {{sum(c)}}, both of which
should have NDV=1.
* {{count\(*)}} is not really a constant; its NDV=1 setting should not really
on (benignly) assuming it is.
* The NDV check const-ness is temporary; once the node is analyzed, it is
correctly marked as non-const. So, the calcs rely on one path saying the the
function is const, another path saying it is not const.
This should be cleaned up to provide a more reliable, understandable way of
achieving the goal of NDV=1.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IMPALA-7497) Consider reintroducing numNulls count in compute stats
[ https://issues.apache.org/jira/browse/IMPALA-7497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bharath v resolved IMPALA-7497. --- Resolution: Fixed Assignee: bharath v Fix Version/s: Impala 3.2.0 > Consider reintroducing numNulls count in compute stats > -- > > Key: IMPALA-7497 > URL: https://issues.apache.org/jira/browse/IMPALA-7497 > Project: IMPALA > Issue Type: Improvement > Components: Frontend >Affects Versions: Impala 3.0, Impala 2.12.0, Impala 3.1.0 >Reporter: Balazs Jeszenszky >Assignee: bharath v >Priority: Major > Fix For: Impala 3.2.0 > > > IMPALA-1003 disabled numNulls calculations for performance reasons. A lot has > changed since, it'd be good to reevaluate computing numNulls. The planner > still has some code that uses it for cardinality estimations, so just adding > it back to compute stats can lead to easy wins. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-7659) Collect count of nulls when collecting stats
[
https://issues.apache.org/jira/browse/IMPALA-7659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v updated IMPALA-7659:
--
Component/s: Frontend
> Collect count of nulls when collecting stats
>
>
> Key: IMPALA-7659
> URL: https://issues.apache.org/jira/browse/IMPALA-7659
> Project: IMPALA
> Issue Type: Bug
> Components: Backend, Frontend
>Affects Versions: Impala 3.0, Impala 2.12.0, Impala 3.1.0
>Reporter: Piotr Findeisen
>Assignee: bharath v
>Priority: Major
> Fix For: Impala 3.2.0
>
>
> When Impala calculates table stats, NULL count gets overridden with -1.
> Number of NULLs in a table is a useful information. Even if Impala does not
> benefit from this information, some other tools do. Thus, not collecting this
> information may pose a problem for Impala users (potentially forcing them to
> run COMPUTE STATS elsewhere).
> Now, counting NULLs should be an operation that is cheaper than counting
> NDVs. However, code comment in {{ComputeStatsStmt.java}} suggests otherwise
> ([~tarmstrong] suggested this is because of IMPALA-7655).
> My suggestion would be to
> - improve expression used to collect NULL count
> - collect NULL count during COMPUTE STATS
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-7497) Consider reintroducing numNulls count in compute stats
[ https://issues.apache.org/jira/browse/IMPALA-7497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bharath v updated IMPALA-7497: -- Affects Version/s: Impala 3.1.0 Impala 3.0 Impala 2.12.0 > Consider reintroducing numNulls count in compute stats > -- > > Key: IMPALA-7497 > URL: https://issues.apache.org/jira/browse/IMPALA-7497 > Project: IMPALA > Issue Type: Improvement > Components: Frontend >Affects Versions: Impala 3.0, Impala 2.12.0, Impala 3.1.0 >Reporter: Balazs Jeszenszky >Assignee: bharath v >Priority: Major > Fix For: Impala 3.2.0 > > > IMPALA-1003 disabled numNulls calculations for performance reasons. A lot has > changed since, it'd be good to reevaluate computing numNulls. The planner > still has some code that uses it for cardinality estimations, so just adding > it back to compute stats can lead to easy wins. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Resolved] (IMPALA-7497) Consider reintroducing numNulls count in compute stats
[ https://issues.apache.org/jira/browse/IMPALA-7497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bharath v resolved IMPALA-7497. --- Resolution: Fixed Assignee: bharath v Fix Version/s: Impala 3.2.0 > Consider reintroducing numNulls count in compute stats > -- > > Key: IMPALA-7497 > URL: https://issues.apache.org/jira/browse/IMPALA-7497 > Project: IMPALA > Issue Type: Improvement > Components: Frontend >Affects Versions: Impala 3.0, Impala 2.12.0, Impala 3.1.0 >Reporter: Balazs Jeszenszky >Assignee: bharath v >Priority: Major > Fix For: Impala 3.2.0 > > > IMPALA-1003 disabled numNulls calculations for performance reasons. A lot has > changed since, it'd be good to reevaluate computing numNulls. The planner > still has some code that uses it for cardinality estimations, so just adding > it back to compute stats can lead to easy wins. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IMPALA-7659) Collect count of nulls when collecting stats
[
https://issues.apache.org/jira/browse/IMPALA-7659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v updated IMPALA-7659:
--
Affects Version/s: Impala 3.1.0
Impala 3.0
Impala 2.12.0
> Collect count of nulls when collecting stats
>
>
> Key: IMPALA-7659
> URL: https://issues.apache.org/jira/browse/IMPALA-7659
> Project: IMPALA
> Issue Type: Bug
> Components: Backend, Frontend
>Affects Versions: Impala 3.0, Impala 2.12.0, Impala 3.1.0
>Reporter: Piotr Findeisen
>Assignee: bharath v
>Priority: Major
> Fix For: Impala 3.2.0
>
>
> When Impala calculates table stats, NULL count gets overridden with -1.
> Number of NULLs in a table is a useful information. Even if Impala does not
> benefit from this information, some other tools do. Thus, not collecting this
> information may pose a problem for Impala users (potentially forcing them to
> run COMPUTE STATS elsewhere).
> Now, counting NULLs should be an operation that is cheaper than counting
> NDVs. However, code comment in {{ComputeStatsStmt.java}} suggests otherwise
> ([~tarmstrong] suggested this is because of IMPALA-7655).
> My suggestion would be to
> - improve expression used to collect NULL count
> - collect NULL count during COMPUTE STATS
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Resolved] (IMPALA-7659) Collect count of nulls when collecting stats
[
https://issues.apache.org/jira/browse/IMPALA-7659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v resolved IMPALA-7659.
---
Resolution: Fixed
Assignee: bharath v
Fix Version/s: Impala 3.2.0
> Collect count of nulls when collecting stats
>
>
> Key: IMPALA-7659
> URL: https://issues.apache.org/jira/browse/IMPALA-7659
> Project: IMPALA
> Issue Type: Bug
> Components: Backend, Frontend
>Affects Versions: Impala 3.0, Impala 2.12.0, Impala 3.1.0
>Reporter: Piotr Findeisen
>Assignee: bharath v
>Priority: Major
> Fix For: Impala 3.2.0
>
>
> When Impala calculates table stats, NULL count gets overridden with -1.
> Number of NULLs in a table is a useful information. Even if Impala does not
> benefit from this information, some other tools do. Thus, not collecting this
> information may pose a problem for Impala users (potentially forcing them to
> run COMPUTE STATS elsewhere).
> Now, counting NULLs should be an operation that is cheaper than counting
> NDVs. However, code comment in {{ComputeStatsStmt.java}} suggests otherwise
> ([~tarmstrong] suggested this is because of IMPALA-7655).
> My suggestion would be to
> - improve expression used to collect NULL count
> - collect NULL count during COMPUTE STATS
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IMPALA-7944) count(*) correctly has NDV=1 via being labeled as constant
[
https://issues.apache.org/jira/browse/IMPALA-7944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Rogers updated IMPALA-7944:
Description:
The {{count(*)}} function has an NDV of 1: the function always returns a single
value. This is important because it tells us that the query:
{code:sql}
SELECT COUNT(*) FROM foo
{code}
Returns just one row. All good.
In the analyzer, we set a value of NDV=1 via an incorrect process: by labeling
{{count(*)}} as constant:
* For historical reasons, NDV calculations occur before a node is analyzed.
* We use the default NDV calc: if the node is constant, set NDV = 1, else
compute it.
* Since the function node for {{count(*)}} is not analyzed, we determine
constant-ness from an inspection.
* All checks for non-constantness fail, leaving the final check: a function is
constant if either a) it has no arguments, or b) all its arguments are constant.
* Since {{count(*)}} has no expression arguments, and is not marked as
non-deterministic, we infer it must be costant.
* Therefore, it's NDV is set to 1.
This, of course, highly unstable for multiple reasons:
* NDV calculations are done before the node is analyzed. This means, NDV
calculations for a {{SlotRef}} would fail because the ref has not yet been
resolved to a column. (The {{SlotRef}} has special code to work around this
fact.)
* The "treat zero-argument functions as constants and so use NDV=1" rule works
for {{count(*)}}, but not for {{count(c)}}, nor or {{sum(c)}}, both of which
should have NDV=1.
* {{count(*)}} is not really a constant; its NDV=1 setting should not really
on (benignly) assuming it is.
* The NDV check const-ness is temporary; once the node is analyzed, it is
correctly marked as non-const. So, the calcs rely on one path saying the the
function is const, another path saying it is not const.
This should be cleaned up to provide a more reliable, understandable way of
achieving the goal of NDV=1.
As it turns out, this seemed to have been a known issue in the code:
{code:java}
// TODO: we can't correctly determine const-ness before analyzing 'fn_'. We
should
// rework logic so that we do not call this function on unanalyzed exprs.
// Aggregate functions are never constant.
{code}
was:
The {{count\(*)}} function has an NDV of 1: the function always returns a
single value. This is important because it tells us that the query:
{code:sql}
SELECT COUNT(*) FROM foo
{code}
Returns just one row. All good.
In the analyzer, we set a value of NDV=1 via an incorrect process: by labeling
{{count\(*)}} as constant:
* For historical reasons, NDV calculations occur before a node is analyzed.
* We use the default NDV calc: if the node is constant, set NDV = 1, else
compute it.
* Since the function node for {{count\(*)}} is not analyzed, we determine
constant-ness from an inspection.
* All checks for non-constantness fail, leaving the final check: a function is
constant if either a) it has no arguments, or b) all its arguments are constant.
* Since {{count\(*)}} has no expression arguments, and is not marked as
non-deterministic, we infer it must be costant.
* Therefore, it's NDV is set to 1.
This, of course, highly unstable for multiple reasons:
* NDV calculations are done before the node is analyzed. This means, NDV
calculations for a {{SlotRef}} would fail because the ref has not yet been
resolved to a column. (The {{SlotRef}} has special code to work around this
fact.)
* The "treat zero-argument functions as constants and so use NDV=1" rule works
for {{count\(*)}}, but not for {{count(c)}}, nor or {{sum(c)}}, both of which
should have NDV=1.
* {{count\(*)}} is not really a constant; its NDV=1 setting should not really
on (benignly) assuming it is.
* The NDV check const-ness is temporary; once the node is analyzed, it is
correctly marked as non-const. So, the calcs rely on one path saying the the
function is const, another path saying it is not const.
This should be cleaned up to provide a more reliable, understandable way of
achieving the goal of NDV=1.
> count(*) correctly has NDV=1 via being labeled as constant
> --
>
> Key: IMPALA-7944
> URL: https://issues.apache.org/jira/browse/IMPALA-7944
> Project: IMPALA
> Issue Type: Bug
> Components: Frontend
>Affects Versions: Impala 3.0
>Reporter: Paul Rogers
>Assignee: Paul Rogers
>Priority: Minor
>
> The {{count(*)}} function has an NDV of 1: the function always returns a
> single value. This is important because it tells us that the query:
> {code:sql}
> SELECT COUNT(*) FROM foo
> {code}
> Returns just one row. All good.
> In the analyzer, we set a value of NDV=1 via an incorrect process: by
> labeling {{count(*)}} as
[jira] [Created] (IMPALA-7944) count(*) correctly has NDV=1 via being labeled as constant
Paul Rogers created IMPALA-7944:
---
Summary: count(*) correctly has NDV=1 via being labeled as constant
Key: IMPALA-7944
URL: https://issues.apache.org/jira/browse/IMPALA-7944
Project: IMPALA
Issue Type: Bug
Components: Frontend
Affects Versions: Impala 3.0
Reporter: Paul Rogers
Assignee: Paul Rogers
The {{count\(*)}} function has an NDV of 1: the function always returns a
single value. This is important because it tells us that the query:
{code:sql}
SELECT COUNT(*) FROM foo
{code}
Returns just one row. All good.
In the analyzer, we set a value of NDV=1 via an incorrect process: by labeling
{{count\(*)}} as constant:
* For historical reasons, NDV calculations occur before a node is analyzed.
* We use the default NDV calc: if the node is constant, set NDV = 1, else
compute it.
* Since the function node for {{count\(*)}} is not analyzed, we determine
constant-ness from an inspection.
* All checks for non-constantness fail, leaving the final check: a function is
constant if either a) it has no arguments, or b) all its arguments are constant.
* Since {{count\(*)}} has no expression arguments, and is not marked as
non-deterministic, we infer it must be costant.
* Therefore, it's NDV is set to 1.
This, of course, highly unstable for multiple reasons:
* NDV calculations are done before the node is analyzed. This means, NDV
calculations for a {{SlotRef}} would fail because the ref has not yet been
resolved to a column. (The {{SlotRef}} has special code to work around this
fact.)
* The "treat zero-argument functions as constants and so use NDV=1" rule works
for {{count\(*)}}, but not for {{count(c)}}, nor or {{sum(c)}}, both of which
should have NDV=1.
* {{count\(*)}} is not really a constant; its NDV=1 setting should not really
on (benignly) assuming it is.
* The NDV check const-ness is temporary; once the node is analyzed, it is
correctly marked as non-const. So, the calcs rely on one path saying the the
function is const, another path saying it is not const.
This should be cleaned up to provide a more reliable, understandable way of
achieving the goal of NDV=1.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-6832) Impala 3.1 Doc: Add additional units to EXTRACT, DATE_PART, TRUNC for temporal data type1
[ https://issues.apache.org/jira/browse/IMPALA-6832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-6832. --- Resolution: Fixed > Impala 3.1 Doc: Add additional units to EXTRACT, DATE_PART, TRUNC for > temporal data type1 > - > > Key: IMPALA-6832 > URL: https://issues.apache.org/jira/browse/IMPALA-6832 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 3.1.0 >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > Part 1 for 3.0: [https://gerrit.cloudera.org/#/c/9957/] > Part 1 for DOCS: https://gerrit.cloudera.org/#/c/11044/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (IMPALA-7481) Impala Doc: Deprecated file-based authorization
[ https://issues.apache.org/jira/browse/IMPALA-7481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni reopened IMPALA-7481: - > Impala Doc: Deprecated file-based authorization > --- > > Key: IMPALA-7481 > URL: https://issues.apache.org/jira/browse/IMPALA-7481 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 3.0 >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7634) Impala 3.1 Doc: Doc the command to gracefully shutdown Impala
[ https://issues.apache.org/jira/browse/IMPALA-7634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7634. --- Resolution: Fixed > Impala 3.1 Doc: Doc the command to gracefully shutdown Impala > - > > Key: IMPALA-7634 > URL: https://issues.apache.org/jira/browse/IMPALA-7634 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 3.1.0 >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11872/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-7836) Impala 3.1 Doc: New query option 'topn_bytes_limit' for TopN to Sort conversion
[ https://issues.apache.org/jira/browse/IMPALA-7836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7836. --- Resolution: Fixed > Impala 3.1 Doc: New query option 'topn_bytes_limit' for TopN to Sort > conversion > --- > > Key: IMPALA-7836 > URL: https://issues.apache.org/jira/browse/IMPALA-7836 > Project: IMPALA > Issue Type: Sub-task > Components: Docs, Frontend >Affects Versions: Impala 2.9.0 >Reporter: Sahil Takiar >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > IMPALA-5004 adds a new query level option called 'topn_bytes_limit' that we > should document. The changes in IMPALA-5004 work by estimating the amount of > memory required to run a TopN operator. The memory estimate is based on the > size of the individual tuples that need to be processed by the TopN operator, > as well as the sum of the limit and offset in the query. TopN operators don't > spill to disk so they have to keep all rows they process in memory. > If the estimated size of the working set of the TopN operator exceeds the > threshold of 'topn_bytes_limit' the TopN operator will be replaced with a > Sort operator. The Sort operator can spill to disk, but it processes all the > data (the limit and offset have no affect). So switching to Sort might incur > performance penalties, but it will require less memory. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Reopened] (IMPALA-7233) Impala 3.1 Doc: Doc the support for IANA timezone database
[ https://issues.apache.org/jira/browse/IMPALA-7233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni reopened IMPALA-7233: - > Impala 3.1 Doc: Doc the support for IANA timezone database > -- > > Key: IMPALA-7233 > URL: https://issues.apache.org/jira/browse/IMPALA-7233 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Labels: future_release_doc > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11946/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Reopened] (IMPALA-7705) Impala 2.13 & 3.1 Docs: ALTER DATABASE SET OWNER
[ https://issues.apache.org/jira/browse/IMPALA-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni reopened IMPALA-7705: - > Impala 2.13 & 3.1 Docs: ALTER DATABASE SET OWNER > > > Key: IMPALA-7705 > URL: https://issues.apache.org/jira/browse/IMPALA-7705 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Labels: future_release_doc > Fix For: Impala 3.1.0 > > > > ALTER DATABASE SET OWNER https://issues.apache.org/jira/browse/IMPALA-7016 > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Reopened] (IMPALA-7743) Impala 3.1 Doc: Document the option to load incremental statistics from catalog
[ https://issues.apache.org/jira/browse/IMPALA-7743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni reopened IMPALA-7743: - > Impala 3.1 Doc: Document the option to load incremental statistics from > catalog > --- > > Key: IMPALA-7743 > URL: https://issues.apache.org/jira/browse/IMPALA-7743 > Project: IMPALA > Issue Type: Sub-task >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Labels: future_release_doc > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11790/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Reopened] (IMPALA-7815) Impala 3.1 Release Notes
[ https://issues.apache.org/jira/browse/IMPALA-7815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni reopened IMPALA-7815: - > Impala 3.1 Release Notes > > > Key: IMPALA-7815 > URL: https://issues.apache.org/jira/browse/IMPALA-7815 > Project: IMPALA > Issue Type: Task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Labels: future_release_doc > Fix For: Impala 3.1.0 > > > Update: > impala_keydefs.ditamap > impala_release_notes.ditamap > impala_fixed_issues.xml > impala_incompatible_changes.xml > impala_new_features.xml -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-7789) Impala 3.1 Doc: Admission Control Status in Impala Shell
[ https://issues.apache.org/jira/browse/IMPALA-7789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni updated IMPALA-7789: Labels: (was: future_release_doc) > Impala 3.1 Doc: Admission Control Status in Impala Shell > > > Key: IMPALA-7789 > URL: https://issues.apache.org/jira/browse/IMPALA-7789 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11895/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-7186) Docs for kudu_read_mode
[ https://issues.apache.org/jira/browse/IMPALA-7186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni updated IMPALA-7186: Labels: (was: docs future_release_doc) > Docs for kudu_read_mode > --- > > Key: IMPALA-7186 > URL: https://issues.apache.org/jira/browse/IMPALA-7186 > Project: IMPALA > Issue Type: Task > Components: Docs >Affects Versions: Impala 3.1.0 >Reporter: Thomas Tauber-Marshall >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > IMPALA-6812 added a new query option, KUDU_READ_MODE, which should be > documented with something like: > KUDU_READ_MODE Query Option > This query option allows users to set a desired consistency level for scans > of Kudu tables. Possible values are DEFAULT, READ_LATEST, and > READ_AT_SNAPSHOT. If DEFAULT is specified, the value of the startup flag > '--kudu_read_mode' will be used. > READ_LATEST > Kudu provides no consistency guarantees for this mode, expect that all > returned rows were committed at some point, sometimes known as 'Read > Committed' isolation. > READ_AT_SNAPSHOT > Kudu will take a snapshot of the current state of the data and perform the > scan over the snapshot, possibly after briefly waiting for ongoing writes to > complete. This provides "Read Your Writes" consistency within a single Impala > session, except in the case of a Kudu leader change. See the Kudu > documentation for more details. > Type: string > Default: DEFAULT > Added in: Impala 3.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-6832) Impala 3.1 Doc: Add additional units to EXTRACT, DATE_PART, TRUNC for temporal data type1
[ https://issues.apache.org/jira/browse/IMPALA-6832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni updated IMPALA-6832: Labels: (was: future_release_doc) > Impala 3.1 Doc: Add additional units to EXTRACT, DATE_PART, TRUNC for > temporal data type1 > - > > Key: IMPALA-6832 > URL: https://issues.apache.org/jira/browse/IMPALA-6832 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 3.1.0 >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > Part 1 for 3.0: [https://gerrit.cloudera.org/#/c/9957/] > Part 1 for DOCS: https://gerrit.cloudera.org/#/c/11044/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7186) Docs for kudu_read_mode
[ https://issues.apache.org/jira/browse/IMPALA-7186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7186. --- Resolution: Fixed > Docs for kudu_read_mode > --- > > Key: IMPALA-7186 > URL: https://issues.apache.org/jira/browse/IMPALA-7186 > Project: IMPALA > Issue Type: Task > Components: Docs >Affects Versions: Impala 3.1.0 >Reporter: Thomas Tauber-Marshall >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > IMPALA-6812 added a new query option, KUDU_READ_MODE, which should be > documented with something like: > KUDU_READ_MODE Query Option > This query option allows users to set a desired consistency level for scans > of Kudu tables. Possible values are DEFAULT, READ_LATEST, and > READ_AT_SNAPSHOT. If DEFAULT is specified, the value of the startup flag > '--kudu_read_mode' will be used. > READ_LATEST > Kudu provides no consistency guarantees for this mode, expect that all > returned rows were committed at some point, sometimes known as 'Read > Committed' isolation. > READ_AT_SNAPSHOT > Kudu will take a snapshot of the current state of the data and perform the > scan over the snapshot, possibly after briefly waiting for ongoing writes to > complete. This provides "Read Your Writes" consistency within a single Impala > session, except in the case of a Kudu leader change. See the Kudu > documentation for more details. > Type: string > Default: DEFAULT > Added in: Impala 3.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-6832) Impala 3.1 Doc: Add additional units to EXTRACT, DATE_PART, TRUNC for temporal data type1
[ https://issues.apache.org/jira/browse/IMPALA-6832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-6832. --- Resolution: Fixed > Impala 3.1 Doc: Add additional units to EXTRACT, DATE_PART, TRUNC for > temporal data type1 > - > > Key: IMPALA-6832 > URL: https://issues.apache.org/jira/browse/IMPALA-6832 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 3.1.0 >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > Part 1 for 3.0: [https://gerrit.cloudera.org/#/c/9957/] > Part 1 for DOCS: https://gerrit.cloudera.org/#/c/11044/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7186) Docs for kudu_read_mode
[ https://issues.apache.org/jira/browse/IMPALA-7186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7186. --- Resolution: Fixed > Docs for kudu_read_mode > --- > > Key: IMPALA-7186 > URL: https://issues.apache.org/jira/browse/IMPALA-7186 > Project: IMPALA > Issue Type: Task > Components: Docs >Affects Versions: Impala 3.1.0 >Reporter: Thomas Tauber-Marshall >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > IMPALA-6812 added a new query option, KUDU_READ_MODE, which should be > documented with something like: > KUDU_READ_MODE Query Option > This query option allows users to set a desired consistency level for scans > of Kudu tables. Possible values are DEFAULT, READ_LATEST, and > READ_AT_SNAPSHOT. If DEFAULT is specified, the value of the startup flag > '--kudu_read_mode' will be used. > READ_LATEST > Kudu provides no consistency guarantees for this mode, expect that all > returned rows were committed at some point, sometimes known as 'Read > Committed' isolation. > READ_AT_SNAPSHOT > Kudu will take a snapshot of the current state of the data and perform the > scan over the snapshot, possibly after briefly waiting for ongoing writes to > complete. This provides "Read Your Writes" consistency within a single Impala > session, except in the case of a Kudu leader change. See the Kudu > documentation for more details. > Type: string > Default: DEFAULT > Added in: Impala 3.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Reopened] (IMPALA-6832) Impala 3.1 Doc: Add additional units to EXTRACT, DATE_PART, TRUNC for temporal data type1
[ https://issues.apache.org/jira/browse/IMPALA-6832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni reopened IMPALA-6832: - > Impala 3.1 Doc: Add additional units to EXTRACT, DATE_PART, TRUNC for > temporal data type1 > - > > Key: IMPALA-6832 > URL: https://issues.apache.org/jira/browse/IMPALA-6832 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 3.1.0 >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > Part 1 for 3.0: [https://gerrit.cloudera.org/#/c/9957/] > Part 1 for DOCS: https://gerrit.cloudera.org/#/c/11044/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-7481) Impala Doc: Deprecated file-based authorization
[ https://issues.apache.org/jira/browse/IMPALA-7481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni updated IMPALA-7481: Labels: (was: future_release_doc) > Impala Doc: Deprecated file-based authorization > --- > > Key: IMPALA-7481 > URL: https://issues.apache.org/jira/browse/IMPALA-7481 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 3.0 >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-7244) Impala 3.1 Doc: Remove unsupported format write support
[ https://issues.apache.org/jira/browse/IMPALA-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni updated IMPALA-7244: Labels: (was: future_release_doc) > Impala 3.1 Doc: Remove unsupported format write support > --- > > Key: IMPALA-7244 > URL: https://issues.apache.org/jira/browse/IMPALA-7244 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 3.1.0 >Reporter: Bikramjeet Vig >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > the parent task removes write support for unsupported formats like > *Sequence,* *Avro and compressed text*. Also, the related query options > *ALLOW_UNSUPPORTED_FORMATS* and *SEQ_COMPRESSION_MODE* have been migrated to > the 'REMOVED' query options type and therefore are no longer functional. > https://gerrit.cloudera.org/#/c/11842/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Reopened] (IMPALA-7244) Impala 3.1 Doc: Remove unsupported format write support
[ https://issues.apache.org/jira/browse/IMPALA-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni reopened IMPALA-7244: - > Impala 3.1 Doc: Remove unsupported format write support > --- > > Key: IMPALA-7244 > URL: https://issues.apache.org/jira/browse/IMPALA-7244 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 3.1.0 >Reporter: Bikramjeet Vig >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > the parent task removes write support for unsupported formats like > *Sequence,* *Avro and compressed text*. Also, the related query options > *ALLOW_UNSUPPORTED_FORMATS* and *SEQ_COMPRESSION_MODE* have been migrated to > the 'REMOVED' query options type and therefore are no longer functional. > https://gerrit.cloudera.org/#/c/11842/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7481) Impala Doc: Deprecated file-based authorization
[ https://issues.apache.org/jira/browse/IMPALA-7481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7481. --- Resolution: Fixed > Impala Doc: Deprecated file-based authorization > --- > > Key: IMPALA-7481 > URL: https://issues.apache.org/jira/browse/IMPALA-7481 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 3.0 >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7244) Impala 3.1 Doc: Remove unsupported format write support
[ https://issues.apache.org/jira/browse/IMPALA-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7244. --- Resolution: Fixed > Impala 3.1 Doc: Remove unsupported format write support > --- > > Key: IMPALA-7244 > URL: https://issues.apache.org/jira/browse/IMPALA-7244 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 3.1.0 >Reporter: Bikramjeet Vig >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > the parent task removes write support for unsupported formats like > *Sequence,* *Avro and compressed text*. Also, the related query options > *ALLOW_UNSUPPORTED_FORMATS* and *SEQ_COMPRESSION_MODE* have been migrated to > the 'REMOVED' query options type and therefore are no longer functional. > https://gerrit.cloudera.org/#/c/11842/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7244) Impala 3.1 Doc: Remove unsupported format write support
[ https://issues.apache.org/jira/browse/IMPALA-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7244. --- Resolution: Fixed > Impala 3.1 Doc: Remove unsupported format write support > --- > > Key: IMPALA-7244 > URL: https://issues.apache.org/jira/browse/IMPALA-7244 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 3.1.0 >Reporter: Bikramjeet Vig >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > the parent task removes write support for unsupported formats like > *Sequence,* *Avro and compressed text*. Also, the related query options > *ALLOW_UNSUPPORTED_FORMATS* and *SEQ_COMPRESSION_MODE* have been migrated to > the 'REMOVED' query options type and therefore are no longer functional. > https://gerrit.cloudera.org/#/c/11842/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (IMPALA-7186) Docs for kudu_read_mode
[ https://issues.apache.org/jira/browse/IMPALA-7186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni reopened IMPALA-7186: - > Docs for kudu_read_mode > --- > > Key: IMPALA-7186 > URL: https://issues.apache.org/jira/browse/IMPALA-7186 > Project: IMPALA > Issue Type: Task > Components: Docs >Affects Versions: Impala 3.1.0 >Reporter: Thomas Tauber-Marshall >Assignee: Alex Rodoni >Priority: Major > Labels: docs, future_release_doc > Fix For: Impala 3.1.0 > > > IMPALA-6812 added a new query option, KUDU_READ_MODE, which should be > documented with something like: > KUDU_READ_MODE Query Option > This query option allows users to set a desired consistency level for scans > of Kudu tables. Possible values are DEFAULT, READ_LATEST, and > READ_AT_SNAPSHOT. If DEFAULT is specified, the value of the startup flag > '--kudu_read_mode' will be used. > READ_LATEST > Kudu provides no consistency guarantees for this mode, expect that all > returned rows were committed at some point, sometimes known as 'Read > Committed' isolation. > READ_AT_SNAPSHOT > Kudu will take a snapshot of the current state of the data and perform the > scan over the snapshot, possibly after briefly waiting for ongoing writes to > complete. This provides "Read Your Writes" consistency within a single Impala > session, except in the case of a Kudu leader change. See the Kudu > documentation for more details. > Type: string > Default: DEFAULT > Added in: Impala 3.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7481) Impala Doc: Deprecated file-based authorization
[ https://issues.apache.org/jira/browse/IMPALA-7481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7481. --- Resolution: Fixed > Impala Doc: Deprecated file-based authorization > --- > > Key: IMPALA-7481 > URL: https://issues.apache.org/jira/browse/IMPALA-7481 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 3.0 >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-7706) Impala Doc: ALTER TABLE SET OWNER not on Sentry page for Impala
[ https://issues.apache.org/jira/browse/IMPALA-7706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7706. --- Resolution: Fixed > Impala Doc: ALTER TABLE SET OWNER not on Sentry page for Impala > --- > > Key: IMPALA-7706 > URL: https://issues.apache.org/jira/browse/IMPALA-7706 > Project: IMPALA > Issue Type: Task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > ALTER TABLE SET OWNER, which requires either ALL WITH GRANT, or OWNER WITH > GRANT for the TABLE, is not mentioned on the page. It's a special case so > may not fit in the table. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-7706) Impala Doc: ALTER TABLE SET OWNER not on Sentry page for Impala
[ https://issues.apache.org/jira/browse/IMPALA-7706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni updated IMPALA-7706: Labels: (was: future_release_doc) > Impala Doc: ALTER TABLE SET OWNER not on Sentry page for Impala > --- > > Key: IMPALA-7706 > URL: https://issues.apache.org/jira/browse/IMPALA-7706 > Project: IMPALA > Issue Type: Task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > ALTER TABLE SET OWNER, which requires either ALL WITH GRANT, or OWNER WITH > GRANT for the TABLE, is not mentioned on the page. It's a special case so > may not fit in the table. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7546) Impala 3.1 Doc: Doc the new query option TIMEZONE
[ https://issues.apache.org/jira/browse/IMPALA-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7546. --- Resolution: Fixed > Impala 3.1 Doc: Doc the new query option TIMEZONE > - > > Key: IMPALA-7546 > URL: https://issues.apache.org/jira/browse/IMPALA-7546 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11505/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7706) Impala Doc: ALTER TABLE SET OWNER not on Sentry page for Impala
[ https://issues.apache.org/jira/browse/IMPALA-7706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7706. --- Resolution: Fixed > Impala Doc: ALTER TABLE SET OWNER not on Sentry page for Impala > --- > > Key: IMPALA-7706 > URL: https://issues.apache.org/jira/browse/IMPALA-7706 > Project: IMPALA > Issue Type: Task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > ALTER TABLE SET OWNER, which requires either ALL WITH GRANT, or OWNER WITH > GRANT for the TABLE, is not mentioned on the page. It's a special case so > may not fit in the table. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (IMPALA-7706) Impala Doc: ALTER TABLE SET OWNER not on Sentry page for Impala
[ https://issues.apache.org/jira/browse/IMPALA-7706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni reopened IMPALA-7706: - > Impala Doc: ALTER TABLE SET OWNER not on Sentry page for Impala > --- > > Key: IMPALA-7706 > URL: https://issues.apache.org/jira/browse/IMPALA-7706 > Project: IMPALA > Issue Type: Task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > ALTER TABLE SET OWNER, which requires either ALL WITH GRANT, or OWNER WITH > GRANT for the TABLE, is not mentioned on the page. It's a special case so > may not fit in the table. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Reopened] (IMPALA-7546) Impala 3.1 Doc: Doc the new query option TIMEZONE
[ https://issues.apache.org/jira/browse/IMPALA-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni reopened IMPALA-7546: - > Impala 3.1 Doc: Doc the new query option TIMEZONE > - > > Key: IMPALA-7546 > URL: https://issues.apache.org/jira/browse/IMPALA-7546 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11505/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-7546) Impala 3.1 Doc: Doc the new query option TIMEZONE
[ https://issues.apache.org/jira/browse/IMPALA-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni updated IMPALA-7546: Labels: (was: future_release_doc) > Impala 3.1 Doc: Doc the new query option TIMEZONE > - > > Key: IMPALA-7546 > URL: https://issues.apache.org/jira/browse/IMPALA-7546 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11505/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-7861) ABFS docs: SSL is now enabled by default regardless of URI scheme
[ https://issues.apache.org/jira/browse/IMPALA-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni updated IMPALA-7861: Labels: (was: future_release_doc) > ABFS docs: SSL is now enabled by default regardless of URI scheme > - > > Key: IMPALA-7861 > URL: https://issues.apache.org/jira/browse/IMPALA-7861 > Project: IMPALA > Issue Type: Bug >Reporter: Sean Mackrory >Assignee: Alex Rodoni >Priority: Trivial > Fix For: Impala 3.1.0 > > > When it was originally submitted to Hadoop, the ABFS driver disabled TLS when > using the URI scheme "abfs", and enabled TLS when using the URI scheme > "abfss". This was reflected in the documentation originally submitted for > ABFS: > https://github.com/apache/impala/commit/5baa289fd039d339c63d5c475645e69fe0c6b8df. > We should update that to reflect that TLS is enabled with either URI scheme > unless you disable TLS in configuration by setting > fs.azure.always.use.https=false in the configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7861) ABFS docs: SSL is now enabled by default regardless of URI scheme
[ https://issues.apache.org/jira/browse/IMPALA-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7861. --- Resolution: Fixed > ABFS docs: SSL is now enabled by default regardless of URI scheme > - > > Key: IMPALA-7861 > URL: https://issues.apache.org/jira/browse/IMPALA-7861 > Project: IMPALA > Issue Type: Bug >Reporter: Sean Mackrory >Assignee: Alex Rodoni >Priority: Trivial > Fix For: Impala 3.1.0 > > > When it was originally submitted to Hadoop, the ABFS driver disabled TLS when > using the URI scheme "abfs", and enabled TLS when using the URI scheme > "abfss". This was reflected in the documentation originally submitted for > ABFS: > https://github.com/apache/impala/commit/5baa289fd039d339c63d5c475645e69fe0c6b8df. > We should update that to reflect that TLS is enabled with either URI scheme > unless you disable TLS in configuration by setting > fs.azure.always.use.https=false in the configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (IMPALA-7861) ABFS docs: SSL is now enabled by default regardless of URI scheme
[ https://issues.apache.org/jira/browse/IMPALA-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni reopened IMPALA-7861: - > ABFS docs: SSL is now enabled by default regardless of URI scheme > - > > Key: IMPALA-7861 > URL: https://issues.apache.org/jira/browse/IMPALA-7861 > Project: IMPALA > Issue Type: Bug >Reporter: Sean Mackrory >Assignee: Alex Rodoni >Priority: Trivial > Fix For: Impala 3.1.0 > > > When it was originally submitted to Hadoop, the ABFS driver disabled TLS when > using the URI scheme "abfs", and enabled TLS when using the URI scheme > "abfss". This was reflected in the documentation originally submitted for > ABFS: > https://github.com/apache/impala/commit/5baa289fd039d339c63d5c475645e69fe0c6b8df. > We should update that to reflect that TLS is enabled with either URI scheme > unless you disable TLS in configuration by setting > fs.azure.always.use.https=false in the configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7861) ABFS docs: SSL is now enabled by default regardless of URI scheme
[ https://issues.apache.org/jira/browse/IMPALA-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7861. --- Resolution: Fixed > ABFS docs: SSL is now enabled by default regardless of URI scheme > - > > Key: IMPALA-7861 > URL: https://issues.apache.org/jira/browse/IMPALA-7861 > Project: IMPALA > Issue Type: Bug >Reporter: Sean Mackrory >Assignee: Alex Rodoni >Priority: Trivial > Fix For: Impala 3.1.0 > > > When it was originally submitted to Hadoop, the ABFS driver disabled TLS when > using the URI scheme "abfs", and enabled TLS when using the URI scheme > "abfss". This was reflected in the documentation originally submitted for > ABFS: > https://github.com/apache/impala/commit/5baa289fd039d339c63d5c475645e69fe0c6b8df. > We should update that to reflect that TLS is enabled with either URI scheme > unless you disable TLS in configuration by setting > fs.azure.always.use.https=false in the configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7431) Impala 3.1 Doc: Make METASTORE_DB configurable and default to escaped $IMPALA_HOME
[ https://issues.apache.org/jira/browse/IMPALA-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7431. --- Resolution: Fixed > Impala 3.1 Doc: Make METASTORE_DB configurable and default to escaped > $IMPALA_HOME > -- > > Key: IMPALA-7431 > URL: https://issues.apache.org/jira/browse/IMPALA-7431 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7789) Impala 3.1 Doc: Admission Control Status in Impala Shell
[ https://issues.apache.org/jira/browse/IMPALA-7789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7789. --- Resolution: Fixed > Impala 3.1 Doc: Admission Control Status in Impala Shell > > > Key: IMPALA-7789 > URL: https://issues.apache.org/jira/browse/IMPALA-7789 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11895/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7434) Impala 2.12 Doc: Kudu's kinit does not support auth_to_local rules with Heimdal kerberos
[ https://issues.apache.org/jira/browse/IMPALA-7434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7434. --- Resolution: Fixed > Impala 2.12 Doc: Kudu's kinit does not support auth_to_local rules with > Heimdal kerberos > > > Key: IMPALA-7434 > URL: https://issues.apache.org/jira/browse/IMPALA-7434 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11204/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7806) Impala 3.1 Doc: Check the existing known issues against 3.1 fixes
[ https://issues.apache.org/jira/browse/IMPALA-7806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7806. --- Resolution: Fixed > Impala 3.1 Doc: Check the existing known issues against 3.1 fixes > - > > Key: IMPALA-7806 > URL: https://issues.apache.org/jira/browse/IMPALA-7806 > Project: IMPALA > Issue Type: Task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11921/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7743) Impala 3.1 Doc: Document the option to load incremental statistics from catalog
[ https://issues.apache.org/jira/browse/IMPALA-7743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7743. --- Resolution: Fixed > Impala 3.1 Doc: Document the option to load incremental statistics from > catalog > --- > > Key: IMPALA-7743 > URL: https://issues.apache.org/jira/browse/IMPALA-7743 > Project: IMPALA > Issue Type: Sub-task >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11790/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7836) Impala 3.1 Doc: New query option 'topn_bytes_limit' for TopN to Sort conversion
[ https://issues.apache.org/jira/browse/IMPALA-7836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7836. --- Resolution: Fixed > Impala 3.1 Doc: New query option 'topn_bytes_limit' for TopN to Sort > conversion > --- > > Key: IMPALA-7836 > URL: https://issues.apache.org/jira/browse/IMPALA-7836 > Project: IMPALA > Issue Type: Sub-task > Components: Docs, Frontend >Affects Versions: Impala 2.9.0 >Reporter: Sahil Takiar >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > IMPALA-5004 adds a new query level option called 'topn_bytes_limit' that we > should document. The changes in IMPALA-5004 work by estimating the amount of > memory required to run a TopN operator. The memory estimate is based on the > size of the individual tuples that need to be processed by the TopN operator, > as well as the sum of the limit and offset in the query. TopN operators don't > spill to disk so they have to keep all rows they process in memory. > If the estimated size of the working set of the TopN operator exceeds the > threshold of 'topn_bytes_limit' the TopN operator will be replaced with a > Sort operator. The Sort operator can spill to disk, but it processes all the > data (the limit and offset have no affect). So switching to Sort might incur > performance penalties, but it will require less memory. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-7434) Impala 2.12 Doc: Kudu's kinit does not support auth_to_local rules with Heimdal kerberos
[ https://issues.apache.org/jira/browse/IMPALA-7434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7434. --- Resolution: Fixed > Impala 2.12 Doc: Kudu's kinit does not support auth_to_local rules with > Heimdal kerberos > > > Key: IMPALA-7434 > URL: https://issues.apache.org/jira/browse/IMPALA-7434 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11204/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-7432) Impala 3.1 Doc: Add logged_in_user alias for effective_user
[ https://issues.apache.org/jira/browse/IMPALA-7432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7432. --- Resolution: Fixed > Impala 3.1 Doc: Add logged_in_user alias for effective_user > --- > > Key: IMPALA-7432 > URL: https://issues.apache.org/jira/browse/IMPALA-7432 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11755/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-7525) Impala Doc: Document SHOW GRANT USER
[ https://issues.apache.org/jira/browse/IMPALA-7525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7525. --- Resolution: Fixed > Impala Doc: Document SHOW GRANT USER > > > Key: IMPALA-7525 > URL: https://issues.apache.org/jira/browse/IMPALA-7525 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11454/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-7614) Impala 3.1 Doc: Document the New Invalidate Options
[
https://issues.apache.org/jira/browse/IMPALA-7614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rodoni closed IMPALA-7614.
---
Resolution: Fixed
> Impala 3.1 Doc: Document the New Invalidate Options
> ---
>
> Key: IMPALA-7614
> URL: https://issues.apache.org/jira/browse/IMPALA-7614
> Project: IMPALA
> Issue Type: Task
> Components: Docs
>Reporter: Alex Rodoni
>Assignee: Alex Rodoni
>Priority: Major
> Fix For: Impala 3.1.0
>
>
> Document the new options:
> - invalidate_tables_timeout_s
> - invalidate_tables_on_memory_pressure{quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IMPALA-7195) Impala 3.1 Doc: Proxy user list should support groups
[ https://issues.apache.org/jira/browse/IMPALA-7195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7195. --- Resolution: Fixed > Impala 3.1 Doc: Proxy user list should support groups > - > > Key: IMPALA-7195 > URL: https://issues.apache.org/jira/browse/IMPALA-7195 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11068/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-7103) Impala 3.1 Doc: Query option to enable EC
[ https://issues.apache.org/jira/browse/IMPALA-7103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7103. --- Resolution: Fixed > Impala 3.1 Doc: Query option to enable EC > - > > Key: IMPALA-7103 > URL: https://issues.apache.org/jira/browse/IMPALA-7103 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11855/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-7765) Impala 3.1 Doc: Docuement MAX_MEM_ESTIMATE_FOR_ADMISSION
[ https://issues.apache.org/jira/browse/IMPALA-7765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7765. --- Resolution: Fixed > Impala 3.1 Doc: Docuement MAX_MEM_ESTIMATE_FOR_ADMISSION > > > Key: IMPALA-7765 > URL: https://issues.apache.org/jira/browse/IMPALA-7765 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11804/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-7233) Impala 3.1 Doc: Doc the support for IANA timezone database
[ https://issues.apache.org/jira/browse/IMPALA-7233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7233. --- Resolution: Fixed > Impala 3.1 Doc: Doc the support for IANA timezone database > -- > > Key: IMPALA-7233 > URL: https://issues.apache.org/jira/browse/IMPALA-7233 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11946/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-6481) Impala Doc: WIDTH_BUCKET function
[ https://issues.apache.org/jira/browse/IMPALA-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-6481. --- Resolution: Fixed > Impala Doc: WIDTH_BUCKET function > - > > Key: IMPALA-6481 > URL: https://issues.apache.org/jira/browse/IMPALA-6481 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7525) Impala Doc: Document SHOW GRANT USER
[ https://issues.apache.org/jira/browse/IMPALA-7525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7525. --- Resolution: Fixed > Impala Doc: Document SHOW GRANT USER > > > Key: IMPALA-7525 > URL: https://issues.apache.org/jira/browse/IMPALA-7525 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11454/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7206) Doc THREAD_RESERVATION_LIMIT
[ https://issues.apache.org/jira/browse/IMPALA-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7206. --- Resolution: Fixed > Doc THREAD_RESERVATION_LIMIT > > > Key: IMPALA-7206 > URL: https://issues.apache.org/jira/browse/IMPALA-7206 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11237/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-6919) Impala 3.1 Doc: Doc the COMMENT ON statements
[ https://issues.apache.org/jira/browse/IMPALA-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-6919. --- Resolution: Fixed > Impala 3.1 Doc: Doc the COMMENT ON statements > - > > Key: IMPALA-6919 > URL: https://issues.apache.org/jira/browse/IMPALA-6919 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 2.13.0, Impala 3.1.0 >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11370/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-6481) Impala Doc: WIDTH_BUCKET function
[ https://issues.apache.org/jira/browse/IMPALA-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-6481. --- Resolution: Fixed > Impala Doc: WIDTH_BUCKET function > - > > Key: IMPALA-6481 > URL: https://issues.apache.org/jira/browse/IMPALA-6481 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-7432) Impala 3.1 Doc: Add logged_in_user alias for effective_user
[ https://issues.apache.org/jira/browse/IMPALA-7432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7432. --- Resolution: Fixed > Impala 3.1 Doc: Add logged_in_user alias for effective_user > --- > > Key: IMPALA-7432 > URL: https://issues.apache.org/jira/browse/IMPALA-7432 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11755/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7392) Document SCAN_BYTES_LIMIT
[ https://issues.apache.org/jira/browse/IMPALA-7392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7392. --- Resolution: Fixed > Document SCAN_BYTES_LIMIT > - > > Key: IMPALA-7392 > URL: https://issues.apache.org/jira/browse/IMPALA-7392 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Tim Armstrong >Assignee: Alex Rodoni >Priority: Major > Labels: docs, resource-management > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11240/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-7788) Impala Doc: ADLS Gen2 Support
[ https://issues.apache.org/jira/browse/IMPALA-7788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7788. --- Resolution: Fixed > Impala Doc: ADLS Gen2 Support > - > > Key: IMPALA-7788 > URL: https://issues.apache.org/jira/browse/IMPALA-7788 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > - Update impala_adls doc > - Search for file format notes, such as for S3, and update the docs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-7076) Impala 2.13 & 3.1 Docs: ALTER TABLE / VIEW SET OWNER
[ https://issues.apache.org/jira/browse/IMPALA-7076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7076. --- Resolution: Fixed > Impala 2.13 & 3.1 Docs: ALTER TABLE / VIEW SET OWNER > > > Key: IMPALA-7076 > URL: https://issues.apache.org/jira/browse/IMPALA-7076 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Fredy Wijaya >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7815) Impala 3.1 Release Notes
[ https://issues.apache.org/jira/browse/IMPALA-7815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7815. --- Resolution: Fixed > Impala 3.1 Release Notes > > > Key: IMPALA-7815 > URL: https://issues.apache.org/jira/browse/IMPALA-7815 > Project: IMPALA > Issue Type: Task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > Update: > impala_keydefs.ditamap > impala_release_notes.ditamap > impala_fixed_issues.xml > impala_incompatible_changes.xml > impala_new_features.xml -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7788) Impala Doc: ADLS Gen2 Support
[ https://issues.apache.org/jira/browse/IMPALA-7788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7788. --- Resolution: Fixed > Impala Doc: ADLS Gen2 Support > - > > Key: IMPALA-7788 > URL: https://issues.apache.org/jira/browse/IMPALA-7788 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > - Update impala_adls doc > - Search for file format notes, such as for S3, and update the docs -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7705) Impala 2.13 & 3.1 Docs: ALTER DATABASE SET OWNER
[ https://issues.apache.org/jira/browse/IMPALA-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7705. --- Resolution: Fixed > Impala 2.13 & 3.1 Docs: ALTER DATABASE SET OWNER > > > Key: IMPALA-7705 > URL: https://issues.apache.org/jira/browse/IMPALA-7705 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > > ALTER DATABASE SET OWNER https://issues.apache.org/jira/browse/IMPALA-7016 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-7218) Impala 3.1 Doc: Allow Column Definitions in ALTER VIEW
[ https://issues.apache.org/jira/browse/IMPALA-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7218. --- Resolution: Fixed > Impala 3.1 Doc: Allow Column Definitions in ALTER VIEW > -- > > Key: IMPALA-7218 > URL: https://issues.apache.org/jira/browse/IMPALA-7218 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-7233) Impala 3.1 Doc: Doc the support for IANA timezone database
[ https://issues.apache.org/jira/browse/IMPALA-7233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7233. --- Resolution: Fixed > Impala 3.1 Doc: Doc the support for IANA timezone database > -- > > Key: IMPALA-7233 > URL: https://issues.apache.org/jira/browse/IMPALA-7233 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11946/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-7687) Impala 3.1 Doc: Add support for multiple distinct operators in the same query block
[ https://issues.apache.org/jira/browse/IMPALA-7687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7687. --- Resolution: Fixed > Impala 3.1 Doc: Add support for multiple distinct operators in the same query > block > --- > > Key: IMPALA-7687 > URL: https://issues.apache.org/jira/browse/IMPALA-7687 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 3.1.0 >Reporter: Adam Holley >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11823/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-7206) Doc THREAD_RESERVATION_LIMIT
[ https://issues.apache.org/jira/browse/IMPALA-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7206. --- Resolution: Fixed > Doc THREAD_RESERVATION_LIMIT > > > Key: IMPALA-7206 > URL: https://issues.apache.org/jira/browse/IMPALA-7206 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11237/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7123) Impala 3.1 or 4.0 Doc: Restrict Impala to only support timezones that work in Hive (IANA + Java)
[ https://issues.apache.org/jira/browse/IMPALA-7123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7123. --- Resolution: Fixed > Impala 3.1 or 4.0 Doc: Restrict Impala to only support timezones that work in > Hive (IANA + Java) > > > Key: IMPALA-7123 > URL: https://issues.apache.org/jira/browse/IMPALA-7123 > Project: IMPALA > Issue Type: Task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7103) Impala 3.1 Doc: Query option to enable EC
[ https://issues.apache.org/jira/browse/IMPALA-7103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7103. --- Resolution: Fixed > Impala 3.1 Doc: Query option to enable EC > - > > Key: IMPALA-7103 > URL: https://issues.apache.org/jira/browse/IMPALA-7103 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11855/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7614) Impala 3.1 Doc: Document the New Invalidate Options
[
https://issues.apache.org/jira/browse/IMPALA-7614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rodoni closed IMPALA-7614.
---
Resolution: Fixed
> Impala 3.1 Doc: Document the New Invalidate Options
> ---
>
> Key: IMPALA-7614
> URL: https://issues.apache.org/jira/browse/IMPALA-7614
> Project: IMPALA
> Issue Type: Task
> Components: Docs
>Reporter: Alex Rodoni
>Assignee: Alex Rodoni
>Priority: Major
> Fix For: Impala 3.1.0
>
>
> Document the new options:
> - invalidate_tables_timeout_s
> - invalidate_tables_on_memory_pressure{quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7687) Impala 3.1 Doc: Add support for multiple distinct operators in the same query block
[ https://issues.apache.org/jira/browse/IMPALA-7687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7687. --- Resolution: Fixed > Impala 3.1 Doc: Add support for multiple distinct operators in the same query > block > --- > > Key: IMPALA-7687 > URL: https://issues.apache.org/jira/browse/IMPALA-7687 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 3.1.0 >Reporter: Adam Holley >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11823/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7076) Impala 2.13 & 3.1 Docs: ALTER TABLE / VIEW SET OWNER
[ https://issues.apache.org/jira/browse/IMPALA-7076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7076. --- Resolution: Fixed > Impala 2.13 & 3.1 Docs: ALTER TABLE / VIEW SET OWNER > > > Key: IMPALA-7076 > URL: https://issues.apache.org/jira/browse/IMPALA-7076 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Fredy Wijaya >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-7705) Impala 2.13 & 3.1 Docs: ALTER DATABASE SET OWNER
[ https://issues.apache.org/jira/browse/IMPALA-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7705. --- Resolution: Fixed > Impala 2.13 & 3.1 Docs: ALTER DATABASE SET OWNER > > > Key: IMPALA-7705 > URL: https://issues.apache.org/jira/browse/IMPALA-7705 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > > ALTER DATABASE SET OWNER https://issues.apache.org/jira/browse/IMPALA-7016 > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7743) Impala 3.1 Doc: Document the option to load incremental statistics from catalog
[ https://issues.apache.org/jira/browse/IMPALA-7743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7743. --- Resolution: Fixed > Impala 3.1 Doc: Document the option to load incremental statistics from > catalog > --- > > Key: IMPALA-7743 > URL: https://issues.apache.org/jira/browse/IMPALA-7743 > Project: IMPALA > Issue Type: Sub-task >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11790/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-6919) Impala 3.1 Doc: Doc the COMMENT ON statements
[ https://issues.apache.org/jira/browse/IMPALA-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-6919. --- Resolution: Fixed > Impala 3.1 Doc: Doc the COMMENT ON statements > - > > Key: IMPALA-6919 > URL: https://issues.apache.org/jira/browse/IMPALA-6919 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 2.13.0, Impala 3.1.0 >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11370/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7195) Impala 3.1 Doc: Proxy user list should support groups
[ https://issues.apache.org/jira/browse/IMPALA-7195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7195. --- Resolution: Fixed > Impala 3.1 Doc: Proxy user list should support groups > - > > Key: IMPALA-7195 > URL: https://issues.apache.org/jira/browse/IMPALA-7195 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11068/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7634) Impala 3.1 Doc: Doc the command to gracefully shutdown Impala
[ https://issues.apache.org/jira/browse/IMPALA-7634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7634. --- Resolution: Fixed > Impala 3.1 Doc: Doc the command to gracefully shutdown Impala > - > > Key: IMPALA-7634 > URL: https://issues.apache.org/jira/browse/IMPALA-7634 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 3.1.0 >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11872/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7392) Document SCAN_BYTES_LIMIT
[ https://issues.apache.org/jira/browse/IMPALA-7392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7392. --- Resolution: Fixed > Document SCAN_BYTES_LIMIT > - > > Key: IMPALA-7392 > URL: https://issues.apache.org/jira/browse/IMPALA-7392 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Tim Armstrong >Assignee: Alex Rodoni >Priority: Major > Labels: docs, resource-management > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11240/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7218) Impala 3.1 Doc: Allow Column Definitions in ALTER VIEW
[ https://issues.apache.org/jira/browse/IMPALA-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7218. --- Resolution: Fixed > Impala 3.1 Doc: Allow Column Definitions in ALTER VIEW > -- > > Key: IMPALA-7218 > URL: https://issues.apache.org/jira/browse/IMPALA-7218 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7123) Impala 3.1 or 4.0 Doc: Restrict Impala to only support timezones that work in Hive (IANA + Java)
[ https://issues.apache.org/jira/browse/IMPALA-7123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7123. --- Resolution: Fixed > Impala 3.1 or 4.0 Doc: Restrict Impala to only support timezones that work in > Hive (IANA + Java) > > > Key: IMPALA-7123 > URL: https://issues.apache.org/jira/browse/IMPALA-7123 > Project: IMPALA > Issue Type: Task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-7431) Impala 3.1 Doc: Make METASTORE_DB configurable and default to escaped $IMPALA_HOME
[ https://issues.apache.org/jira/browse/IMPALA-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7431. --- Resolution: Fixed > Impala 3.1 Doc: Make METASTORE_DB configurable and default to escaped > $IMPALA_HOME > -- > > Key: IMPALA-7431 > URL: https://issues.apache.org/jira/browse/IMPALA-7431 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-7806) Impala 3.1 Doc: Check the existing known issues against 3.1 fixes
[ https://issues.apache.org/jira/browse/IMPALA-7806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7806. --- Resolution: Fixed > Impala 3.1 Doc: Check the existing known issues against 3.1 fixes > - > > Key: IMPALA-7806 > URL: https://issues.apache.org/jira/browse/IMPALA-7806 > Project: IMPALA > Issue Type: Task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11921/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-7789) Impala 3.1 Doc: Admission Control Status in Impala Shell
[ https://issues.apache.org/jira/browse/IMPALA-7789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7789. --- Resolution: Fixed > Impala 3.1 Doc: Admission Control Status in Impala Shell > > > Key: IMPALA-7789 > URL: https://issues.apache.org/jira/browse/IMPALA-7789 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11895/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IMPALA-7434) Impala 2.12 Doc: Kudu's kinit does not support auth_to_local rules with Heimdal kerberos
[ https://issues.apache.org/jira/browse/IMPALA-7434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni updated IMPALA-7434: Labels: (was: future_release_doc) > Impala 2.12 Doc: Kudu's kinit does not support auth_to_local rules with > Heimdal kerberos > > > Key: IMPALA-7434 > URL: https://issues.apache.org/jira/browse/IMPALA-7434 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11204/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-7836) Impala 3.1 Doc: New query option 'topn_bytes_limit' for TopN to Sort conversion
[ https://issues.apache.org/jira/browse/IMPALA-7836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni updated IMPALA-7836: Labels: (was: future_release_doc) > Impala 3.1 Doc: New query option 'topn_bytes_limit' for TopN to Sort > conversion > --- > > Key: IMPALA-7836 > URL: https://issues.apache.org/jira/browse/IMPALA-7836 > Project: IMPALA > Issue Type: Sub-task > Components: Docs, Frontend >Affects Versions: Impala 2.9.0 >Reporter: Sahil Takiar >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > IMPALA-5004 adds a new query level option called 'topn_bytes_limit' that we > should document. The changes in IMPALA-5004 work by estimating the amount of > memory required to run a TopN operator. The memory estimate is based on the > size of the individual tuples that need to be processed by the TopN operator, > as well as the sum of the limit and offset in the query. TopN operators don't > spill to disk so they have to keep all rows they process in memory. > If the estimated size of the working set of the TopN operator exceeds the > threshold of 'topn_bytes_limit' the TopN operator will be replaced with a > Sort operator. The Sort operator can spill to disk, but it processes all the > data (the limit and offset have no affect). So switching to Sort might incur > performance penalties, but it will require less memory. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-6919) Impala 3.1 Doc: Doc the COMMENT ON statements
[ https://issues.apache.org/jira/browse/IMPALA-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni updated IMPALA-6919: Labels: (was: future_release_doc) > Impala 3.1 Doc: Doc the COMMENT ON statements > - > > Key: IMPALA-6919 > URL: https://issues.apache.org/jira/browse/IMPALA-6919 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 2.13.0, Impala 3.1.0 >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11370/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-7614) Impala 3.1 Doc: Document the New Invalidate Options
[
https://issues.apache.org/jira/browse/IMPALA-7614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rodoni updated IMPALA-7614:
Labels: (was: future_release_doc)
> Impala 3.1 Doc: Document the New Invalidate Options
> ---
>
> Key: IMPALA-7614
> URL: https://issues.apache.org/jira/browse/IMPALA-7614
> Project: IMPALA
> Issue Type: Task
> Components: Docs
>Reporter: Alex Rodoni
>Assignee: Alex Rodoni
>Priority: Major
> Fix For: Impala 3.1.0
>
>
> Document the new options:
> - invalidate_tables_timeout_s
> - invalidate_tables_on_memory_pressure{quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-7432) Impala 3.1 Doc: Add logged_in_user alias for effective_user
[ https://issues.apache.org/jira/browse/IMPALA-7432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni updated IMPALA-7432: Labels: (was: future_release_doc) > Impala 3.1 Doc: Add logged_in_user alias for effective_user > --- > > Key: IMPALA-7432 > URL: https://issues.apache.org/jira/browse/IMPALA-7432 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11755/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-7743) Impala 3.1 Doc: Document the option to load incremental statistics from catalog
[ https://issues.apache.org/jira/browse/IMPALA-7743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni updated IMPALA-7743: Labels: (was: future_release_doc) > Impala 3.1 Doc: Document the option to load incremental statistics from > catalog > --- > > Key: IMPALA-7743 > URL: https://issues.apache.org/jira/browse/IMPALA-7743 > Project: IMPALA > Issue Type: Sub-task >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11790/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-7206) Doc THREAD_RESERVATION_LIMIT
[ https://issues.apache.org/jira/browse/IMPALA-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni updated IMPALA-7206: Labels: (was: future_release_doc) > Doc THREAD_RESERVATION_LIMIT > > > Key: IMPALA-7206 > URL: https://issues.apache.org/jira/browse/IMPALA-7206 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11237/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-7103) Impala 3.1 Doc: Query option to enable EC
[ https://issues.apache.org/jira/browse/IMPALA-7103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni updated IMPALA-7103: Labels: (was: future_release_doc) > Impala 3.1 Doc: Query option to enable EC > - > > Key: IMPALA-7103 > URL: https://issues.apache.org/jira/browse/IMPALA-7103 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11855/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-7195) Impala 3.1 Doc: Proxy user list should support groups
[ https://issues.apache.org/jira/browse/IMPALA-7195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni updated IMPALA-7195: Labels: (was: future_release_doc) > Impala 3.1 Doc: Proxy user list should support groups > - > > Key: IMPALA-7195 > URL: https://issues.apache.org/jira/browse/IMPALA-7195 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.1.0 > > > https://gerrit.cloudera.org/#/c/11068/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
