Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[exporter] Remove jaeger dbmodel dependency #36972

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

zzzk1
Copy link

@zzzk1 zzzk1 commented Dec 27, 2024

Description

Copy the Jaeger plugin/storage/es/spanstore/dbmodel for logzioexporter, and remove the dependency. The dbmodel package in Jaeger will be internal from v1.65 (jaegertracing/jaeger#6428).

Link to tracking issue

Fixes #36970

Testing

Covered by existing

yurishkuro pushed a commit to jaegertracing/jaeger that referenced this pull request Dec 27, 2024
## Which problem is this PR solving?
- Resolves #6410
- Prerequisite:
open-telemetry/opentelemetry-collector-contrib#36972

## Description of the changes
- move plugin/storage/es/spanstore/dbmodel to
plugin/storage/es/spanstore/internal/dbmodel

## How was this change tested?
- 

## Checklist
- [x] I have read
https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
- [x] I have signed all commits
- [ ] I have added unit tests for the new functionality
- [x] I have run lint and test steps successfully
  - for `jaeger`: `make lint test`
  - for `jaeger-ui`: `npm run lint` and `npm run test`

---------

Signed-off-by: zzzk1 <[email protected]>
@@ -16,22 +15,107 @@ const (
tagDotReplacementCharacter = "@"
)

// logzioSpan is same as esSpan with a few different json field names and an addition on type field.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I strongly advise to structure your PR such that it does not move code unnecessarily. The diff view should be showing no changes to this type, instead for me it shows as deleted and another one added below, which is named differently and may or may not be the same. Why introduce this additional complexity for the reviewer?

Copy link
Member

@yurishkuro yurishkuro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, but code owners need to sign off -- @yotamloe

}

// LogzioSpan is same as ESSpan with a few different json field names and an addition on type field.
type LogzioSpan struct {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

none of the new structs should public

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.

Eliminate logziospan dependency on the plugin/storage/es/spanstore/dbmodel
3 participants