GraphDB-SE Entity Pool

compared with
Current by evgeni.milev
on Jun 04, 2015 15:59.

This line was removed.
This word was removed. This word was added.
This line was added.

Changes (6)

View Page History
* all new entities are kept in memory - not recommended for large transactions (> 100M statements) to prevent {{{*}OutOfMemoryErrors{*}}}
* good for large number of small transactions
* mandatory in recommended for cluster environment - ensures entity IDs consistency between worker nodes
* mandatory when used with Solr and Elascticsearch connectors. See more [here|Elasticsearch GraphDB Connector#ElasticsearchGraphDBConnector-Prerequisites] and [here|Elasticsearch GraphDB Connector#ElasticsearchGraphDBConnector-Prerequisites]
* should be used with [Solr|Solr GraphDB Connector#Prerequisites] and [Elascticsearch|Elasticsearch GraphDB Connector#Prerequisites] connectors.

h1. Configuration
| {{entity-pool-implementation}} | {{classic}} | default |
| | {{transactional-simple}} |
| | {{transactional}} | The recommended for the current version of GraphDB transactional implementation. \\
| | {{transactional}} | The recommended transactional implementation in the current version of GraphDB. \\
Currently For 6.2 it is {{{*}transactional-simple{*}}}. May change in future versions |