You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Nishani (JIRA)" <ji...@apache.org> on 2016/05/25 11:27:12 UTC

[jira] [Commented] (PHOENIX-2208) Navigation to trace information in tracing UI should be driven off of query instead of trace ID

    [ https://issues.apache.org/jira/browse/PHOENIX-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299903#comment-15299903 ] 

Nishani  commented on PHOENIX-2208:
-----------------------------------

Hi,

An issue is raised if the query is not unique (ex. same query is run multiple times). Therefore trace id is more appropriate. Else the first few characters from description of traces can be used.

> Navigation to trace information in tracing UI should be driven off of query instead of trace ID
> -----------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-2208
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2208
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: Nishani 
>
> Instead of driving the trace UI based on the trace ID, we should drive it off of the query string. Something like a drop down list that shows the query string of the last N queries which can be selected from, with a search box for a regex query string and perhaps time range that would search for the trace ID under the covers. 



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