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

receiver/kafkareceiver - Allow user to read from latest or smallest offset #14976

Closed
MacNale opened this issue Oct 17, 2022 · 6 comments
Closed
Labels
enhancement New feature or request priority:needed Triagers reviewed the issue but need code owner to set priority receiver/kafka Stale

Comments

@MacNale
Copy link

MacNale commented Oct 17, 2022

Is your feature request related to a problem? Please describe.

I cant specify kafka offset to configure receiver/kafkareceiver to start reading from.

Describe the solution you'd like

support config as follows -

offset: smallest | latest

Describe alternatives you've considered

No response

Additional context

No response

@MacNale MacNale added enhancement New feature or request needs triage New item requiring triage labels Oct 17, 2022
@evan-bradley evan-bradley added receiver/kafka priority:needed Triagers reviewed the issue but need code owner to set priority and removed needs triage New item requiring triage labels Oct 17, 2022
@github-actions
Copy link
Contributor

Pinging code owners: @pavolloffay @MovieStoreGuy. See Adding Labels via Comments if you do not have permissions to add labels yourself.

@MovieStoreGuy
Copy link
Contributor

Hey @MacNale ,

Could you give us a scenario where this would be valuable?

@MacNale
Copy link
Author

MacNale commented Nov 3, 2022

This is for testing. Having such offset makes my integration testing easy.

@github-actions
Copy link
Contributor

github-actions bot commented Jan 3, 2023

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@ueisele
Copy link
Contributor

ueisele commented May 2, 2023

Hello,

I also need this feature to submit metrics already published to Kafka to an additional sink.
In principle, it would of course also be possible to create a consumer group in advance and set the offset. However, a way to configure this would make this much easier.
Since this only required a few lines of code, I implemented this and created the PR #21408.

@github-actions github-actions bot removed the Stale label May 27, 2023
@github-actions
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Jul 26, 2023
@MacNale MacNale closed this as completed Aug 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority:needed Triagers reviewed the issue but need code owner to set priority receiver/kafka Stale
Projects
None yet
Development

No branches or pull requests

4 participants