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

Should we allow Proc Filters that use Status #4211

Open
stroomdev10 opened this issue Apr 15, 2024 · 0 comments
Open

Should we allow Proc Filters that use Status #4211

stroomdev10 opened this issue Apr 15, 2024 · 0 comments
Labels
bug f:pipeline-processing Issues relating to pipelines and processing question
Milestone
v7.4

Comments

@stroomdev10
Copy link
Member

A Proc Filter that includes for example Status=Unlocked appears to skip streams that are locked at the time of Task Creation.

The skipped streams are unlikely to be picked up on subsequent runs due to their Stream Ids having been passed by the Tracker.

Should we disallow the use of Status in Proc Filters?
@stroomdev10 stroomdev10 added this to the v7.4 milestone Apr 15, 2024
@stroomdev10 stroomdev10 changed the title Should we allow the creation of Proc Filters that use Status Should we allow Proc Filters that use Status Apr 15, 2024
@at055612 at055612 added the f:pipeline-processing Issues relating to pipelines and processing label Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug f:pipeline-processing Issues relating to pipelines and processing question
Projects
None yet
Milestone
v7.4
Development

No branches or pull requests
2 participants
@at055612 @stroomdev10