Original Message:
Sent: 03-03-2025 05:14
From: Utsa Das
Subject: Limitation for Reltio External Queue (Amazon SQS)
Hi @vasanth p ,
Thanks for your information.
Could you please let me know if there is any retry mechanism present for below two scenarios :-
- If the external queue is down/full for some reason and any create/update from Reltio did not go to the queue , how to retry the same events to make sure we are not missing any events from reltio to external SQS queue.
- If for some reason/networking issue the messages did not go from queue to downstream system , how to make sure to get the same from the queue again once the network is up ?
------------------------------
Utsa Das
Novartis
Original Message:
Sent: 02-26-2025 01:28
From: vasanth p
Subject: Limitation for Reltio External Queue (Amazon SQS)
Reltio imposes certain limitations on SQS queues, primarily driven by AWS SQS restrictions. The key limitation is that the maximum message size for SQS is 256 KB. If a message exceeds this limit, it will not be delivered, and Reltio provides a workaround where it writes only the URI and event type for large objects. The full data must then be retrieved separately using an additional API call to Reltio.
If you need to reduce the message size, you can filter unnecessary fields by modifying the JMSEventsFilteringFields configuration. Additionally, Reltio does not provide a built-in way to identify oversized messages directly, but users can implement custom logic to check message sizes before sending them to the queue
------------------------------
vasanth p
Majix soultions
Original Message:
Sent: 02-25-2025 02:29
From: Utsa Das
Subject: Limitation for Reltio External Queue (Amazon SQS)
Hi Experts ,
We are designing real time and near time publish process through reltio external queue (Amazon SQS ).
Can you please let you know if there is any limitation/threshold values Reltio is having regarding SQS queues ?
------------------------------
Utsa Das
Novartis
------------------------------