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

Posted to notifications@skywalking.apache.org by GitBox <gi...@apache.org> on 2023/01/17 06:05:14 UTC

[GitHub] [skywalking] wu-sheng commented on pull request #10282: Change trace/span on ElasticSearch to use traceIDs routing.

wu-sheng commented on PR #10282:
URL: https://github.com/apache/skywalking/pull/10282#issuecomment-1384876698

   > > Mentioned [#10276 (reply in thread)](https://github.com/apache/skywalking/discussions/10276#discussioncomment-4693566), more record should be updated.
   > > 
   > > * Zipkin Span
   > > * How would we treat log entity? It may have trace-id. What is the policy?
   > 
   > The currently supported query scenarios in `LogQueryEsDAO`are rich, not easy to set policy. If the main usage scenario is to query through traceid, it is appropriate to set routing as traceid.
   
   TraceSegment query has various conditions too. What is the different?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@skywalking.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org