Preferences EntityStore

Group ID	Artifact ID	Version
org.qi4j.extension	org.qi4j.extension.entitystore-preferences	0

Group ID	Artifact ID	Version
org.qi4j.extension	org.qi4j.extension.entitystore-preferences	0

Group ID	Artifact ID	Version
org.qi4j.extension	org.qi4j.extension.entitystore-redis	0

Group ID	Artifact ID	Version
org.qi4j.extension	org.qi4j.extension.entitystore-redis	0

Group ID	Artifact ID	Version
org.qi4j.extension	org.qi4j.extension.entitystore-riak	0

Group ID	Artifact ID	Version
org.qi4j.extension	org.qi4j.extension.entitystore-riak	0

SQL EntityStore

code

docs

tests

EntityStore service backed by a SQL database.

This extension fully leverage the SQL Library meaning that you must use it to assemble your DataSource and that you +

Qi4j
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
Glo ssaryÂ

SQL EntityStore

code

docs

tests

EntityStore service backed by a SQL data base.

This extension fully leverage the SQL Library meaning that you must use it to assemble your DataSource and that you get Circuit Breaker and JMX integration for free.

Tip

See the SQL Support Sample that demonstrate combined use of SQL Library, SQL EntityStore and SQL Index/Query.

The following SQL databases are supported:

PostgreSQL @@ -80,7 +80,7 @@ get Apache Derby and Oracle JavaDB

Each entity state is stored as a single row so maximum number of entities is the maximum number of rows per table supported by the underlying SQL database.

Implementations per database Vendor share a generic codebase but can override about everything SQL. As a consequence -they can have strong differences in terms of performance if they use vendor specific extensions.

TableÂ 79.Â Artifact

Group ID	Artifact ID	Version
org.qi4j.extension	org.qi4j.extension.entitystore-sql	0

Configuration

SQL EntityStore Configuration is optional and provides only one configur ation property: schemaName defaulted to +they can have strong differences in terms of performance if they use vendor specific extensions.

TableÂ 73.Â Artifact

Group ID	Artifact ID	Version
org.qi4j.extension	org.qi4j.extension.entitystore-sql	0

Configuration

SQL EntityStore Configuration is optional and provides only one configur ation property: schemaName defaulted to qi4j_es. On SQL databases that donât support schemas this configuration property is simply ignored.

The assembly snippets below show the DataSource assembly alongside the SQL EntityStore assembly. Remember to configure the DataSource properly, see SQL Library and Configure a Service.

PostgreSQL

Maximum number of entities is unlimited.

Assembly is done using the provided Assembler:

public void assemble( ModuleAssembly module )
     throws AssemblyException
@@ -233,4 +233,9 @@ password=

\ No newline at end of file +password=

\ No newline at end of file Modified: zest/site/content/qi4j/develop/extension-es-voldemort.html URL: http://svn.apache.org/viewvc/zest/site/content/qi4j/develop/extension-es-voldemort.html?rev=1685534&r1=1685533&r2=1685534&view=diff ============================================================================== --- zest/site/content/qi4j/develop/extension-es-voldemort.html (original) +++ zest/site/content/qi4j/develop/extension-es-voldemort.html Mon Jun 15 10:37:01 2015 @@ -66,4 +66,120 @@ })(); -

Qi4j
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
Glo ssaryÂ

Voldemort EntityStore

code

docs

tests

Voldemort EntityStore

Note

This Extension has no documentation yet. Learn how to contribute in Writing Documentation.

TableÂ 80.Â Artifact

Group ID	Artifact ID	Version
org.qi4j.extension	org.qi4j.extension.entitystore-voldemort	0

\ No newline at end of file +

Qi4j
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
Glo ssaryÂ

Voldemort EntityStore

code

docs

tests

EntityStore service back ed by Voldemort.

TableÂ 74.Â Artifact

Group ID	Artifact ID	Version
org.qi4j.extension	org.qi4j.extension.entitystore-voldemort	0

Assembly

Assembly is done using the provided Assembler.

