Closed arnoweiss closed 4 months ago
Hi @arnoweiss
i would not consider this a bug, this is a feature request of sorting by createdAt
property. It could be that
the sorting option is not available on that field in upstream EDC. I would consider this as enhancement and raise the
request in upstream EDC
Raised also on upstream EDC
Thanks! What feels buggy is that the case isn't handled (leading to HTTP 500) and the inconsistency between /v2/edrs/request
and /v2/policydefinitions/request
. That's why I'd leave it open and see if the feature upstream fixes that behavior.
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
https://github.com/eclipse-edc/Connector/pull/4337
I guess it will be available in the next TX-EDC release
Hey @arnoweiss
closing this. The upstream https://github.com/eclipse-edc/Connector/pull/4337 has been included in upstream 0.8.0 and therefore in the tractusx-edc
0.8.0-rc1
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.