[
https://issues.apache.org/jira/browse/PHOENIX-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14121710#comment-14121710
]
Jesse Yates edited comment on PHOENIX-1196 at 9/4/14 6:26 PM:
--------------------------------------------------------------
Over in PHOENIX-1226 we are talking about typing the annotations that come
through so we can actually have columns that are not just strings, but real
types. It would be nice if we started with something like:
{code}
phoenix.tracing.custom.annotation.<type>.<annotation key>=<annotation value>
{code}
where the only 'type' we support at the moment is "string" or "varchar". Its
slightly more verbose, but provides us some flexibility later.
Also, I'm just a big fan of proper prefixing to avoid clashes so adding phoenix
and custom to the expected key is something that should be done regardless of
the rest of the key used.
was (Author: jesse_yates):
Over in PHOENIX-1126 we are talking about typing the annotations that come
through so we can actually have columns that are not just strings, but real
types. It would be nice if we started with something like:
{code}
phoenix.tracing.custom.annotation.<type>.<annotation key>=<annotation value>
{code}
where the only 'type' we support at the moment is "string" or "varchar". Its
slightly more verbose, but provides us some flexibility later.
Also, I'm just a big fan of proper prefixing to avoid clashes so adding phoenix
and custom to the expected key is something that should be done regardless of
the rest of the key used.
> Add ability to add custom tracing annotations for connections
> -------------------------------------------------------------
>
> Key: PHOENIX-1196
> URL: https://issues.apache.org/jira/browse/PHOENIX-1196
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Eli Levine
> Assignee: Eli Levine
> Fix For: 5.0.0, 4.1
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
