Skip to content

Fix tracing to continue from existing trace created by grpc client - #245

Merged
feast-ci-bot merged 19 commits into
feast-dev:0.1.xfrom
pradithya:0.1.x
Sep 19, 2019
Merged

Fix tracing to continue from existing trace created by grpc client#245
feast-ci-bot merged 19 commits into
feast-dev:0.1.xfrom
pradithya:0.1.x

Conversation

@pradithya

@pradithya pradithya commented Sep 9, 2019

Copy link
Copy Markdown
Collaborator

Main purpose of this PR is to fix jaeger tracing behavior where currently it will start a new trace instead of continuing trace created by client.

Changes:

  • Add ServerTracingInterceptor
  • Upgrade opentracing-api and jaeger-client version

@feast-ci-bot

Copy link
Copy Markdown
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pradithya

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@davidheryanto

Copy link
Copy Markdown
Collaborator

/lgtm

@davidheryanto

Copy link
Copy Markdown
Collaborator

/retest

@davidheryanto

Copy link
Copy Markdown
Collaborator

/test unit-test-cli

@feast-dev feast-dev deleted a comment from feast-ci-bot Sep 19, 2019
@feast-ci-bot
feast-ci-bot merged commit dd216c2 into feast-dev:0.1.x Sep 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants