Page History

...

• Local caches (they are useless but require a lot of time to be supported)
• Scalar - it is already extremely outdated and noone asks for an update
• Visorcmd - a node that is always connected to the grid may be a destabilizing behavior; actionable utilities like control.sh make more sense
• Full text and spacial indexes - they are not persistent; should be rewritten for durable memory later on
• Schedule module - hardly used, local-only scheduling (same issues as with local cache)
• Explicit locks outside the transaction - lock concept is broken in a distributed system
• Modules with legacy library versions: hibernate-4.2, hibernate-5.1, spring-data, visor-console-2.10, etc?
• Remove current data structures (Lock, Semaphore, Set, Queue). Cache-based implementation leads to configuration issues. May be implemented on top of cache API in an auxiliary library or have an internal cache-free implementation
• AOP - hard to believe it's used
• Deprecated metrics - kept only for backward compatibility
• Checkpoint SPI - regular caches may be used as a storage, no need for another storage abstraction
• Old thin client and old JDBC connector
• GAR files - should be replaced with JAR files, no need for tasks scan inside the jar. Also, remove IgniteCompute methods executing tasks by task name
• Deprecated methods, fields and classes marked with `@deprecated`. Also revive IGNITE-6301 to remove indexedTypes field
• As many IGNITE_ parameters as possible from IgniteSystemProperties
• "Force server mode" for client nodes
• JSR107 (JCache) compatibility (useless but require a time to be supported)