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.

Sign up for GitHub

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

Jump to bottom

[FEATURE REQ] Provide a convenient method in EventProcessorClientBuilder to configure initialPartitionEventPosition for all partitions #26432

Closed
2 tasks done
saragluna opened this issue Jan 12, 2022 · 2 comments
Closed
2 tasks done

[FEATURE REQ] Provide a convenient method in EventProcessorClientBuilder to configure initialPartitionEventPosition for all partitions #26432

saragluna opened this issue Jan 12, 2022 · 2 comments
Assignees
@conniey
Labels
Client This issue points to a problem in the data-plane of the library. Event Hubs feature-request This issue requires a new behavior in the product in order be resolved.
Milestone
Backlog

Comments

@saragluna
Copy link
Member

Is your feature request related to a problem? Please describe.
The EventProcessorClientBuilder provides a initialPartitionEventPosition to configure the initial event position for each partition. But there're cases when users simply want to start from earliest or latest for each partition. In such cases, they have to duplicate this configuration for the number of partitions times. And if users are configuring these positions from a Spring Boot property file, they have to write such properties multiple times. In Spring Cloud Stream, we can provide a convenient way for users to specify earliest or latest for all partitions, but we need to find the number of partitions an event hub has before passing it to the builder.

Describe the solution you'd like
The EventProcessorClientBuilder provides such a convenient method to configure the initial event position for all partitions.

Describe alternatives you've considered
N/A

Additional context
N/A

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

  • Description Added
  • Expected solution specified
@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jan 12, 2022
@joshfree joshfree added Client This issue points to a problem in the data-plane of the library. Event Hubs feature-request This issue requires a new behavior in the product in order be resolved. labels Jan 13, 2022
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jan 13, 2022
@joshfree
Copy link
Member

@saragluna could you and @conniey chat and make sure we prioritize this at the right level to support spring?

@ramya-rao-a ramya-rao-a added this to the Backlog milestone Jan 18, 2022
@conniey
Copy link
Member

conniey commented Jan 18, 2022

This seems like a duplicate of #11431

@conniey conniey closed this as completed Jan 18, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@conniey conniey

Labels
Client This issue points to a problem in the data-plane of the library. Event Hubs feature-request This issue requires a new behavior in the product in order be resolved.
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
4 participants
@joshfree @conniey @ramya-rao-a @saragluna