Pavel, we can optionally enforce that, but not by default. Dmitry, the problem is the following. User configures Ignite cache and query entity, does several puts than empty results for SQL. The reason is very simple - typo in class name or simply different classes in configuration and of actual cache entry. The fix is pretty simple and make product more usable.
--Yakov
