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

[exporterhelper] Move batching API to a separate module #11143

Open
mx-psi opened this issue Sep 11, 2024 · 1 comment
Open

[exporterhelper] Move batching API to a separate module #11143

mx-psi opened this issue Sep 11, 2024 · 1 comment

Comments

@mx-psi
Copy link
Member

mx-psi commented Sep 11, 2024

We can look into separating the batching API into a different module. This helps in the separation of concerns and potentially allows us to stabilize exporterhelper without stabilizing the batching API.

@mx-psi mx-psi self-assigned this Sep 11, 2024
@mx-psi
Copy link
Member Author

mx-psi commented Sep 19, 2024

The symbols that would be moved to a different module would be those that are marked with Experimental/early stage of development, that is:

  • BatcherOption
  • WithRequestBatchFuncs
  • WithBatcher
  • WithRequestQueue
  • Request
  • RequestErrorHandler
  • RequestFromLogsFunc, RequestFromMetricsFunc, RequestFromTracesFunc

We would also move the exporterqueue and exporterbatcher packages into this separate module.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Blocked
Development

No branches or pull requests

1 participant