Hello, we use Ignite as a cache in front of our databases (SQL Server, Oracle) and asked ourselves if the problem of index fragmentation, which is known from SQL databases, could also occur here. (for example see https://blog.devart.com/sql-server-index-fragmentation-in-depth.html).
Is there this danger with in memory or persistent caches? How does Ignite deal with this problem? This is especially interesting for tables that are constantly updated. Do we have to take appropriate measures for index maintenance such as Index Reorg/Rebuild? Regards David -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
