Reconsider dynamic indexing of attributes on query

[codingchili]

• Do we really want to index any attribute that is queried?
• Do we want to force users to create indexes before inserting? (SQLite+CQEngine only)
• Should users be able to specify indexes in addition to those queried? (on AsyncStorage)

A temporary workaround for CQEngine causes all indexes to be recreated when the application is restarted and an attribute for which an index has not been created for is queried.

System.setProperty("cqengine.reinit.preexisting.indexes", Boolean.TRUE.toString());

This will impact startup speeds for larger datasets. This only affects CQEngine with disk persistence, in this case CQEngine does not have access to the Attribute implementation to be used for the indexed attribute as it cannot be inferred from the index tables.

[codingchili]

Avoid using reflection for attributes as a primary loader on any store and allow clients to add indexes/attributes through the API.

Affects

• JsonStreamQuery/JsonMap
• PrivateMap
• SharedMap
• IndexedMapPersisted
• IndexedMapVolatile

Avoid using Serializer.getValueByPath by using an attribute loader added with the addIndex method.

[codingchili]

Changes in 1.3.0.

• Indexes are no longer added automatically when queried.
• Indexes can now be added manually with #addIndex in the AsyncStorage APIs.

This resolves some issues with ghost objects/duplicates caused by index inconsistencies.

Updating documentation for storages.

See https://github.com/npgall/cqengine/issues/242