You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2019/02/21 01:48:00 UTC
[jira] [Created] (IMPALA-8236) Adding new TUnit values to runtime
profile is broken
Tim Armstrong created IMPALA-8236:
-------------------------------------
Summary: Adding new TUnit values to runtime profile is broken
Key: IMPALA-8236
URL: https://issues.apache.org/jira/browse/IMPALA-8236
Project: IMPALA
Issue Type: Bug
Components: Backend
Reporter: Tim Armstrong
See IMPALA-8235 for context.
The problem this tracks is that there's no way to add a new value to the TUnit enum, which is required in TCounter, without breaking existing readers (at least Java readers), which will fail to decode TCounter values with an enum value they don't recognise.
The workaround is to only use the following units in anything that is serialised into a TCounter:
{noformat}
UNIT,
UNIT_PER_SECOND,
CPU_TICKS,
BYTES
BYTES_PER_SECOND,
TIME_NS,
DOUBLE_VALUE
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)