Hello Lseg team, We are currently exploring a proof of concept for a cascading caching service in our UAT environment. As part of this, we require that the cascading service only exposes a specific subset of FIDs from the source service. Specifically, we would like to know if it is possible to perform static filtering of FIDs at the ADS POP level, instead of implementing a dynamic publisher-based filtering mechanism. For example, our existing service, RTDS_MD, presents FIDs 22, 23, 30, 36, and 41. We are in the process of creating a new cascading service called RTDS_MD_NEW_CASCADE, which will cascade from RTDS_MD but should only present FIDs 30 and 36. Could you please advise on whether this static filtering can be achieved at the ADS POP level? We had gone through ADS document, but we want to filter on certain fids irrespectively, not through fids with value example as below.
*ads*ELEKTRON_DD*filterField : 259
*ads*ELEKTRON_DD*filterFieldValues : 178
*ads*ELEKTRON_DD*filterList178*contains : 30, 36
*ads*ELEKTRON_DD*filterList178*remove :
Any guidance or recommendations you could provide on how best to implement this would be greatly appreciated. Looking forward to your expert advice. Regards, Rajkumar Gajam
