[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=16944841#comment-16944841
]
ASF subversion and git services commented on IMPALA-8826:
-
Commit c4874d9a94d6e2fda7ead957dbb385fea3a5c0b1 in impala's branch
refs/heads/master from Alex Rodoni
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=c4874d9 ]
IMPALA-8826: [DOCS] Add docs for PLAN_ROOT_SINK and result spooling
Change-Id: I78bfceb225d25078c54c1ed8f88ca250ef42dafe
Reviewed-on: http://gerrit.cloudera.org:8080/14314
Reviewed-by: Sahil Takiar
Tested-by: Impala Public Jenkins
> 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: Alexandra Rodoni
>Priority: Major
> Labels: future_release_doc, in_34
>
> 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.
> Query option:
> SPOOL_QUERY_RESULTS
> MAX_RESULT_SPOOLING_MEM
> MAX_SPILLED_RESULT_SPOOLING_MEM
> FETCH_ROWS_TIMEOUT_MS (https://issues.apache.org/jira/browse/IMPALA-7312)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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=16939027#comment-16939027
]
Alex Rodoni commented on IMPALA-8826:
-
https://gerrit.cloudera.org/#/c/14314/
> 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.
> Query option:
> SPOOL_QUERY_RESULTS
> MAX_RESULT_SPOOLING_MEM
> MAX_SPILLED_RESULT_SPOOLING_MEM
> FETCH_ROWS_TIMEOUT_MS (https://issues.apache.org/jira/browse/IMPALA-7312)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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=16901361#comment-16901361
]
Sahil Takiar commented on IMPALA-8826:
--
It is likely going to be for the 3.3 release, although I'm not exactly sure
when that will be.
> 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] [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
