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

Provide a SequencingPolicy based on a MetaData field #1929

Closed
lfgcampos opened this issue Sep 17, 2021 · 0 comments · Fixed by #1930
Closed

Provide a SequencingPolicy based on a MetaData field #1929

lfgcampos opened this issue Sep 17, 2021 · 0 comments · Fixed by #1930
Assignees
Labels
Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
Milestone

Comments

@lfgcampos
Copy link
Contributor

Feature Description

Provide a SequencingPolicy based on a MetaData field would provide an extra option for the users when configuring their Event Processors. Using a MetaData field proved to be a common approach for some businesses.

Current Behaviour

There is no MetaData based SequencingPolicy.

Wanted Behaviour

An OOTB MetaData based SequencingPolicy.

Possible Workarounds

N/A

@lfgcampos lfgcampos added Type: Feature Use to signal an issue is completely new to the project. Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Status: In Progress Use to signal this issue is actively worked on. labels Sep 17, 2021
@lfgcampos lfgcampos added this to the Release 4.6.0 milestone Sep 17, 2021
@lfgcampos lfgcampos self-assigned this Sep 17, 2021
@close-label close-label bot added the Status: Resolved Use to signal that work on this issue is done. label Sep 20, 2021
@lfgcampos lfgcampos removed the Status: In Progress Use to signal this issue is actively worked on. label Sep 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant