You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Philip Zeyliger (JIRA)" <ji...@apache.org> on 2018/06/12 22:17:00 UTC
[jira] [Commented] (IMPALA-7164) Define public API for
RuntimeProfile
[ https://issues.apache.org/jira/browse/IMPALA-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16510312#comment-16510312 ]
Philip Zeyliger commented on IMPALA-7164:
-----------------------------------------
I think instead of a map of counters keyed by counter name, we should strive to put those names in the Thrift schema definition itself. That will allow evolution and be considerably more obvious.
> Define public API for RuntimeProfile
> ------------------------------------
>
> Key: IMPALA-7164
> URL: https://issues.apache.org/jira/browse/IMPALA-7164
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Reporter: Tim Armstrong
> Priority: Major
> Labels: resource-management, usability
>
> Currently the only public API for the runtime profile is the Thrift definition. The exact layout and counters are all implementation-dependent and subject to change. People are trying to build tools that consume runtime profiles and process them, but that's hard since the counters can change from version to version and sometimes the semantics change.
> I think we need to figure out which things are part of the public API, validate that they make sense and document them clearly. We should also clearly document that things outside of this public API are subject to change without notice. I don't think the public API necessarily needs to be "porcelain", but we should generally try to avoid unnecessary changes and mention any changes in release notes etc.
> We could start simple and just collect "public" counter names in a module and comment each of them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org