[
https://issues.apache.org/jira/browse/PHOENIX-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14355368#comment-14355368
]
James Taylor commented on PHOENIX-1691:
---------------------------------------
{quote}
Currently what ever sampler first chosen sticking with that. I am thinking
whether we can throw exception in this case to suggest the user that already
trace enabled and to change the sampler rate disable the trace and enable with
new sampling rate. What do you say?
{quote}
If possible, it'd be nice to be able to update the sampling rate on the
connection, rather than keeping the first on. If that's not possible/feasible,
then throwing an exception is the next best option.
> Allow settting sampling rate while enabling tracing.
> ----------------------------------------------------
>
> Key: PHOENIX-1691
> URL: https://issues.apache.org/jira/browse/PHOENIX-1691
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Rajeshbabu Chintaguntla
> Assignee: Rajeshbabu Chintaguntla
> Fix For: 5.0.0, 4.4
>
> Attachments: PHOENIX-1691.patch
>
>
> Now we can dynamically enable/disable tracing from query. We should also be
> able to set sampling rate while enabling tracing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
