Skip to end of metadata
Go to start of metadata

Infinispan Cache DSL Translator

The Infinispan Cache DSL Translator, known by the type infinispan-cache-dsl, can read the java objects from a remote Infinispan Cache via the Hot Rod client using the Google Protobuf for serialization. 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. If you are using Infinispan in library mode, see the Infinispan Cache Translator for this type of configuration.

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.

Installation

The infinispan-cache-dsl translator is not configured, out-of-the-box, in the standalone-teiid.xml configuration. To configure the translator, run the add-infinispan-cache-dsl-translator.cli script. This script can also be found in the teiid-jboss-dist.zip kit, under docs/teiid/datasources/infinispan. See the jdg-remote-cache quick start for an example. Note, this assumes you will be installing a separate JDG server, which will be accessed via the Hot Rod Client installed into the Teiid server.

Supported Capabilities

The following are the connector capabilities:

  • Compare Criteria - EQ
  • Compare Criteria Ordered - LT, GT, LE, GE - if the supportsCompareCriteriaOrdered translator override is set to true. It defaults to false due to an issue with JDG.
  • And/Or Criteria
  • In Criteria
  • Like Criteria
  • Order By
  • INSERT, UPDATE, DELETE (non-transactional)

The following will not be pushed down to JDG for processing, but will be done within Teiid:

  • Not (NE, <>)
  • IsNull

Limitations:

  • support for 'Not' has been disabled, because JDG considers <column when null> <> 1 to be true and SQL does not.
  • boolean data type: JDG will throw an exception if no value is specified on the insert or when no default value is defined in the protobuf definition file.
  • char data type: is not a supported type in theProtobuf data types (https://developers.google.com/protocol-buffers/docs/proto#scalar). Would either have to handle conversion in the protobuf marshaller or create a Teiid view with the data type as char.
  • 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.
  • Supports performing writes to the cache

Metadata

Definition Requirements
  • 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 data type for the attribute in the class must match the JDG cache key data type.
  • 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.
  • Columns will be identified as SEARCHABLE if either the protobuf definition for a column indicates its indexed or the pojo class has the attribute/method annotated.
  • 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.
Options for Defining

There are several options to defining the metadata representing your object in the cache.

  • "Recommended" Use the Teiid Connection Importer in Teiid Designer to create the physical source model based on your object cache.
  • Use dynamic VDB that only defines the data source to use. Example:

The metadata will be resolved by reverse engineering the defined object in the cache. This can be useful when using the Teiid Designer Teiid Connection Importer for building the physical source model(s).

  • Use dynamic VDB, but you define the metadata using DDL.

Note, this also shows a container class, PhoneNumber, as an example of the foreign key that's defines the relationship.

  • Use the Teiid Connection Importer Teiid Designer to manually create the physical source model based on your object cache using the above
    Usage patterns.

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.. 

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.