-
Notifications
You must be signed in to change notification settings - Fork 54
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
HTTP 500 on /v2/edrs/request with sortField #1380
Comments
Hi @arnoweiss i would not consider this a bug, this is a feature request of sorting by |
Raised also on upstream EDC |
Thanks! What feels buggy is that the case isn't handled (leading to HTTP 500) and the inconsistency between |
Yeah, i understand that feels buggy, but imho it's a missing feature (sorting by a field) instead of a wrong behavior :) |
Hi @arnoweiss it has been implemented in upstream EDC in this PR I guess it will be available in the next TX-EDC release |
Hey @arnoweiss closing this. The upstream eclipse-edc/Connector#4337 has been included in upstream 0.8.0 and therefore in the |
Describe the bug
When trying to sort for the
createdAt
property of an EDR, the Consumer Control Plane returns HTTP 500.To Reproduce
POST /v2/edrs/request
with body:Expected behavior
HTTP 200 with the relevant EDRs sorted by creation timestamp.
Similar scenarios:
/v2/edrs/request
:agreementId
works.https://w3id.org/edc/v0.0.1/ns/createdAt
crashes with HTTP 500./v2/policydefinitions/request
createdAt
works.@id
crashes with HTTP 500.Screenshots/Error Messages
Control Plane Logs
Context Information
Possible Implementation
This may be an upstream issue. The relevant class (EndpointDataReferenceEntry) indeed has no
createdAt
field. Other payloads (such as IdResponse) have it. Yet, thecreatedAt
property is correctly returned if thesortField
andsortProperty
are not set in theQuerySpec
request.The text was updated successfully, but these errors were encountered: