-
Notifications
You must be signed in to change notification settings - Fork 128
Java: Document @Capabilities.ExpandRestrictions.*
#1958
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
base: main
Are you sure you want to change the base?
Conversation
Co-authored-by: Adrian Görler <[email protected]>
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.
Looks good!
@@ -528,17 +528,29 @@ The total number of request of OData batches can be limited by application confi | |||
|
|||
<div class="impl java"> | |||
|
|||
Settings <Config java>cds.odataV4.batch.maxRequests</Config> resp. <Config java>cds.odataV2.batch.maxRequests</Config> specify the corresponding limits. | |||
Use settings <Config java>cds.odataV4.batch.maxRequests</Config> resp. <Config java>cds.odataV2.batch.maxRequests</Config> to limit the amount of queries per OData `$batch`. |
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 way we have implemented this, it is not really a HTTP Server / Protocol Adapter specific thing, as it also applies on ApplicationService
-level. Should we somehow make that clear?
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 wonder if that is more about the runtime than about protocol adapter.
Next chapter?
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 annotations are from OData, so Protocol Adapter section from that perspective makes sense. Maybe we can just mention it in the text?
NB: The feature will be released in 4.2.0. |
Mentions
@Capabilities.ExpandRestrictions.*
.I wonder if that is more about the runtime than about protocol adapter.