ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitry Sherstobitov <sdn.x...@gmail.com>
Subject [DISCUSSION] Simplification of Ignite options and cache configuration
Date Wed, 17 Apr 2019 10:37:02 GMT
Dear Ignite developers,

I have some ideas about Ignite 3.0 release and simplifications that might be included in the
future release:

1. Remove  *_ENABLED/*_DISABLED from Ignite system properties. I see only one advantage in
this case - some information about default value: e.g. _ENABLED property is disabled by default.
On the other hand, you need to know is this property ends with _ENABLED to _DISABLED. Removing
these additions makes property names more clear and they will be easy to remember and use
(default values could be found in search engine as before) (https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteSystemProperties.html)
2. Group similar properties into sub-objects in CacheConfiguration. For example, all SQL properties
may be in some SQLCacheConfiguration object, writeThrough/readThrough may be in some sub-object
as well. This change makes CacheConfiguration class more clear and XML cache configuration
itself much easier to configure - the user has information about all properties in context
and which of them are mandatory.

Best regards,
Dmitriy Sherstobitov

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message