[
https://issues.apache.org/jira/browse/IMPALA-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721613#comment-16721613
]
ASF subversion and git services commented on IMPALA-7351:
---------------------------------------------------------
Commit b2e63da2bad513864fcad3341e7206c24c166dcc in impala's branch
refs/heads/master from [~bikram.sngh91]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=b2e63da ]
IMPALA-7351 IMPALA-7353: Add justification for constant memory estimates
Added justification as comments for UNION, SELECT and Data Source scan
nodes that have a constant memory estimate.
Change-Id: I0049ea2f50400bd264d9257df0fac7397abb357c
Reviewed-on: http://gerrit.cloudera.org:8080/12063
Reviewed-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com>
Tested-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com>
> Add memory estimates for plan nodes and sinks with missing estimates
> --------------------------------------------------------------------
>
> Key: IMPALA-7351
> URL: https://issues.apache.org/jira/browse/IMPALA-7351
> Project: IMPALA
> Issue Type: Sub-task
> Components: Frontend
> Reporter: Tim Armstrong
> Assignee: Bikramjeet Vig
> Priority: Major
> Labels: admission-control, resource-management
>
> Many plan nodes and sinks, e.g. KuduScanNode, KuduTableSink, ExchangeNode,
> etc are missing memory estimates entirely.
> We should add a basic estimate for all these cases based on experiments and
> data from real workloads. In some cases 0 may be the right estimate (e.g. for
> streaming nodes like SelectNode that just pass through data) but we should
> remove TODOs and document the reasoning in those cases.
--
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
