Infinispan DSL Translator

The Infinispan DSL Translator, known by the type infinispan-cache-dslm, can read the java objects from a remote Infinispan Cache via the Hot Rod client using the Google Protobuf for serialization. The objects will be reversed into a relational model, which can then be joined with other integrated data sources. The benefit of this JDG design is it will enable Teiid to query the cache using DSL, which is similar to doing Lucene searching on a local cache.

Properties

The Infinispan DSL Translator currently has no import or execution properties. See the JCA resource adapter section below as to how to configure the cache to be queried.

Supported Capabilities

The following are the connector capabilities:

• Compare Criteria - EQ, NE, LT, GT, LE, GE.
• And/Or Criteria
• In Criteria
• Like Criteria
• IsNull
• INSERT, UPDATE, DELETE (non-transactional)
  Limitations:
• 1-to-Many, currently only supports Collection or Array, not Map's'
• Write transactions not supported by JDG when using Hot Rod client
  To be done:
• support deleting containing class(s) (i.e., person --> phones, delete a phone)
• support updating containing class(s)

Usage

Retrieve objects from a cache and transform into rows and columns.

• Each google registered class in the cache will have a corresponding table created.
• The table for the root class, must have a primary key defined, which must map to an attribute in the class.
• The table "name in source" (NIS) will be the name of the JDG cache this table/class is stored
• The table columns will be created from the google protobuf definition, that corresponds to a registered class.
• Attributes defined as repeatable (i.e., collections, arrays, etc.) or a container class, will be supported as 1-to-* relationships, and will have corresponding registered class (if they are to be searched).
• A 1-to-* relationship class must have a foreign key to map to the root class/table, where the name in source for the foreign key is the name of the root class method to access those child objects. Note, this is the class method, not a reference in the google protobuf definition.
• A container/child class will have attributes where the NIS contain a period. Example: phone.number
  This is because this maps to to google protobuf definition and what is expected to be used in the DSL query.

Note that by just using a dynamic vdb, the metadata import logic will provide you with the physical table(s) that can be queried. An example is shown here for demonstration purposes. This also shows a container class, PhoneNumber, as an example of the foreign key that's defines the relationship.

<vdb name="PeopleVDB" version="1">
    <model name="People" visible="true">
        <property name="importer.useFullSchemaName" value="false"/>
       
        <source name="infinispan-cache-dsl-connector" translator-name="infinispan-cache-dsl" connection-jndi-name="java:/infinispanRemote" />

        <metadata type="DDL"><![CDATA[

 CREATE FOREIGN TABLE Person (
	PersonObject object OPTIONS (NAMEINSOURCE 'this', UPDATABLE FALSE, SEARCHABLE 'Unsearchable', NATIVE_TYPE 'java.lang.Object'),
	id integer NOT NULL OPTIONS (SEARCHABLE 'Searchable', NATIVE_TYPE 'int'),
	name string OPTIONS (SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'),
	email string OPTIONS (SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'),
	CONSTRAINT PK_ID PRIMARY KEY(id)
) OPTIONS (NAMEINSOURCE 'PersonsCache', UPDATABLE TRUE);

CREATE FOREIGN TABLE PhoneNumber (
	number string OPTIONS (NAMEINSOURCE 'phone.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'),
	type string OPTIONS (NAMEINSOURCE 'phone.type', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'),
	id integer NOT NULL OPTIONS (SELECTABLE FALSE, UPDATABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'),
	CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones')
) OPTIONS (NAMEINSOURCE 'PersonsCache', UPDATABLE TRUE);

         ]]> </metadata>
    </model>

</vdb>

JCA Resource Adapter

See the Infinispan-DSL resource adapter for this translator.   It can be configured to lookup the cache container via JNDI, server list, or hot rod properties..