-
Notifications
You must be signed in to change notification settings - Fork 235
feat: field selectors support for InformerEventSource #2835
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
Conversation
|
closes #2813 |
Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
| informer = | ||
| @Informer( | ||
| withFields = | ||
| @Field(field = "type", value = FieldSelectorTestReconciler.MY_SECRET_TYPE))) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems a little strange to me to read. Maybe "name" or "key" so it's not @Field(field = ... but of course this is just recommendation so feel free to discard it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it is a bit smelly.
Alternatively, we could have:
@FieldSelector(field="type", value="value", negated=false)
So there would not be with and without fields in @Informer just a list of @FieldSelector.
We might want to have similar api for java api for informers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@metacosm what do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
refactored it to a more explicit model, PTAL
xstefank
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Way better!
...ator-framework-core/src/main/java/io/javaoperatorsdk/operator/api/config/informer/Field.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
### What changes were proposed in this pull request? This PR aims to upgrade `operator-sdk` to 5.2.1 ### Why are the changes needed? To bring the latest improvements and bug fixes: - https://javaoperatorsdk.io/blog/2025/11/25/version-5.2-released/ - https://github.com/operator-framework/java-operator-sdk/releases/tag/v5.2.1 - https://github.com/operator-framework/java-operator-sdk/releases/tag/v5.2.0 - operator-framework/java-operator-sdk#2937 - operator-framework/java-operator-sdk#2934 - operator-framework/java-operator-sdk#2917 - operator-framework/java-operator-sdk#2835 ### Does this PR introduce _any_ user-facing change? No behavior change. ### How was this patch tested? Pass the CIs. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #424 from dongjoon-hyun/SPARK-54671. Authored-by: Dongjoon Hyun <dongjoon@apache.org> Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
Signed-off-by: Attila Mészáros a_meszaros@apple.com
closes #2813