spec
spec copied to clipboard
CESQL: clarify behaviours of errors in OR expressions
Currently, in the Go SDK V2, (type = 'dev.knative.example') OR (missingattribute = 'test') results in an error, even if type = 'dev.knative.example', so long as missingattribute is not set on the event. However, if this implementation were changed to eagerly return on a true value (which an optimized implementation should do), then the return value would be true.
We should
- Clarify whether the evaluation should be eager or not
- Open issues to any SDKs with an implementation that does not match the new, clarified spec
This issue is stale because it has been open for 30 days with no
activity. Mark as fresh by updating e.g., adding the comment /remove-lifecycle stale.
@Cali0707 can we close this one now?
Yes, I believe so. Thanks!