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

Eli Levine updated PHOENIX-1198:
--------------------------------
    Description: 
Users need a way to associate log lines emitted by Phoenix with other logs 
generated by higher levels of applications. This JIRA calls for allowing 
callers to pass custom annotations to Phoenix connections. The mechanism for 
passing in these annotations is the same as PHOENIX-1196. Phoenix will look for 
properties that start with "phoenix.annotation." and use them when generating 
log lines.

e.g. If a connection was created with a property 
+phoenix.annotation.userid=123+ Phoenix would emit log lines that would look 
like this: {code}{userid=123} some log line{code}

  was:These tags can be passed in either when creating connections or calling 
upsert/select. Similar to PHOENIX-1196. Maybe they can shared the same 
mechanism for passing in values to be logged/traced.


> Add ability to pass custom annotations to be added to log lines
> ---------------------------------------------------------------
>
>                 Key: PHOENIX-1198
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1198
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Eli Levine
>            Assignee: Eli Levine
>             Fix For: 5.0.0, 4.1
>
>
> Users need a way to associate log lines emitted by Phoenix with other logs 
> generated by higher levels of applications. This JIRA calls for allowing 
> callers to pass custom annotations to Phoenix connections. The mechanism for 
> passing in these annotations is the same as PHOENIX-1196. Phoenix will look 
> for properties that start with "phoenix.annotation." and use them when 
> generating log lines.
> e.g. If a connection was created with a property 
> +phoenix.annotation.userid=123+ Phoenix would emit log lines that would look 
> like this: {code}{userid=123} some log line{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to