Description
In a recent POC, I was exploring how JSON.SET FT.SEARCH and FT.AGGREGRATE commands work in case of a sharded architecture.
Turns out that JSON.SET / JSON.GET commands was making distributed calls to the entirety of the database, and automatic re-establishing connection with other node was happening.
But with FT.CREATE FT.SEARCH FT.AGGREGATE, while I was expecting the same result, they were not performing in a distributed fashion. Basically the index was getting created only on the single node, and hence the Search and Aggregate Operations were getting performed locally on a single node, and were not filtering documents across all the nodes.
The Cluster I made it locally as mentioned in Redis Cluster Setup
P.S. - I did some surfing over GPT, and it confirmed that Redis Enterprise Paid version provides a Distributed RediSearch functionality, but could not find any concrete documentation on the official Redis Docs.
Please confirm whether there is any such concept of Distributed RediSearch present at all, since then we would look on to using Redis as our primary database option with a highly horizontally scalable architecture