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

Split internal/coreinternal/processor into a separate internal/filter module #16410

Merged
merged 1 commit into from
Nov 22, 2022

Conversation

bogdandrutu
Copy link
Member

Allows to avoid dependency on OTTL in all packages (after we change filter to use ottl).

Signed-off-by: Bogdan Drutu [email protected]

Copy link
Member

@TylerHelmuth TylerHelmuth left a comment

Choose a reason for hiding this comment

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

What is the difference between internal and internal/coreinternal? I like the idea of moving filter out of a processor-specific package, but should it still be in coreinternal?

@bogdandrutu
Copy link
Member Author

coreinternal was a historical package that was moved from "core" repo. No other meaning of "core", so I don't think we need it in "coreinternal"

@bogdandrutu
Copy link
Member Author

Also, all of these are internal packages, so we can play with the structure as much as we want :)

… module

Allows to avoid dependency on OTTL in all packages (after we change filter to use ottl).

Signed-off-by: Bogdan Drutu <[email protected]>
@bogdandrutu bogdandrutu merged commit 7b88749 into open-telemetry:main Nov 22, 2022
@bogdandrutu bogdandrutu deleted the splitfilter branch November 22, 2022 01:51
shalper2 pushed a commit to shalper2/opentelemetry-collector-contrib that referenced this pull request Dec 6, 2022
… module (open-telemetry#16410)

Allows to avoid dependency on OTTL in all packages (after we change filter to use ottl).

Signed-off-by: Bogdan Drutu <[email protected]>

Signed-off-by: Bogdan Drutu <[email protected]>
@plantfansam plantfansam mentioned this pull request Jul 21, 2023
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