Conversation
|
Hi, what use-cases do you have in mind, where attachment can become heavy? The TMForum Spec recommends to only use the "content" field for small attachments and for bigger cases (pictures, videos etc.) to just link the attachment through the "url"-property. In order to save the database, we should rather go for a solution where the input is (create/update) is restricted to only accept contents under a certain size. |
|
Hi, Perhaps there has been a missuse, but in SBX large PDFs have been attached (e.g.: https://tmf.dome-marketplace-sbx.org/tmf-api/quoteManagement/v4/quote/urn:ngsi-ld:quote:014f8da2-2a39-4c99-a5d2-e22ce06de8bf) Entities like these are the reasons behind this proposal |
|
Hi, if in any instance such entities are inserted, they should be removed. And for preventing that in the future, input-checks should be implemented. |
Hi @wistefan
We got a ticket because in sbx because it had a problem while listing entities in Quote API.
The problem was that since attachment can get really heavy in terms of bytes the API would return an error 500 because the size limit was reached.
The solution we thought about it is the following: