[jira] [Comment Edited] (IMPALA-7369) Implement DATE builtin functions
[ https://issues.apache.org/jira/browse/IMPALA-7369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16899330#comment-16899330 ] Alex Rodoni edited comment on IMPALA-7369 at 8/3/19 2:37 AM: - [~attilaj] I am not able to execute the following functions on nightly7 build - neither with TIMESTAMP or DATE. And they are not documented currently even for TIMESTAMP. DATE ADD_YEARS(DATE d, INT/BIGINT num_years), DATE SUB_YEARS(DATE d, INT/BIGINT num_years) DATE SUB_MONTH(...) DATE ADD_DAYS(DATE d, INT/BIGINT num_days), DATE SUB_DAYS(DATE d, INT/BIGINT num_days) DATE ADD_WEEKS(DATE d, INT/BIGINT num_weeks), DATE SUB_WEEKS(DATE d, INT/BIGINT num_weeks) was (Author: arodoni_cloudera): [~attilaj] I am not able to execute the following functions on nightly7 build - neither with TIMESTAMP or DATE. And they are not documented currently even for TIMESTAMP. DATE ADD_YEARS(DATE d, INT/BIGINT num_years), DATE SUB_YEARS(DATE d, INT/BIGINT num_years) DATE ADD_DAYS(DATE d, INT/BIGINT num_days), DATE SUB_DAYS(DATE d, INT/BIGINT num_days) DATE ADD_WEEKS(DATE d, INT/BIGINT num_weeks), DATE SUB_WEEKS(DATE d, INT/BIGINT num_weeks) > Implement DATE builtin functions > > > Key: IMPALA-7369 > URL: https://issues.apache.org/jira/browse/IMPALA-7369 > Project: IMPALA > Issue Type: Sub-task >Reporter: Attila Jeges >Assignee: Attila Jeges >Priority: Major > Fix For: Impala 3.3.0 > > > - Built-in functions supported in Hive should be implemented in Impala es > well. > - Already implemented TIMESTAMP built-in functions that work on the date part > of timestamps should be implemented for DATE types too. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-7369) Implement DATE builtin functions
[ https://issues.apache.org/jira/browse/IMPALA-7369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16899330#comment-16899330 ] Alex Rodoni commented on IMPALA-7369: - [~attilaj] I am not able to execute the following functions on nightly7 build - neither with TIMESTAMP or DATE. And they are not documented currently even for TIMESTAMP. DATE ADD_YEARS(DATE d, INT/BIGINT num_years), DATE SUB_YEARS(DATE d, INT/BIGINT num_years) DATE ADD_DAYS(DATE d, INT/BIGINT num_days), DATE SUB_DAYS(DATE d, INT/BIGINT num_days) DATE ADD_WEEKS(DATE d, INT/BIGINT num_weeks), DATE SUB_WEEKS(DATE d, INT/BIGINT num_weeks) > Implement DATE builtin functions > > > Key: IMPALA-7369 > URL: https://issues.apache.org/jira/browse/IMPALA-7369 > Project: IMPALA > Issue Type: Sub-task >Reporter: Attila Jeges >Assignee: Attila Jeges >Priority: Major > Fix For: Impala 3.3.0 > > > - Built-in functions supported in Hive should be implemented in Impala es > well. > - Already implemented TIMESTAMP built-in functions that work on the date part > of timestamps should be implemented for DATE types too. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-8829) Document limitation of parsing memory string
[
https://issues.apache.org/jira/browse/IMPALA-8829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16899302#comment-16899302
]
Alex Rodoni commented on IMPALA-8829:
-
I grep'ed for "TB" in the docs, and did not find any other examples using "TB".
> Document limitation of parsing memory string
>
>
> Key: IMPALA-8829
> URL: https://issues.apache.org/jira/browse/IMPALA-8829
> Project: IMPALA
> Issue Type: Task
> Components: Docs
>Affects Versions: Impala 3.1.0, Impala 3.2.0, Impala 3.3.0
>Reporter: Michael Ho
>Assignee: Alex Rodoni
>Priority: Major
>
> During review of https://gerrit.cloudera.org/#/c/13986/, [~tarmstrong] found
> that {{ParseUtil::ParseMemSpec()}} doesn't support parsing strings with "TB"
> in it. We may want to document this limitation in older version so that users
> won't specify "TB" in startup flags. Off the top of my head, the scratch
> space and data cache are probably affected. Any memory limits related flags
> may also be affected.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Work started] (IMPALA-8829) Document limitation of parsing memory string
[
https://issues.apache.org/jira/browse/IMPALA-8829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on IMPALA-8829 started by Alex Rodoni.
---
> Document limitation of parsing memory string
>
>
> Key: IMPALA-8829
> URL: https://issues.apache.org/jira/browse/IMPALA-8829
> Project: IMPALA
> Issue Type: Task
> Components: Docs
>Affects Versions: Impala 3.1.0, Impala 3.2.0, Impala 3.3.0
>Reporter: Michael Ho
>Assignee: Alex Rodoni
>Priority: Major
>
> During review of https://gerrit.cloudera.org/#/c/13986/, [~tarmstrong] found
> that {{ParseUtil::ParseMemSpec()}} doesn't support parsing strings with "TB"
> in it. We may want to document this limitation in older version so that users
> won't specify "TB" in startup flags. Off the top of my head, the scratch
> space and data cache are probably affected. Any memory limits related flags
> may also be affected.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-8829) Document limitation of parsing memory string
[
https://issues.apache.org/jira/browse/IMPALA-8829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16899299#comment-16899299
]
Michael Ho commented on IMPALA-8829:
May also need to update any existing doc with "TB" in the example.
> Document limitation of parsing memory string
>
>
> Key: IMPALA-8829
> URL: https://issues.apache.org/jira/browse/IMPALA-8829
> Project: IMPALA
> Issue Type: Task
> Components: Docs
>Affects Versions: Impala 3.1.0, Impala 3.2.0, Impala 3.3.0
>Reporter: Michael Ho
>Assignee: Alex Rodoni
>Priority: Major
>
> During review of https://gerrit.cloudera.org/#/c/13986/, [~tarmstrong] found
> that {{ParseUtil::ParseMemSpec()}} doesn't support parsing strings with "TB"
> in it. We may want to document this limitation in older version so that users
> won't specify "TB" in startup flags. Off the top of my head, the scratch
> space and data cache are probably affected. Any memory limits related flags
> may also be affected.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Created] (IMPALA-8829) Document limitation of parsing memory string
Michael Ho created IMPALA-8829:
--
Summary: Document limitation of parsing memory string
Key: IMPALA-8829
URL: https://issues.apache.org/jira/browse/IMPALA-8829
Project: IMPALA
Issue Type: Task
Components: Docs
Affects Versions: Impala 3.2.0, Impala 3.1.0, Impala 3.3.0
Reporter: Michael Ho
Assignee: Alex Rodoni
During review of https://gerrit.cloudera.org/#/c/13986/, [~tarmstrong] found
that {{ParseUtil::ParseMemSpec(}} doesn't support parsing strings with "TB" in
it. We may want to document this limitation in older version so that users
won't specify "TB" in startup flags. Off the top of my head, the scratch space
and data cache are probably affected. Any memory limits related flags may also
be affected.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-8829) Document limitation of parsing memory string
[
https://issues.apache.org/jira/browse/IMPALA-8829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-8829:
---
Description: During review of https://gerrit.cloudera.org/#/c/13986/,
[~tarmstrong] found that {{ParseUtil::ParseMemSpec()}} doesn't support parsing
strings with "TB" in it. We may want to document this limitation in older
version so that users won't specify "TB" in startup flags. Off the top of my
head, the scratch space and data cache are probably affected. Any memory limits
related flags may also be affected. (was: During review of
https://gerrit.cloudera.org/#/c/13986/, [~tarmstrong] found that
{{ParseUtil::ParseMemSpec(}} doesn't support parsing strings with "TB" in it.
We may want to document this limitation in older version so that users won't
specify "TB" in startup flags. Off the top of my head, the scratch space and
data cache are probably affected. Any memory limits related flags may also be
affected.)
> Document limitation of parsing memory string
>
>
> Key: IMPALA-8829
> URL: https://issues.apache.org/jira/browse/IMPALA-8829
> Project: IMPALA
> Issue Type: Task
> Components: Docs
>Affects Versions: Impala 3.1.0, Impala 3.2.0, Impala 3.3.0
>Reporter: Michael Ho
>Assignee: Alex Rodoni
>Priority: Major
>
> During review of https://gerrit.cloudera.org/#/c/13986/, [~tarmstrong] found
> that {{ParseUtil::ParseMemSpec()}} doesn't support parsing strings with "TB"
> in it. We may want to document this limitation in older version so that users
> won't specify "TB" in startup flags. Off the top of my head, the scratch
> space and data cache are probably affected. Any memory limits related flags
> may also be affected.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Created] (IMPALA-8829) Document limitation of parsing memory string
Michael Ho created IMPALA-8829:
--
Summary: Document limitation of parsing memory string
Key: IMPALA-8829
URL: https://issues.apache.org/jira/browse/IMPALA-8829
Project: IMPALA
Issue Type: Task
Components: Docs
Affects Versions: Impala 3.2.0, Impala 3.1.0, Impala 3.3.0
Reporter: Michael Ho
Assignee: Alex Rodoni
During review of https://gerrit.cloudera.org/#/c/13986/, [~tarmstrong] found
that {{ParseUtil::ParseMemSpec(}} doesn't support parsing strings with "TB" in
it. We may want to document this limitation in older version so that users
won't specify "TB" in startup flags. Off the top of my head, the scratch space
and data cache are probably affected. Any memory limits related flags may also
be affected.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (IMPALA-8803) Coordinator should release admitted memory per-backend rather than per-query
[
https://issues.apache.org/jira/browse/IMPALA-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16899281#comment-16899281
]
Tim Armstrong commented on IMPALA-8803:
---
Yeah, I think there are some queries that fan-in so backends would go idle
earlier. Our scheduler isn't really very smart about this now, but could be
smarter in future. So I think that's a nice optimisation. I think I agree with
your thought process about the batching, I don't think it needs to be totally
optimal, but having a log() bound on it is nice.
> Coordinator should release admitted memory per-backend rather than per-query
>
>
> Key: IMPALA-8803
> URL: https://issues.apache.org/jira/browse/IMPALA-8803
> Project: IMPALA
> Issue Type: Sub-task
>Reporter: Sahil Takiar
>Assignee: Sahil Takiar
>Priority: Major
>
> When {{SPOOL_QUERY_RESULTS}} is true, the coordinator backend may be long
> lived, even though all other backends for the query have completed.
> Currently, the Coordinator only releases admitted memory when the entire
> query has completed (include the coordinator fragment) -
> https://github.com/apache/impala/blob/72c9370856d7436885adbee3e8da7e7d9336df15/be/src/runtime/coordinator.cc#L562
> In order to more aggressively return admitted memory, the coordinator should
> release memory when each backend for a query completes, rather than waiting
> for the entire query to complete.
> Releasing memory per backend should be batched because releasing admitted
> memory in the admission controller requires obtaining a global lock and
> refreshing the internal stats of the admission controller. Batching will help
> mitigate any additional overhead from releasing admitted memory per backend.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-8456) Impala Doc: Document HTTP based HS2/beeswax endpoints on coordinators
[ https://issues.apache.org/jira/browse/IMPALA-8456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16899248#comment-16899248 ] ASF subversion and git services commented on IMPALA-8456: - Commit f5c593ae85d18db1f8eca15b6b9c2a86ffd5eea8 in impala's branch refs/heads/master from Alex Rodoni [ https://gitbox.apache.org/repos/asf?p=impala.git;h=f5c593a ] IMPALA-8456: [DOCS] New HTTP protocol for Impala clients Change-Id: I3101f8babc77a5a872778499a54ac479a66ad996 Reviewed-on: http://gerrit.cloudera.org:8080/13960 Tested-by: Impala Public Jenkins Reviewed-by: Bharath Vissapragada > Impala Doc: Document HTTP based HS2/beeswax endpoints on coordinators > - > > Key: IMPALA-8456 > URL: https://issues.apache.org/jira/browse/IMPALA-8456 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Labels: future_release_doc, in_33 > Fix For: Impala 3.3.0 > > > Also document IMPALA-8717 > https://issues.apache.org/jira/browse/IMPALA-8783 -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-8814) Impala Doc: Webui and SPNEGO
[ https://issues.apache.org/jira/browse/IMPALA-8814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16899249#comment-16899249 ] ASF subversion and git services commented on IMPALA-8814: - Commit 2450cd49b6f2dbd6b73c210a2f000d427572d245 in impala's branch refs/heads/master from Alex Rodoni [ https://gitbox.apache.org/repos/asf?p=impala.git;h=2450cd4 ] IMPALA-8814: [DOCS] Document the SPNEGO support for Impala Web UIs Change-Id: I3cbf1265bf6b897d2728ecb9446a07b1c34a576e Reviewed-on: http://gerrit.cloudera.org:8080/13958 Tested-by: Impala Public Jenkins Reviewed-by: Thomas Tauber-Marshall > Impala Doc: Webui and SPNEGO > > > Key: IMPALA-8814 > URL: https://issues.apache.org/jira/browse/IMPALA-8814 > Project: IMPALA > Issue Type: Task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Labels: future_release_doc, in_33 > Fix For: Impala 3.3.0 > > > https://gerrit.cloudera.org/#/c/13774/ > Doc review at: https://gerrit.cloudera.org/#/c/13958/ -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-8814) Impala Doc: Webui and SPNEGO
[ https://issues.apache.org/jira/browse/IMPALA-8814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-8814. --- Resolution: Fixed Fix Version/s: Impala 3.3.0 > Impala Doc: Webui and SPNEGO > > > Key: IMPALA-8814 > URL: https://issues.apache.org/jira/browse/IMPALA-8814 > Project: IMPALA > Issue Type: Task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Labels: future_release_doc, in_33 > Fix For: Impala 3.3.0 > > > https://gerrit.cloudera.org/#/c/13774/ > Doc review at: https://gerrit.cloudera.org/#/c/13958/ -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-8814) Impala Doc: Webui and SPNEGO
[ https://issues.apache.org/jira/browse/IMPALA-8814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-8814. --- Resolution: Fixed Fix Version/s: Impala 3.3.0 > Impala Doc: Webui and SPNEGO > > > Key: IMPALA-8814 > URL: https://issues.apache.org/jira/browse/IMPALA-8814 > Project: IMPALA > Issue Type: Task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Labels: future_release_doc, in_33 > Fix For: Impala 3.3.0 > > > https://gerrit.cloudera.org/#/c/13774/ > Doc review at: https://gerrit.cloudera.org/#/c/13958/ -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Closed] (IMPALA-8456) Impala Doc: Document HTTP based HS2/beeswax endpoints on coordinators
[ https://issues.apache.org/jira/browse/IMPALA-8456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-8456. --- Resolution: Fixed Fix Version/s: Impala 3.3.0 > Impala Doc: Document HTTP based HS2/beeswax endpoints on coordinators > - > > Key: IMPALA-8456 > URL: https://issues.apache.org/jira/browse/IMPALA-8456 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Labels: future_release_doc, in_33 > Fix For: Impala 3.3.0 > > > Also document IMPALA-8717 > https://issues.apache.org/jira/browse/IMPALA-8783 -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-8456) Impala Doc: Document HTTP based HS2/beeswax endpoints on coordinators
[ https://issues.apache.org/jira/browse/IMPALA-8456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-8456. --- Resolution: Fixed Fix Version/s: Impala 3.3.0 > Impala Doc: Document HTTP based HS2/beeswax endpoints on coordinators > - > > Key: IMPALA-8456 > URL: https://issues.apache.org/jira/browse/IMPALA-8456 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Labels: future_release_doc, in_33 > Fix For: Impala 3.3.0 > > > Also document IMPALA-8717 > https://issues.apache.org/jira/browse/IMPALA-8783 -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (IMPALA-2019) Proper UTF-8 support in string functions
[ https://issues.apache.org/jira/browse/IMPALA-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16899180#comment-16899180 ] Tim Armstrong commented on IMPALA-2019: --- Returning the length in bytes is currently the expected behaviour. Agree that UTF-8 support would be great. > Proper UTF-8 support in string functions > > > Key: IMPALA-2019 > URL: https://issues.apache.org/jira/browse/IMPALA-2019 > Project: IMPALA > Issue Type: New Feature > Components: Backend >Affects Versions: Impala 2.1, Impala 2.2 >Reporter: Andrés Cordero >Priority: Minor > Labels: sql-language > > As documented here: > http://www.cloudera.com/content/cloudera/en/documentation/cloudera-impala/latest/topics/impala_string.html > Impala does not properly handle non-ASCII UTF-8 characters, and will return > results in string functions such as length that are inconsistent with Hive. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Created] (IMPALA-8828) Support impersonation via http paths
Thomas Tauber-Marshall created IMPALA-8828: -- Summary: Support impersonation via http paths Key: IMPALA-8828 URL: https://issues.apache.org/jira/browse/IMPALA-8828 Project: IMPALA Issue Type: Improvement Components: Clients Affects Versions: Impala 3.3.0 Reporter: Thomas Tauber-Marshall Assignee: Thomas Tauber-Marshall When clients connect over http, we should allow them to perform impersonation via the 'doAs' parameter, eg. by specifying a path of the form '/?doAs=' This is useful for example for Apache Knox, which proxies connections to Impala and authenticates as itself via Kerberos but runs queries as other users. We can leverage the existing support for impersonation, eg. knox would have to be included in 'authorized_proxy_user_config' to be able to do the impersonation -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IMPALA-8828) Support impersonation via http paths
Thomas Tauber-Marshall created IMPALA-8828: -- Summary: Support impersonation via http paths Key: IMPALA-8828 URL: https://issues.apache.org/jira/browse/IMPALA-8828 Project: IMPALA Issue Type: Improvement Components: Clients Affects Versions: Impala 3.3.0 Reporter: Thomas Tauber-Marshall Assignee: Thomas Tauber-Marshall When clients connect over http, we should allow them to perform impersonation via the 'doAs' parameter, eg. by specifying a path of the form '/?doAs=' This is useful for example for Apache Knox, which proxies connections to Impala and authenticates as itself via Kerberos but runs queries as other users. We can leverage the existing support for impersonation, eg. knox would have to be included in 'authorized_proxy_user_config' to be able to do the impersonation -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Work started] (IMPALA-8376) Add per-directory limits for scratch disk usage
[
https://issues.apache.org/jira/browse/IMPALA-8376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on IMPALA-8376 started by Tim Armstrong.
-
> Add per-directory limits for scratch disk usage
> ---
>
> Key: IMPALA-8376
> URL: https://issues.apache.org/jira/browse/IMPALA-8376
> Project: IMPALA
> Issue Type: Sub-task
> Components: Backend
>Reporter: Tim Armstrong
>Assignee: Tim Armstrong
>Priority: Major
> Labels: resource-management
>
> The current syntax is:
> {noformat}
> --scratch_dirs=/data/1/impala/impalad,/data/10/impala/impalad,/data/11/impala/impalad,/data/2/impala/impalad,/data/3/impala/impalad,/data/4/impala/impalad,/data/5/impala/impalad,/data/6/impala/impalad,/data/7/impala/impalad,/data/8/impala/impalad,/data/9/impala/impalad,/data/12/impala/impalad
> {noformat}
> The current syntax for the data cache is
> {noformat}
> --data_cache_dir=/tmp --data_cache_size=500MB
> {noformat}
> One idea is to allow optionally specifying the limit after each directory:
> {noformat}
> --scratch_dirs=/data/1/impala/impalad:500MB,/data/10/impala/impalad:2GB,/data/11/impala/impalad
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-8817) TestTestcaseBuilder broken on S3
[
https://issues.apache.org/jira/browse/IMPALA-8817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong updated IMPALA-8817:
--
Labels: broken-build (was: )
> TestTestcaseBuilder broken on S3
>
>
> Key: IMPALA-8817
> URL: https://issues.apache.org/jira/browse/IMPALA-8817
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
>Affects Versions: Impala 3.3.0
>Reporter: Csaba Ringhofer
>Assignee: Csaba Ringhofer
>Priority: Major
> Labels: broken-build
> Fix For: Impala 3.3.0
>
>
> metadata.test_testcase_builder.TestTestcaseBuilder.test_query_without_from
> fails with the following stack trace in S3 environment:
> {code}
> metadata/test_testcase_builder.py:41: in test_query_without_from
> result = self.execute_query_expect_success(self.client,
> testcase_generate_query)
> common/impala_test_suite.py:700: in wrapper
> return function(*args, **kwargs)
> common/impala_test_suite.py:708: in execute_query_expect_success
> result = cls.__execute_query(impalad_client, query, query_options, user)
> common/impala_test_suite.py:802: in __execute_query
> return impalad_client.execute(query, user=user)
> common/impala_connection.py:184: in execute
> return self.__beeswax_client.execute(sql_stmt, user=user)
> beeswax/impala_beeswax.py:187: in execute
> handle = self.__execute_query(query_string.strip(), user=user)
> beeswax/impala_beeswax.py:362: in __execute_query
> handle = self.execute_query_async(query_string, user=user)
> beeswax/impala_beeswax.py:356: in execute_query_async
> handle = self.__do_rpc(lambda: self.imp_service.query(query,))
> beeswax/impala_beeswax.py:519: in __do_rpc
> raise ImpalaBeeswaxException(self.__build_error_message(b), b)
> E ImpalaBeeswaxException: ImpalaBeeswaxException:
> EINNER EXCEPTION:
> EMESSAGE: AnalysisException: Incomplete HDFS URI, no host: hdfs:///tmp
> E CAUSED BY: IOException: Incomplete HDFS URI, no host: hdfs:///tmp
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Assigned] (IMPALA-8826) Impala Doc: Add docs for PLAN_ROOT_SINK and result spooling
[
https://issues.apache.org/jira/browse/IMPALA-8826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rodoni reassigned IMPALA-8826:
---
Assignee: Alex Rodoni
> Impala Doc: Add docs for PLAN_ROOT_SINK and result spooling
> ---
>
> Key: IMPALA-8826
> URL: https://issues.apache.org/jira/browse/IMPALA-8826
> Project: IMPALA
> Issue Type: Sub-task
> Components: Docs
>Reporter: Sahil Takiar
>Assignee: Alex Rodoni
>Priority: Major
> Labels: future_release_doc
>
> Currently, I don't see many docs explaining what a {{PLAN_ROOT_SINK}} is,
> even though it shows up in explain plans and runtime profiles. After more of
> the changes in IMPALA-8656 are merged, understanding what {{PLAN_ROOT_SINK}}
> is will be more important, because it will start taking up a memory
> reservation and possibly spilling to disk.
> I don't see any docs on data sinks in general, so perhaps it would be useful
> to create a dedicated page for explaining data sinks and how they work. We
> can start by documenting the {{PLAN_ROOT_SINK}} as that may be the most
> commonly used one.
> We should document all the changes being made in IMPALA-8656 as well.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-8826) Impala Doc: Add docs for PLAN_ROOT_SINK and result spooling
[
https://issues.apache.org/jira/browse/IMPALA-8826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16899079#comment-16899079
]
Alex Rodoni commented on IMPALA-8826:
-
Thank you [~stakiar]! I am assigning this to myself to keep track. Is this for
3.3?
> Impala Doc: Add docs for PLAN_ROOT_SINK and result spooling
> ---
>
> Key: IMPALA-8826
> URL: https://issues.apache.org/jira/browse/IMPALA-8826
> Project: IMPALA
> Issue Type: Sub-task
> Components: Docs
>Reporter: Sahil Takiar
>Assignee: Alex Rodoni
>Priority: Major
> Labels: future_release_doc
>
> Currently, I don't see many docs explaining what a {{PLAN_ROOT_SINK}} is,
> even though it shows up in explain plans and runtime profiles. After more of
> the changes in IMPALA-8656 are merged, understanding what {{PLAN_ROOT_SINK}}
> is will be more important, because it will start taking up a memory
> reservation and possibly spilling to disk.
> I don't see any docs on data sinks in general, so perhaps it would be useful
> to create a dedicated page for explaining data sinks and how they work. We
> can start by documenting the {{PLAN_ROOT_SINK}} as that may be the most
> commonly used one.
> We should document all the changes being made in IMPALA-8656 as well.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-8826) Impala Doc: Add docs for PLAN_ROOT_SINK and result spooling
[
https://issues.apache.org/jira/browse/IMPALA-8826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rodoni updated IMPALA-8826:
Labels: future_release_doc (was: )
> Impala Doc: Add docs for PLAN_ROOT_SINK and result spooling
> ---
>
> Key: IMPALA-8826
> URL: https://issues.apache.org/jira/browse/IMPALA-8826
> Project: IMPALA
> Issue Type: Sub-task
> Components: Docs
>Reporter: Sahil Takiar
>Priority: Major
> Labels: future_release_doc
>
> Currently, I don't see many docs explaining what a {{PLAN_ROOT_SINK}} is,
> even though it shows up in explain plans and runtime profiles. After more of
> the changes in IMPALA-8656 are merged, understanding what {{PLAN_ROOT_SINK}}
> is will be more important, because it will start taking up a memory
> reservation and possibly spilling to disk.
> I don't see any docs on data sinks in general, so perhaps it would be useful
> to create a dedicated page for explaining data sinks and how they work. We
> can start by documenting the {{PLAN_ROOT_SINK}} as that may be the most
> commonly used one.
> We should document all the changes being made in IMPALA-8656 as well.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-8738) Add a column representing the type（table or view） in the show tables output
[
https://issues.apache.org/jira/browse/IMPALA-8738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16899070#comment-16899070
]
Thomas Tauber-Marshall commented on IMPALA-8738:
Sure, that sounds good.
> Add a column representing the type（table or view） in the show tables output
> ---
>
> Key: IMPALA-8738
> URL: https://issues.apache.org/jira/browse/IMPALA-8738
> Project: IMPALA
> Issue Type: Improvement
> Components: Catalog, Frontend
>Reporter: baotuquan
>Assignee: baotuquan
>Priority: Minor
> Labels: features
>
> Now the output of the +*show tables*+ command in the system is as follows：
> {code:java}
> default> show tables;
> Query: show tables
> +--+
> | name |
> +--+
> | table1 |
> | view1 |
> +--+
> {code}
> I think we should add a column for the representation type，The output should
> be like this
> {code:java}
> default> show tables;
> Query: show tables
> +---+
> | name | type |
> ++
> | table1 | table |
> | view1 | view |
> ++
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Comment Edited] (IMPALA-2019) Proper UTF-8 support in string functions
[ https://issues.apache.org/jira/browse/IMPALA-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16899033#comment-16899033 ] Matthew Ropp edited comment on IMPALA-2019 at 8/2/19 4:48 PM: -- Agree 100% this should not be considered a minor issue. Proper UTF-8 support should be part and parcel of any modern database or data platform! was (Author: mropp): Agree 100% this should not be consider a minor issue. Proper UTF-8 support should be part and parcel of any modern database or data platform! > Proper UTF-8 support in string functions > > > Key: IMPALA-2019 > URL: https://issues.apache.org/jira/browse/IMPALA-2019 > Project: IMPALA > Issue Type: New Feature > Components: Backend >Affects Versions: Impala 2.1, Impala 2.2 >Reporter: Andrés Cordero >Priority: Minor > Labels: sql-language > > As documented here: > http://www.cloudera.com/content/cloudera/en/documentation/cloudera-impala/latest/topics/impala_string.html > Impala does not properly handle non-ASCII UTF-8 characters, and will return > results in string functions such as length that are inconsistent with Hive. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-2019) Proper UTF-8 support in string functions
[ https://issues.apache.org/jira/browse/IMPALA-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16899033#comment-16899033 ] Matthew Ropp commented on IMPALA-2019: -- Agree 100% this should not be consider a minor issue. Proper UTF-8 support should be part and parcel of any modern database or data platform! > Proper UTF-8 support in string functions > > > Key: IMPALA-2019 > URL: https://issues.apache.org/jira/browse/IMPALA-2019 > Project: IMPALA > Issue Type: New Feature > Components: Backend >Affects Versions: Impala 2.1, Impala 2.2 >Reporter: Andrés Cordero >Priority: Minor > Labels: sql-language > > As documented here: > http://www.cloudera.com/content/cloudera/en/documentation/cloudera-impala/latest/topics/impala_string.html > Impala does not properly handle non-ASCII UTF-8 characters, and will return > results in string functions such as length that are inconsistent with Hive. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Created] (IMPALA-8827) Create tests for Hive stats interop in ACID tables
Csaba Ringhofer created IMPALA-8827: --- Summary: Create tests for Hive stats interop in ACID tables Key: IMPALA-8827 URL: https://issues.apache.org/jira/browse/IMPALA-8827 Project: IMPALA Issue Type: Improvement Components: Infrastructure Affects Versions: Impala 3.3.0 Reporter: Csaba Ringhofer Hive started to use stats to answer some queries in ACID tables. Some tests should check what happens if Hive uses stats computed by Impala. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Created] (IMPALA-8827) Create tests for Hive stats interop in ACID tables
Csaba Ringhofer created IMPALA-8827: --- Summary: Create tests for Hive stats interop in ACID tables Key: IMPALA-8827 URL: https://issues.apache.org/jira/browse/IMPALA-8827 Project: IMPALA Issue Type: Improvement Components: Infrastructure Affects Versions: Impala 3.3.0 Reporter: Csaba Ringhofer Hive started to use stats to answer some queries in ACID tables. Some tests should check what happens if Hive uses stats computed by Impala. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (IMPALA-8826) Impala Doc: Add docs for PLAN_ROOT_SINK
[
https://issues.apache.org/jira/browse/IMPALA-8826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sahil Takiar updated IMPALA-8826:
-
Description:
Currently, I don't see many docs explaining what a {{PLAN_ROOT_SINK}} is, even
though it shows up in explain plans and runtime profiles. After more of the
changes in IMPALA-8656 are merged, understanding what {{PLAN_ROOT_SINK}} is
will be more important, because it will start taking up a memory reservation
and possibly spilling to disk.
I don't see any docs on data sinks in general, so perhaps it would be useful to
create a dedicated page for explaining data sinks and how they work. We can
start by documenting the {{PLAN_ROOT_SINK}} as that may be the most commonly
used one.
We should document all the changes being made in IMPALA-8656 as well.
was:
Currently, I don't see many docs explaining what a {{PLAN_ROOT_SINK}} is, even
though it shows up in explain plans and runtime profiles. After more of the
changes in IMPALA-8656 are merged, understanding what {{PLAN_ROOT_SINK}} is
will be more important, because it will start taking up a memory reservation
and possibly spilling to disk.
I don't see any docs on data sinks in general, so perhaps it would be useful to
create a dedicated page for explaining data sinks and how they work. We can
start by documenting the {{PLAN_ROOT_SINK}} as that may be the most commonly
used one.
> Impala Doc: Add docs for PLAN_ROOT_SINK
> ---
>
> Key: IMPALA-8826
> URL: https://issues.apache.org/jira/browse/IMPALA-8826
> Project: IMPALA
> Issue Type: Sub-task
> Components: Docs
>Reporter: Sahil Takiar
>Priority: Major
>
> Currently, I don't see many docs explaining what a {{PLAN_ROOT_SINK}} is,
> even though it shows up in explain plans and runtime profiles. After more of
> the changes in IMPALA-8656 are merged, understanding what {{PLAN_ROOT_SINK}}
> is will be more important, because it will start taking up a memory
> reservation and possibly spilling to disk.
> I don't see any docs on data sinks in general, so perhaps it would be useful
> to create a dedicated page for explaining data sinks and how they work. We
> can start by documenting the {{PLAN_ROOT_SINK}} as that may be the most
> commonly used one.
> We should document all the changes being made in IMPALA-8656 as well.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-8826) Impala Doc: Add docs for PLAN_ROOT_SINK and result spooling
[
https://issues.apache.org/jira/browse/IMPALA-8826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sahil Takiar updated IMPALA-8826:
-
Summary: Impala Doc: Add docs for PLAN_ROOT_SINK and result spooling (was:
Impala Doc: Add docs for PLAN_ROOT_SINK and BufferedPlanRootSink)
> Impala Doc: Add docs for PLAN_ROOT_SINK and result spooling
> ---
>
> Key: IMPALA-8826
> URL: https://issues.apache.org/jira/browse/IMPALA-8826
> Project: IMPALA
> Issue Type: Sub-task
> Components: Docs
>Reporter: Sahil Takiar
>Priority: Major
>
> Currently, I don't see many docs explaining what a {{PLAN_ROOT_SINK}} is,
> even though it shows up in explain plans and runtime profiles. After more of
> the changes in IMPALA-8656 are merged, understanding what {{PLAN_ROOT_SINK}}
> is will be more important, because it will start taking up a memory
> reservation and possibly spilling to disk.
> I don't see any docs on data sinks in general, so perhaps it would be useful
> to create a dedicated page for explaining data sinks and how they work. We
> can start by documenting the {{PLAN_ROOT_SINK}} as that may be the most
> commonly used one.
> We should document all the changes being made in IMPALA-8656 as well.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-8826) Impala Doc: Add docs for PLAN_ROOT_SINK
[
https://issues.apache.org/jira/browse/IMPALA-8826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16899025#comment-16899025
]
Sahil Takiar commented on IMPALA-8826:
--
CC: [~arodoni_cloudera] FYI - leaving this unassigned for now because I don't
know what content we should put into this yet, but wanted to get it on your
radar
> Impala Doc: Add docs for PLAN_ROOT_SINK
> ---
>
> Key: IMPALA-8826
> URL: https://issues.apache.org/jira/browse/IMPALA-8826
> Project: IMPALA
> Issue Type: Sub-task
> Components: Docs
>Reporter: Sahil Takiar
>Priority: Major
>
> Currently, I don't see many docs explaining what a {{PLAN_ROOT_SINK}} is,
> even though it shows up in explain plans and runtime profiles. After more of
> the changes in IMPALA-8656 are merged, understanding what {{PLAN_ROOT_SINK}}
> is will be more important, because it will start taking up a memory
> reservation and possibly spilling to disk.
> I don't see any docs on data sinks in general, so perhaps it would be useful
> to create a dedicated page for explaining data sinks and how they work. We
> can start by documenting the {{PLAN_ROOT_SINK}} as that may be the most
> commonly used one.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-8826) Impala Doc: Add docs for PLAN_ROOT_SINK and BufferedPlanRootSink
[
https://issues.apache.org/jira/browse/IMPALA-8826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sahil Takiar updated IMPALA-8826:
-
Summary: Impala Doc: Add docs for PLAN_ROOT_SINK and BufferedPlanRootSink
(was: Impala Doc: Add docs for PLAN_ROOT_SINK)
> Impala Doc: Add docs for PLAN_ROOT_SINK and BufferedPlanRootSink
>
>
> Key: IMPALA-8826
> URL: https://issues.apache.org/jira/browse/IMPALA-8826
> Project: IMPALA
> Issue Type: Sub-task
> Components: Docs
>Reporter: Sahil Takiar
>Priority: Major
>
> Currently, I don't see many docs explaining what a {{PLAN_ROOT_SINK}} is,
> even though it shows up in explain plans and runtime profiles. After more of
> the changes in IMPALA-8656 are merged, understanding what {{PLAN_ROOT_SINK}}
> is will be more important, because it will start taking up a memory
> reservation and possibly spilling to disk.
> I don't see any docs on data sinks in general, so perhaps it would be useful
> to create a dedicated page for explaining data sinks and how they work. We
> can start by documenting the {{PLAN_ROOT_SINK}} as that may be the most
> commonly used one.
> We should document all the changes being made in IMPALA-8656 as well.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Created] (IMPALA-8826) Impala Doc: Add docs for PLAN_ROOT_SINK
Sahil Takiar created IMPALA-8826:
Summary: Impala Doc: Add docs for PLAN_ROOT_SINK
Key: IMPALA-8826
URL: https://issues.apache.org/jira/browse/IMPALA-8826
Project: IMPALA
Issue Type: Sub-task
Components: Docs
Reporter: Sahil Takiar
Currently, I don't see many docs explaining what a {{PLAN_ROOT_SINK}} is, even
though it shows up in explain plans and runtime profiles. After more of the
changes in IMPALA-8656 are merged, understanding what {{PLAN_ROOT_SINK}} is
will be more important, because it will start taking up a memory reservation
and possibly spilling to disk.
I don't see any docs on data sinks in general, so perhaps it would be useful to
create a dedicated page for explaining data sinks and how they work. We can
start by documenting the {{PLAN_ROOT_SINK}} as that may be the most commonly
used one.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Created] (IMPALA-8826) Impala Doc: Add docs for PLAN_ROOT_SINK
Sahil Takiar created IMPALA-8826:
Summary: Impala Doc: Add docs for PLAN_ROOT_SINK
Key: IMPALA-8826
URL: https://issues.apache.org/jira/browse/IMPALA-8826
Project: IMPALA
Issue Type: Sub-task
Components: Docs
Reporter: Sahil Takiar
Currently, I don't see many docs explaining what a {{PLAN_ROOT_SINK}} is, even
though it shows up in explain plans and runtime profiles. After more of the
changes in IMPALA-8656 are merged, understanding what {{PLAN_ROOT_SINK}} is
will be more important, because it will start taking up a memory reservation
and possibly spilling to disk.
I don't see any docs on data sinks in general, so perhaps it would be useful to
create a dedicated page for explaining data sinks and how they work. We can
start by documenting the {{PLAN_ROOT_SINK}} as that may be the most commonly
used one.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (IMPALA-8825) Add additional counters to PlanRootSink
[
https://issues.apache.org/jira/browse/IMPALA-8825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16899020#comment-16899020
]
Sahil Takiar commented on IMPALA-8825:
--
Would be nice to have IMPALA-7551 fixed as part of this as well, so linking the
two.
> Add additional counters to PlanRootSink
> ---
>
> Key: IMPALA-8825
> URL: https://issues.apache.org/jira/browse/IMPALA-8825
> Project: IMPALA
> Issue Type: Sub-task
> Components: Backend
>Reporter: Sahil Takiar
>Assignee: Sahil Takiar
>Priority: Major
>
> The current entry in the runtime profile for {{PLAN_ROOT_SINK}} does not
> contain much useful information:
> {code:java}
> PLAN_ROOT_SINK:(Total: 234.996ms, non-child: 234.996ms, % non-child: 100.00%)
> - PeakMemoryUsage: 0{code}
> There are several additional counters we could add to the {{PlanRootSink}}
> (either the {{BufferedPlanRootSink}} or {{BlockingPlanRootSink}}):
> * Amount of time spent blocking inside the {{PlanRootSink}} - both the time
> spent by the client thread waiting for rows to become available and the time
> spent by the impala thread waiting for the client to consume rows
> ** So similar to the {{RowBatchQueueGetWaitTime}} and
> {{RowBatchQueuePutWaitTime}} inside the scan nodes
> ** The difference between these counters and the ones in
> {{ClientRequestState}} (e.g. {{ClientFetchWaitTimer}} and
> {{RowMaterializationTimer}}) should be documented
> * For {{BufferedPlanRootSink}} there are already several {{Buffer pool}}
> counters, we should make sure they are exposed in the {{PLAN_ROOT_SINK}}
> section
> * Track the number of rows sent (e.g. rows sent to {{PlanRootSink::Send}}
> and the number of rows fetched (might need to be tracked in the
> {{ClientRequestState}})
> ** For {{BlockingPlanRootSink}} the sent and fetched values should be pretty
> much the same, but for {{BufferedPlanRootSink}} this is more useful
> ** Similar to {{RowsReturned}} in each exec node
> * The rate at which rows are sent and fetched
> ** Should be useful when attempting to debug perf of the fetching rows (e.g.
> if the send rate is much higher than the fetch rate, then maybe there is
> something wrong with the client)
> ** Similar to {{RowsReturnedRate}} in each exec node
> Open to other suggestions for counters that folks think are useful.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Created] (IMPALA-8825) Add additional counters to PlanRootSink
Sahil Takiar created IMPALA-8825:
Summary: Add additional counters to PlanRootSink
Key: IMPALA-8825
URL: https://issues.apache.org/jira/browse/IMPALA-8825
Project: IMPALA
Issue Type: Sub-task
Components: Backend
Reporter: Sahil Takiar
Assignee: Sahil Takiar
The current entry in the runtime profile for {{PLAN_ROOT_SINK}} does not
contain much useful information:
{code:java}
PLAN_ROOT_SINK:(Total: 234.996ms, non-child: 234.996ms, % non-child: 100.00%)
- PeakMemoryUsage: 0{code}
There are several additional counters we could add to the {{PlanRootSink}}
(either the {{BufferedPlanRootSink}} or {{BlockingPlanRootSink}}):
* Amount of time spent blocking inside the {{PlanRootSink}} - both the time
spent by the client thread waiting for rows to become available and the time
spent by the impala thread waiting for the client to consume rows
** So similar to the {{RowBatchQueueGetWaitTime}} and
{{RowBatchQueuePutWaitTime}} inside the scan nodes
** The difference between these counters and the ones in
{{ClientRequestState}} (e.g. {{ClientFetchWaitTimer}} and
{{RowMaterializationTimer}}) should be documented
* For {{BufferedPlanRootSink}} there are already several {{Buffer pool}}
counters, we should make sure they are exposed in the {{PLAN_ROOT_SINK}} section
* Track the number of rows sent (e.g. rows sent to {{PlanRootSink::Send}} and
the number of rows fetched (might need to be tracked in the
{{ClientRequestState}})
** For {{BlockingPlanRootSink}} the sent and fetched values should be pretty
much the same, but for {{BufferedPlanRootSink}} this is more useful
** Similar to {{RowsReturned}} in each exec node
* The rate at which rows are sent and fetched
** Should be useful when attempting to debug perf of the fetching rows (e.g.
if the send rate is much higher than the fetch rate, then maybe there is
something wrong with the client)
** Similar to {{RowsReturnedRate}} in each exec node
Open to other suggestions for counters that folks think are useful.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (IMPALA-8825) Add additional counters to PlanRootSink
Sahil Takiar created IMPALA-8825:
Summary: Add additional counters to PlanRootSink
Key: IMPALA-8825
URL: https://issues.apache.org/jira/browse/IMPALA-8825
Project: IMPALA
Issue Type: Sub-task
Components: Backend
Reporter: Sahil Takiar
Assignee: Sahil Takiar
The current entry in the runtime profile for {{PLAN_ROOT_SINK}} does not
contain much useful information:
{code:java}
PLAN_ROOT_SINK:(Total: 234.996ms, non-child: 234.996ms, % non-child: 100.00%)
- PeakMemoryUsage: 0{code}
There are several additional counters we could add to the {{PlanRootSink}}
(either the {{BufferedPlanRootSink}} or {{BlockingPlanRootSink}}):
* Amount of time spent blocking inside the {{PlanRootSink}} - both the time
spent by the client thread waiting for rows to become available and the time
spent by the impala thread waiting for the client to consume rows
** So similar to the {{RowBatchQueueGetWaitTime}} and
{{RowBatchQueuePutWaitTime}} inside the scan nodes
** The difference between these counters and the ones in
{{ClientRequestState}} (e.g. {{ClientFetchWaitTimer}} and
{{RowMaterializationTimer}}) should be documented
* For {{BufferedPlanRootSink}} there are already several {{Buffer pool}}
counters, we should make sure they are exposed in the {{PLAN_ROOT_SINK}} section
* Track the number of rows sent (e.g. rows sent to {{PlanRootSink::Send}} and
the number of rows fetched (might need to be tracked in the
{{ClientRequestState}})
** For {{BlockingPlanRootSink}} the sent and fetched values should be pretty
much the same, but for {{BufferedPlanRootSink}} this is more useful
** Similar to {{RowsReturned}} in each exec node
* The rate at which rows are sent and fetched
** Should be useful when attempting to debug perf of the fetching rows (e.g.
if the send rate is much higher than the fetch rate, then maybe there is
something wrong with the client)
** Similar to {{RowsReturnedRate}} in each exec node
Open to other suggestions for counters that folks think are useful.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-2019) Proper UTF-8 support in string functions
[
https://issues.apache.org/jira/browse/IMPALA-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16898861#comment-16898861
]
Philip commented on IMPALA-2019:
Also String lengths seem to be an issue.
It appears to return the *byte length* rather than the *number of characters*.
I would suggest this is +not a minor issue+.
{color:#205081} *select length('€')* {color}
In Hive returns 1
In Impala returns 3
> Proper UTF-8 support in string functions
>
>
> Key: IMPALA-2019
> URL: https://issues.apache.org/jira/browse/IMPALA-2019
> Project: IMPALA
> Issue Type: New Feature
> Components: Backend
>Affects Versions: Impala 2.1, Impala 2.2
>Reporter: Andrés Cordero
>Priority: Minor
> Labels: sql-language
>
> As documented here:
> http://www.cloudera.com/content/cloudera/en/documentation/cloudera-impala/latest/topics/impala_string.html
> Impala does not properly handle non-ASCII UTF-8 characters, and will return
> results in string functions such as length that are inconsistent with Hive.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Resolved] (IMPALA-8817) TestTestcaseBuilder broken on S3
[
https://issues.apache.org/jira/browse/IMPALA-8817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Csaba Ringhofer resolved IMPALA-8817.
-
Resolution: Fixed
Fix Version/s: Impala 3.3.0
> TestTestcaseBuilder broken on S3
>
>
> Key: IMPALA-8817
> URL: https://issues.apache.org/jira/browse/IMPALA-8817
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
>Affects Versions: Impala 3.3.0
>Reporter: Csaba Ringhofer
>Assignee: Csaba Ringhofer
>Priority: Major
> Fix For: Impala 3.3.0
>
>
> metadata.test_testcase_builder.TestTestcaseBuilder.test_query_without_from
> fails with the following stack trace in S3 environment:
> {code}
> metadata/test_testcase_builder.py:41: in test_query_without_from
> result = self.execute_query_expect_success(self.client,
> testcase_generate_query)
> common/impala_test_suite.py:700: in wrapper
> return function(*args, **kwargs)
> common/impala_test_suite.py:708: in execute_query_expect_success
> result = cls.__execute_query(impalad_client, query, query_options, user)
> common/impala_test_suite.py:802: in __execute_query
> return impalad_client.execute(query, user=user)
> common/impala_connection.py:184: in execute
> return self.__beeswax_client.execute(sql_stmt, user=user)
> beeswax/impala_beeswax.py:187: in execute
> handle = self.__execute_query(query_string.strip(), user=user)
> beeswax/impala_beeswax.py:362: in __execute_query
> handle = self.execute_query_async(query_string, user=user)
> beeswax/impala_beeswax.py:356: in execute_query_async
> handle = self.__do_rpc(lambda: self.imp_service.query(query,))
> beeswax/impala_beeswax.py:519: in __do_rpc
> raise ImpalaBeeswaxException(self.__build_error_message(b), b)
> E ImpalaBeeswaxException: ImpalaBeeswaxException:
> EINNER EXCEPTION:
> EMESSAGE: AnalysisException: Incomplete HDFS URI, no host: hdfs:///tmp
> E CAUSED BY: IOException: Incomplete HDFS URI, no host: hdfs:///tmp
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Resolved] (IMPALA-8817) TestTestcaseBuilder broken on S3
[
https://issues.apache.org/jira/browse/IMPALA-8817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Csaba Ringhofer resolved IMPALA-8817.
-
Resolution: Fixed
Fix Version/s: Impala 3.3.0
> TestTestcaseBuilder broken on S3
>
>
> Key: IMPALA-8817
> URL: https://issues.apache.org/jira/browse/IMPALA-8817
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
>Affects Versions: Impala 3.3.0
>Reporter: Csaba Ringhofer
>Assignee: Csaba Ringhofer
>Priority: Major
> Fix For: Impala 3.3.0
>
>
> metadata.test_testcase_builder.TestTestcaseBuilder.test_query_without_from
> fails with the following stack trace in S3 environment:
> {code}
> metadata/test_testcase_builder.py:41: in test_query_without_from
> result = self.execute_query_expect_success(self.client,
> testcase_generate_query)
> common/impala_test_suite.py:700: in wrapper
> return function(*args, **kwargs)
> common/impala_test_suite.py:708: in execute_query_expect_success
> result = cls.__execute_query(impalad_client, query, query_options, user)
> common/impala_test_suite.py:802: in __execute_query
> return impalad_client.execute(query, user=user)
> common/impala_connection.py:184: in execute
> return self.__beeswax_client.execute(sql_stmt, user=user)
> beeswax/impala_beeswax.py:187: in execute
> handle = self.__execute_query(query_string.strip(), user=user)
> beeswax/impala_beeswax.py:362: in __execute_query
> handle = self.execute_query_async(query_string, user=user)
> beeswax/impala_beeswax.py:356: in execute_query_async
> handle = self.__do_rpc(lambda: self.imp_service.query(query,))
> beeswax/impala_beeswax.py:519: in __do_rpc
> raise ImpalaBeeswaxException(self.__build_error_message(b), b)
> E ImpalaBeeswaxException: ImpalaBeeswaxException:
> EINNER EXCEPTION:
> EMESSAGE: AnalysisException: Incomplete HDFS URI, no host: hdfs:///tmp
> E CAUSED BY: IOException: Incomplete HDFS URI, no host: hdfs:///tmp
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-8817) TestTestcaseBuilder broken on S3
[
https://issues.apache.org/jira/browse/IMPALA-8817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16898759#comment-16898759
]
ASF subversion and git services commented on IMPALA-8817:
-
Commit 31aa38b4c78bebafff40bf166dc876be36c13fc5 in impala's branch
refs/heads/master from Csaba Ringhofer
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=31aa38b ]
IMPALA-8817: Fix TestTestcaseBuilder tests on non-HDFS environment
Using "hdfs:///tmp" as path for the test cases did not work in S3
environment.
Change-Id: Ibf6767c3275dc5deec75a36f797d0963f83839cf
Reviewed-on: http://gerrit.cloudera.org:8080/13963
Reviewed-by: Impala Public Jenkins
Tested-by: Impala Public Jenkins
> TestTestcaseBuilder broken on S3
>
>
> Key: IMPALA-8817
> URL: https://issues.apache.org/jira/browse/IMPALA-8817
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
>Affects Versions: Impala 3.3.0
>Reporter: Csaba Ringhofer
>Assignee: Csaba Ringhofer
>Priority: Major
>
> metadata.test_testcase_builder.TestTestcaseBuilder.test_query_without_from
> fails with the following stack trace in S3 environment:
> {code}
> metadata/test_testcase_builder.py:41: in test_query_without_from
> result = self.execute_query_expect_success(self.client,
> testcase_generate_query)
> common/impala_test_suite.py:700: in wrapper
> return function(*args, **kwargs)
> common/impala_test_suite.py:708: in execute_query_expect_success
> result = cls.__execute_query(impalad_client, query, query_options, user)
> common/impala_test_suite.py:802: in __execute_query
> return impalad_client.execute(query, user=user)
> common/impala_connection.py:184: in execute
> return self.__beeswax_client.execute(sql_stmt, user=user)
> beeswax/impala_beeswax.py:187: in execute
> handle = self.__execute_query(query_string.strip(), user=user)
> beeswax/impala_beeswax.py:362: in __execute_query
> handle = self.execute_query_async(query_string, user=user)
> beeswax/impala_beeswax.py:356: in execute_query_async
> handle = self.__do_rpc(lambda: self.imp_service.query(query,))
> beeswax/impala_beeswax.py:519: in __do_rpc
> raise ImpalaBeeswaxException(self.__build_error_message(b), b)
> E ImpalaBeeswaxException: ImpalaBeeswaxException:
> EINNER EXCEPTION:
> EMESSAGE: AnalysisException: Incomplete HDFS URI, no host: hdfs:///tmp
> E CAUSED BY: IOException: Incomplete HDFS URI, no host: hdfs:///tmp
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-8403) Possible thread leak in impalad
[
https://issues.apache.org/jira/browse/IMPALA-8403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16898711#comment-16898711
]
Adriano commented on IMPALA-8403:
-
Thank [~kwho],
yes, it will be a good improvement after IMPALA-7984 will be done.
> Possible thread leak in impalad
> ---
>
> Key: IMPALA-8403
> URL: https://issues.apache.org/jira/browse/IMPALA-8403
> Project: IMPALA
> Issue Type: Bug
>Affects Versions: Impala 2.12.0
>Reporter: Quanlong Huang
>Priority: Major
> Attachments: image-2019-04-10-11-15-11-321.png, reproIMPALA-8403.tgz
>
>
> The metric of thread-manager.running-threads got from
> http://${impalad_host}:25000/metrics?json shows that the number of running
> threads keeps increasing. (See the snapshot) This phenomenon is most
> noticeable in coordinators.
> Maybe a counter bug or threads leak.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-8738) Add a column representing the type（table or view） in the show tables output
[
https://issues.apache.org/jira/browse/IMPALA-8738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16898646#comment-16898646
]
baotuquan commented on IMPALA-8738:
---
The show views and show tables commands have some duplicate functionality and
may mislead newcomers from naming.
There is a similar command in impala, describe extended tables.
So I prefer to use show extended tables or show tables extended.
> Add a column representing the type（table or view） in the show tables output
> ---
>
> Key: IMPALA-8738
> URL: https://issues.apache.org/jira/browse/IMPALA-8738
> Project: IMPALA
> Issue Type: Improvement
> Components: Catalog, Frontend
>Reporter: baotuquan
>Assignee: baotuquan
>Priority: Minor
> Labels: features
>
> Now the output of the +*show tables*+ command in the system is as follows：
> {code:java}
> default> show tables;
> Query: show tables
> +--+
> | name |
> +--+
> | table1 |
> | view1 |
> +--+
> {code}
> I think we should add a column for the representation type，The output should
> be like this
> {code:java}
> default> show tables;
> Query: show tables
> +---+
> | name | type |
> ++
> | table1 | table |
> | view1 | view |
> ++
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
