-
Notifications
You must be signed in to change notification settings - Fork 619
Rename new trigger filters sql field to cesql #6148
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
Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: devguyio The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Going to update the docs |
| // CESQL is a CloudEvents CESQL expression that will be evaluated to true or false against each CloudEvent. | ||
| // | ||
| // +optional | ||
| SQL string `json:"sql,omitempty"` |
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.
I like this proposal, and since we touch an alpha stage experimental feature, this seems right to do.
Makes it more explicit, rather than just a generic sql field on the API 👍
Codecov Report
@@ Coverage Diff @@
## main #6148 +/- ##
==========================================
- Coverage 82.09% 82.06% -0.03%
==========================================
Files 231 231
Lines 7765 7769 +4
==========================================
+ Hits 6375 6376 +1
- Misses 940 942 +2
- Partials 450 451 +1
Continue to review full report at Codecov.
|
|
Release note and docs added |
Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com>
pierDipi
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.
LGTM
| // | ||
| // +optional | ||
| SQL string `json:"sql,omitempty"` | ||
| CESQL string `json:"cesql,omitempty"` |
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 feels like a really confusing rename. Why not change Suffix to CESuffix and Exact to CEExact? Because those are all worse names and this filter is in the context of cloudevents filters. This is a docs problem, not an API naming problem.
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.
The feedback we've had so far is related to the strong database related connotation that comes with sql. What I read from the feedback is that calling it cesql makes it instantly obvious that this is a custom expression language related to CloudEvents.
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.
I agree with @devguyio - renaming to CESQL will help to avoid lot of user confusion and may help with google search in future ...
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.
I also think it's beneficial to change the name
Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com>
|
/retest |
|
/lgtm feel free to unhold ... |
odacremolbap
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.
nit: this comment might need updating
| // The feature set tests four filter dialects: exact, prefix, suffix and sql (aka CloudEvents SQL). |
Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com>
Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com>
Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com>
|
/retest-required |
|
/lgtm |
|
/unhold |
|
/retest |
1 similar comment
|
/retest |
|
It still looks like a flake to me, can't see any correlation to the changes introduced |
|
/retest |
1 similar comment
|
/retest |
|
@devguyio: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Proposed Changes
The original implementation of the SubscriptionsAPI Trigger filters #5715 used the dialect name
sql. The feedback from users was that this is a confusing name and thecesqlname is more in alignment with the Cloud Events SQL Expression Language spec.sqlfield tocesqlPre-review Checklist
E2E tests for any new behaviorSpec PR for any new API featureConformance test for any change to the specRelease Note
Docs
knative/docs#4737