You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@impala.apache.org by "David Rorke (Jira)" <ji...@apache.org> on 2020/03/13 23:06:00 UTC

[jira] [Created] (IMPALA-9505) CatalogMetaProvider using bad TUnit for profile counters

David Rorke created IMPALA-9505:
-----------------------------------

             Summary: CatalogMetaProvider using bad TUnit for profile counters
                 Key: IMPALA-9505
                 URL: https://issues.apache.org/jira/browse/IMPALA-9505
             Project: IMPALA
          Issue Type: Bug
          Components: Frontend
            Reporter: David Rorke


CatalogMetaProvider is using a TUnit value of TUnit.NONE for several runtime profile counters:

[https://github.com/apache/impala/blob/master/fe/src/main/java/org/apache/impala/catalog/local/CatalogdMetaProvider.java#L554-L558]

and

[https://github.com/apache/impala/blob/master/fe/src/main/java/org/apache/impala/catalog/local/CatalogdMetaProvider.java#L387]

TUnit.UNIT would be a better choice here and the use of TUnit.NONE may break existing profile readers which won't expect this value for a numerical counter.  The appropriate set of TUnit types to maximize reader compatibility is described in IMPALA-8236.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)