[
https://issues.apache.org/jira/browse/KUDU-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17112673#comment-17112673
]
ASF subversion and git services commented on KUDU-3116:
-------------------------------------------------------
Commit 926802ba848dc571a087eb3a92249fa500fd0da7 in kudu's branch
refs/heads/master from Brian McDevitt
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=926802b ]
[KUDU-3116] Enhance KuduContext row operation metrics
Adds the ability to track operation counts per table. Introduces the
MapAccumulator to track these metrics in a single accumulator per
operation type.
Change-Id: Ie66dab95041310c27ef62dacccbcc0977a84857e
Reviewed-on: http://gerrit.cloudera.org:8080/15882
Tested-by: Kudu Jenkins
Reviewed-by: Grant Henke <[email protected]>
Reviewed-by: Andrew Wong <[email protected]>
> Enhance operation accumulators in KuduContext to track operations per table
> ---------------------------------------------------------------------------
>
> Key: KUDU-3116
> URL: https://issues.apache.org/jira/browse/KUDU-3116
> Project: Kudu
> Issue Type: Improvement
> Components: java, spark
> Reporter: Brian McDevitt
> Priority: Minor
>
> The KuduContext tracks row count metrics in LongAccumulators, but often the
> same KuduContext is used for multiple tables causing the LongAccumulators to
> report incorrect row count values. Having those metrics tracked per table
> would improve the results/logging.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