@Override
+public void assemble( ModuleAssembly module )
+    throws AssemblyException
+{
+[...snip...]
+
+    new VoldemortAssembler().
+        visibleIn( Visibility.layer ).
+        withConfig( config, Visibility.layer ).
+        assemble( module );
+

Configuration

Most of the configuration of Voldemort is available in the Qi4j Configuration Entity.

    @Optional
+    Property<String> storeName();
+
+    [...snip...]
+
+    @Optional
+    Property<Integer> connectionTimeout();
+
+    /**
+     * The Bootstrap URL for Voldemort runtime to use.
+     * <p>
+     * The configuration property is optional. Default: "tcp://localhost:8581"
+     * </p>
+     * <p>
+     * This value is used to call voldemort.client.ClientConfig#setBootstrapUrls(java.util.List)
+     * </p>
+     *
+     * @return The property containing the bootstrap URL configuration.
+     */
+    @Optional
+    Property<List<String>> bootstrapUrl();
+
+    @Optional
+    Property<Boolean> enableJmx();
+
+    [...snip...]
+
+    @Optional
+    Property<Long> failureDetectorAsyncRecoveryInterval();
+
+    @Optional
+    Property<Long> failureDetectorBannagePeriod();
+
+    @Optional
+    Property<List<String>> failureDetectorCatastrophicErrorType();
+
+    @Optional
+    Property<String> failureDetectorImplementation();
+
+    @Optional
+    Property<Long> failureDetectoreRequestLengthThreshold();
+
+    @Optional
+    Property<Integer> failureDetectorThreshold();
+
+    @Optional
+    Property<Integer> failureDetectorThresholdCountMinimum();
+
+    @Optional
+    Property<Long> failureDetectorThreasholdInterval();
+
+    @Optional
+    Property<Integer> maxBootstrapRetries();
+
+    @Optional
+    Property<Integer> setMaxConnectionsPerNode();
+
+    @Optional
+    Property<Integer> maxQueueRequests();
+
+    @Optional
+    Property<Integer> maxThreads();
+
+    @Optional
+    Property<Integer> maxTotalConnections();
+
+    /** Voldemort has avolved the format over time, and this property sets which request format to use.
+     * See {@code voldemort.client.protocol.RequestFormatType} in Voldemort for further details.
+     *
+     * @return The configuration property that contains the request type formet used in Voldemort.
+     */
+    @Optional
+    Property<String> requestFormatType();
+
+    /** Sets the routing tier of this Voldemort runtime.
+     * <p>
+     *     Possible values are 'client' and 'server'. See {@code voldemort.client.RoutingTier} in
+     *     Voldemort for details.
+     * </p>
+     * @return the confirguration property that contains the Routing Tier setting for Voldemort.
+     */
+    @Optional
+    Property<String> routingTier();
+
+    @Optional
+    Property<Integer> routingTimeout();
+
+    [...snip...]
+
+    @Optional
+    Property<Integer> socketBufferSize();
+
+    @Optional
+    Property<Boolean> socketKeepAlive();
+
+    @Optional
+    Property<Integer> socketTimeout();
+
+    @Optional
+    Property<Integer> threadIdleTime();
+}
+

\ No newline at end of file Modified: zest/site/content/qi4j/develop/extension-index-elasticsearch.html URL: http://svn.apache.org/viewvc/zest/site/content/qi4j/develop/extension-index-elasticsearch.html?rev=1685534&r1=1685533&r2=1685534&view=diff ============================================================================== --- zest/site/content/qi4j/develop/extension-index-elasticsearch.html (original) +++ zest/site/content/qi4j/develop/extension-index-elasticsearch.html Mon Jun 15 10:37:01 2015 @@ -66,14 +66,14 @@ })(); -

Qi4j
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
Glo ssaryÂ

ElasticSearch Index/Query

code

docs

tests

Index/Query services backed by ElasticSearch search engine built on top of +

Qi4j
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
Glo ssaryÂ

ElasticSearch Index/Query

code

docs

tests

Index/Que ry services backed by ElasticSearch search engine built on top of Apache Lucene.

Warning

ElasticSearch Index/Query do not support ComplexQueries from the Query API, ie. queries by "example value".

Three modes of operation are supported:

in-memory ;
on-filesystem ;
clustered. -

TableÂ 81.Â Artifact

Group ID	Artifact ID	Version
org.qi4j.extension	org.qi4j.extension.indexing-elasticsearch	0

Embedded: in Memory or on FileSystem

Both in-memory and on-filesystem assemblies share the same configuration properties, see below.

In Memory Assembly

In-memory ElasticSearch Index/Query service relies on the FileConfig Library to decide where it stores its +

TableÂ 75.Â Artifact

Group ID	Artifact ID	Version
org.qi4j.extension	org.qi4j.extension.indexing-elasticsearch	0

Embedded: in Memory or on FileSystem

Both in-memory and on-filesystem assemblies share the same configuration properties, see below.

In Memory Assembly

In-memory ElasticSearch Index/Query service relies on the FileConfig Library to decide where it stores its transaction logs as thereâs no in-memory transaction log implementation in ElasticSearch.

Assembly is done using the provided Assembler:

new ESMemoryIndexQueryAssembler().withConfig( configModule, configVisibility ).assemble( module );

On FileSystem Assembly

Filesystem based ElasticSearch Index/Query service relies on the FileConfig Library to decide where it stores its index data, transaction logs etcâ¦

Assembly is done using the provided Assembler:

new ESFilesystemIndexQueryAssembler().withConfig( configModule, configVisibility ).assemble( module );
@@ -103,7 +103,7 @@ Associations set the In an ElasticSearch cluster
Assembly
Assembly is done using the provided Assembler:
new ESClusterIndexQueryAssembler().withConfig( configModule, configVisibility ).assemble( module );
+configuration.

`In an ElasticSearch cluster`

`Assembly`

Assembly is done using the provided Assembler:

new ESClusterIndexQueryAssembler().withConfig( configModule, configVisibility ).assemble( module );

`Configuration`

Here are the configuration properties for the clustered ElasticSearch Index/Query service. Note that it inherits the properties defined in the in-memory or on-filesystem configuration, see above.

public interface ElasticSearchClusterConfiguration
         extends ElasticSearchConfiguration
@@ -143,4 +143,9 @@ properties defined in the in-memory or o
 
 }

Again, all configuration properties are defaulted meaning that you can use ElasticSearch Index/Query service without -configuration.


\ No newline at end of file
+configuration.


\ No newline at end of file