[jira] [Resolved] (IMPALA-8235) AdmissionControlTimeSinceLastUpdate TIME_MS counter breaks some profile consumers

["Tim Armstrong (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-8235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Armstrong resolved IMPALA-8235.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 3.2.0

> AdmissionControlTimeSinceLastUpdate TIME_MS counter breaks some profile consumers
> ---------------------------------------------------------------------------------
>
>                 Key: IMPALA-8235
>                 URL: https://issues.apache.org/jira/browse/IMPALA-8235
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 3.2.0
>            Reporter: Tim Armstrong
>            Assignee: Tim Armstrong
>            Priority: Blocker
>              Labels: observability
>             Fix For: Impala 3.2.0
>
>
> The issue is:
> * type is a required field for TCounter with enum type TUnit
> * Some readers (e.g. Java) that encounter an unknown enum value replace it it with null, then throw an exception because it is a required field
> This means that the workflow for adding a new TUnit is basically broken, since we can't add a unit in Impala then update readers later.
> I think we should switch to TIME_NS then reconsider the workflow here.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)