| 4 | |
| 5 | ---- |
| 6 | |
| 7 | == 2013-1-?: DeepaMehta 4.0.14 == |
| 8 | |
| 9 | Improvements: |
| 10 | * For better performance with large amounts of data the storage layer is completely rewritten. Traversal is speedup by a new Lucene association index (#389). |
| 11 | * Association user data is indexed as well (analogous to topic user data) (#389). |
| 12 | * More performant architecture: A storage implementation is coded directly to the DeepaMehta model API. The additional bridging layer is dropped. The concept of a DM-independant MehtaGraph API is abolished. There is no dependency on the external Neo4j MehtaGraph library anymore (#389). |
| 13 | * Modular storage layer: a new service provider interface (`de.deepamehta.core.storage.spi.DeepaMehtaStorage`) allows 3rd-party developers to implement the DeepaMehta storage layer based on alternate DBs (besides Neo4j). Storage implementations are deployed as OSGi services (#391). |
| 14 | * No transactions are created anymore for DB read operations. This may yield a performance benefit (#406). |
| 15 | * Delivering core events involves no runtime reflection anymore. This may yield a performance benefit (#352). |
| 16 | * AssociationDefinition API is simplified and redundancy is removed from serialization format (#393). |
| 17 | * Association's Instantiation associations can be queried by type (#338). |
| 18 | * Neo4j is updated from 1.8 to 1.8.1 |
| 19 | |
| 20 | Bug Fixes: |
| 21 | * This exception should no longer be thrown (#392): |
| 22 | `java.lang.IllegalArgumentException: Reference error: ID 1234 refers to a MehtaEdge when the caller expects a MehtaNode` |