2:37 p.m.
Van Halbert created TEIID-1992:
----------------------------------
Summary: Create Connector/Translator to support Infinispan as a data source
Key: TEIID-1992
URL: https://issues.jboss.org/browse/TEIID-1992
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Van Halbert
Assignee: Van Halbert
Create a Connector/Translator in order for Teiid to support Infinispan as a read-only data
source on its initial release. Read Only because if someone is building an object cache,
the primary means for updating the cache would not be thru relational means. However, if
someone is wanting to add an object cache as a disparate data source for data integration
for exposing the content, then this connector/translator will enable that.
A goal here is to build an object translator framework that can easily plug in other
object cache sources. Example, add support for Coherence. There was a Coherence
connector/translator already created in the sandbox, for which, it will provide direction
for the object translator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:37 p.m.
[
https://issues.jboss.org/browse/TEIID-1992?page=com.atlassian.jira.plugin...
]
Work on TEIID-1992 started by Van Halbert.
Create Connector/Translator to support Infinispan as a data source
------------------------------------------------------------------
Key: TEIID-1992
URL: https://issues.jboss.org/browse/TEIID-1992
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Van Halbert
Assignee: Van Halbert
Create a Connector/Translator in order for Teiid to support Infinispan as a read-only
data source on its initial release. Read Only because if someone is building an object
cache, the primary means for updating the cache would not be thru relational means.
However, if someone is wanting to add an object cache as a disparate data source for data
integration for exposing the content, then this connector/translator will enable that.
A goal here is to build an object translator framework that can easily plug in other
object cache sources. Example, add support for Coherence. There was a Coherence
connector/translator already created in the sandbox, for which, it will provide direction
for the object translator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:37 p.m.
[
https://issues.jboss.org/browse/TEIID-1992?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-1992:
------------------------------------
Would like to get this to work with 7.7, however the local cache version will not work
because of conflicting logging jar dependencies. However, will create this for 8.x and
look to back port support to 7.7 using the Infinispan remote connection option.
Create Connector/Translator to support Infinispan as a data source
------------------------------------------------------------------
Key: TEIID-1992
URL: https://issues.jboss.org/browse/TEIID-1992
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Van Halbert
Assignee: Van Halbert
Create a Connector/Translator in order for Teiid to support Infinispan as a read-only
data source on its initial release. Read Only because if someone is building an object
cache, the primary means for updating the cache would not be thru relational means.
However, if someone is wanting to add an object cache as a disparate data source for data
integration for exposing the content, then this connector/translator will enable that.
A goal here is to build an object translator framework that can easily plug in other
object cache sources. Example, add support for Coherence. There was a Coherence
connector/translator already created in the sandbox, for which, it will provide direction
for the object translator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:35 p.m.
[
https://issues.jboss.org/browse/TEIID-1992?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-1992:
-------------------------------------
For 7.7 to work, Infinispan and JBoss Cache need co-exist in a JBoss 5.1 AS.
So the idea behind your implementation is to read the JPA objects in the Infinispan to
provide content for integration right?
I do not think I understand your comment about Coherence, so this translator will be basis
for developing the Coherence translator?
Create Connector/Translator to support Infinispan as a data source
------------------------------------------------------------------
Key: TEIID-1992
URL: https://issues.jboss.org/browse/TEIID-1992
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Van Halbert
Assignee: Van Halbert
Create a Connector/Translator in order for Teiid to support Infinispan as a read-only
data source on its initial release. Read Only because if someone is building an object
cache, the primary means for updating the cache would not be thru relational means.
However, if someone is wanting to add an object cache as a disparate data source for data
integration for exposing the content, then this connector/translator will enable that.
A goal here is to build an object translator framework that can easily plug in other
object cache sources. Example, add support for Coherence. There was a Coherence
connector/translator already created in the sandbox, for which, it will provide direction
for the object translator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:43 p.m.
[
https://issues.jboss.org/browse/TEIID-1992?page=com.atlassian.jira.plugin...
]
Ken Johnson commented on TEIID-1992:
------------------------------------
I think the goal here should be accessing Infinispan/DataGrid remotely, not in process.
Separate JVMs.
Create Connector/Translator to support Infinispan as a data source
------------------------------------------------------------------
Key: TEIID-1992
URL: https://issues.jboss.org/browse/TEIID-1992
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Van Halbert
Assignee: Van Halbert
Create a Connector/Translator in order for Teiid to support Infinispan as a read-only
data source on its initial release. Read Only because if someone is building an object
cache, the primary means for updating the cache would not be thru relational means.
However, if someone is wanting to add an object cache as a disparate data source for data
integration for exposing the content, then this connector/translator will enable that.
A goal here is to build an object translator framework that can easily plug in other
object cache sources. Example, add support for Coherence. There was a Coherence
connector/translator already created in the sandbox, for which, it will provide direction
for the object translator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:53 p.m.
[
https://issues.jboss.org/browse/TEIID-1992?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-1992:
------------------------------------
Infinispan and Coherence are both object caches. The logic to retrieve from the cache
will be implementation specific to how each performs queries on the cache. They each
provide features for querying, but done differently. However, to deconstruct (translate)
an object into relational will be the same for both. This could be the common logic for
any supported object cache. I see the possibility of this being setup similar to the way
jdbc implementations are done.
Create Connector/Translator to support Infinispan as a data source
------------------------------------------------------------------
Key: TEIID-1992
URL: https://issues.jboss.org/browse/TEIID-1992
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Van Halbert
Assignee: Van Halbert
Create a Connector/Translator in order for Teiid to support Infinispan as a read-only
data source on its initial release. Read Only because if someone is building an object
cache, the primary means for updating the cache would not be thru relational means.
However, if someone is wanting to add an object cache as a disparate data source for data
integration for exposing the content, then this connector/translator will enable that.
A goal here is to build an object translator framework that can easily plug in other
object cache sources. Example, add support for Coherence. There was a Coherence
connector/translator already created in the sandbox, for which, it will provide direction
for the object translator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:53 p.m.
[
https://issues.jboss.org/browse/TEIID-1992?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-1992:
------------------------------------
Infinispan and Coherence are both object caches. The logic to retrieve from the cache
will be implementation specific to how each performs queries on the cache. They each
provide features for querying, but done differently. However, to deconstruct (translate)
an object into relational will be the same for both. This could be the common logic for
any supported object cache. I see the possibility of this being setup similar to the way
jdbc implementations are done.
Create Connector/Translator to support Infinispan as a data source
------------------------------------------------------------------
Key: TEIID-1992
URL: https://issues.jboss.org/browse/TEIID-1992
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Van Halbert
Assignee: Van Halbert
Create a Connector/Translator in order for Teiid to support Infinispan as a read-only
data source on its initial release. Read Only because if someone is building an object
cache, the primary means for updating the cache would not be thru relational means.
However, if someone is wanting to add an object cache as a disparate data source for data
integration for exposing the content, then this connector/translator will enable that.
A goal here is to build an object translator framework that can easily plug in other
object cache sources. Example, add support for Coherence. There was a Coherence
connector/translator already created in the sandbox, for which, it will provide direction
for the object translator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:55 p.m.
[
https://issues.jboss.org/browse/TEIID-1992?page=com.atlassian.jira.plugin...
]
Van Halbert updated TEIID-1992:
-------------------------------
Comment: was deleted
(was: Infinispan and Coherence are both object caches. The logic to retrieve from the
cache will be implementation specific to how each performs queries on the cache. They
each provide features for querying, but done differently. However, to deconstruct
(translate) an object into relational will be the same for both. This could be the
common logic for any supported object cache. I see the possibility of this being setup
similar to the way jdbc implementations are done. )
Create Connector/Translator to support Infinispan as a data source
------------------------------------------------------------------
Key: TEIID-1992
URL: https://issues.jboss.org/browse/TEIID-1992
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Van Halbert
Assignee: Van Halbert
Create a Connector/Translator in order for Teiid to support Infinispan as a read-only
data source on its initial release. Read Only because if someone is building an object
cache, the primary means for updating the cache would not be thru relational means.
However, if someone is wanting to add an object cache as a disparate data source for data
integration for exposing the content, then this connector/translator will enable that.
A goal here is to build an object translator framework that can easily plug in other
object cache sources. Example, add support for Coherence. There was a Coherence
connector/translator already created in the sandbox, for which, it will provide direction
for the object translator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4 p.m.
[
https://issues.jboss.org/browse/TEIID-1992?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1992:
---------------------------------------
OGM provides a JPA to infinispan bridge that in theory can provide an entry point to other
object/cache systems. That may be a good approach for us to piggy back off of. Also see
the salesforce translator for logic that handles parent/child and child/parent
relationship queries via restricted join support (only left outer join using key criteria
and only to a single relationship level). This allows for somewhat natural queries
against that are well-performing rather than requiring separate retrievals of each side of
the relationship.
Create Connector/Translator to support Infinispan as a data source
------------------------------------------------------------------
Key: TEIID-1992
URL: https://issues.jboss.org/browse/TEIID-1992
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Van Halbert
Assignee: Van Halbert
Create a Connector/Translator in order for Teiid to support Infinispan as a read-only
data source on its initial release. Read Only because if someone is building an object
cache, the primary means for updating the cache would not be thru relational means.
However, if someone is wanting to add an object cache as a disparate data source for data
integration for exposing the content, then this connector/translator will enable that.
A goal here is to build an object translator framework that can easily plug in other
object cache sources. Example, add support for Coherence. There was a Coherence
connector/translator already created in the sandbox, for which, it will provide direction
for the object translator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:56 p.m.
[
https://issues.jboss.org/browse/TEIID-1992?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-1992:
-------------------------------------
While learning little more about the JPA support, I see that this can lead to many more
sources too. The [http://www.datanucleus.org] project supports few more big data stores
with JPA access.
Create Connector/Translator to support Infinispan as a data source
------------------------------------------------------------------
Key: TEIID-1992
URL: https://issues.jboss.org/browse/TEIID-1992
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Van Halbert
Assignee: Van Halbert
Create a Connector/Translator in order for Teiid to support Infinispan as a read-only
data source on its initial release. Read Only because if someone is building an object
cache, the primary means for updating the cache would not be thru relational means.
However, if someone is wanting to add an object cache as a disparate data source for data
integration for exposing the content, then this connector/translator will enable that.
A goal here is to build an object translator framework that can easily plug in other
object cache sources. Example, add support for Coherence. There was a Coherence
connector/translator already created in the sandbox, for which, it will provide direction
for the object translator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:08 p.m.
[
https://issues.jboss.org/browse/TEIID-1992?page=com.atlassian.jira.plugin...
]
Justin Hayes updated TEIID-1992:
--------------------------------
Attachment: ispn-integration.zip
Code that uses ispn to store indexes in a generic fashion so they can be queried via
hibernate/lucene integration into ispn.
Create Connector/Translator to support Infinispan as a data source
------------------------------------------------------------------
Key: TEIID-1992
URL: https://issues.jboss.org/browse/TEIID-1992
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Van Halbert
Assignee: Van Halbert
Attachments: ispn-integration.zip
Create a Connector/Translator in order for Teiid to support Infinispan as a read-only
data source on its initial release. Read Only because if someone is building an object
cache, the primary means for updating the cache would not be thru relational means.
However, if someone is wanting to add an object cache as a disparate data source for data
integration for exposing the content, then this connector/translator will enable that.
A goal here is to build an object translator framework that can easily plug in other
object cache sources. Example, add support for Coherence. There was a Coherence
connector/translator already created in the sandbox, for which, it will provide direction
for the object translator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:10 p.m.
[
https://issues.jboss.org/browse/TEIID-1992?page=com.atlassian.jira.plugin...
]
Justin Hayes commented on TEIID-1992:
-------------------------------------
The file I just attached is the module responsible for interfacing with ispn, primarily
for using it as the queryable index layer. The index entries are represented as objects of
type StringIndex, which includes a key and value representing the indexed field and value,
respectively. There is also a docId which is the UUID of the document from which the index
was extracted. It is these StringIndex objects that are stored in ispn and queried via the
lucene directory implementation. Check out the InfinispanService.searchIndex) method to
see how searching is done. The search returns a list of Strings, which are the UUIDs
(docId field) and the invoker is expected to use those UUIDs to load the full documents
from the data store.
This doesn't expose any way to "know" about the metadata stored within the
cache, so I'm not sure how useful it is for what you were already thinking of doing.
In fact, it was made to be the opposite - to support any type of index. That's why the
StringIndex class is so generic.
Create Connector/Translator to support Infinispan as a data source
------------------------------------------------------------------
Key: TEIID-1992
URL: https://issues.jboss.org/browse/TEIID-1992
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Van Halbert
Assignee: Van Halbert
Attachments: ispn-integration.zip
Create a Connector/Translator in order for Teiid to support Infinispan as a read-only
data source on its initial release. Read Only because if someone is building an object
cache, the primary means for updating the cache would not be thru relational means.
However, if someone is wanting to add an object cache as a disparate data source for data
integration for exposing the content, then this connector/translator will enable that.
A goal here is to build an object translator framework that can easily plug in other
object cache sources. Example, add support for Coherence. There was a Coherence
connector/translator already created in the sandbox, for which, it will provide direction
for the object translator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:40 p.m.
[
https://issues.jboss.org/browse/TEIID-1992?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-1992:
------------------------------------
Committed the translator-object, it contains only the core infrastructure for translating
an object (and its children) into results. Will add tasks to this jira for the steps to
making this translator operational to support infinispan and coherence, etc.
Create Connector/Translator to support Infinispan as a data source
------------------------------------------------------------------
Key: TEIID-1992
URL: https://issues.jboss.org/browse/TEIID-1992
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Van Halbert
Assignee: Van Halbert
Attachments: ispn-integration.zip
Create a Connector/Translator in order for Teiid to support Infinispan as a read-only
data source on its initial release. Read Only because if someone is building an object
cache, the primary means for updating the cache would not be thru relational means.
However, if someone is wanting to add an object cache as a disparate data source for data
integration for exposing the content, then this connector/translator will enable that.
A goal here is to build an object translator framework that can easily plug in other
object cache sources. Example, add support for Coherence. There was a Coherence
connector/translator already created in the sandbox, for which, it will provide direction
for the object translator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:18 p.m.
[
https://issues.jboss.org/browse/TEIID-1992?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-1992:
------------------------------------
The initial code for the translator-object project has been committed. It will support
searching either an Infinispan cache or any cache of type Map. In order to use this
translator, the OBJECTTABLE function will need to be used to process (turn into tabular
form) the object into a result set.
As of right now, there are 3 translator options and how they access their cache:
- infinispanCache (can use either jndi to get container, or load via configuration file)
- infinispanRemoteCache (can use either jndi, configuration file, or specify a server
list)
- mapCache (use jndi)
There are 2 options for searching:
- simple key criteria searching (EQUI and IN)
- Hibernate/Lucen search
The Infinispan translators support both options, where the mapCache only supports simple
seachings.
Create Connector/Translator to support Infinispan as a data source
------------------------------------------------------------------
Key: TEIID-1992
URL: https://issues.jboss.org/browse/TEIID-1992
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Van Halbert
Assignee: Van Halbert
Attachments: ispn-integration.zip
Create a Connector/Translator in order for Teiid to support Infinispan as a read-only
data source on its initial release. Read Only because if someone is building an object
cache, the primary means for updating the cache would not be thru relational means.
However, if someone is wanting to add an object cache as a disparate data source for data
integration for exposing the content, then this connector/translator will enable that.
A goal here is to build an object translator framework that can easily plug in other
object cache sources. Example, add support for Coherence. There was a Coherence
connector/translator already created in the sandbox, for which, it will provide direction
for the object translator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:20 p.m.
[
https://issues.jboss.org/browse/TEIID-1992?page=com.atlassian.jira.plugin...
]
Van Halbert edited comment on TEIID-1992 at 9/12/12 3:19 PM:
-------------------------------------------------------------
The initial code for the translator-object project has been committed. It will support
searching either an Infinispan cache or any cache of type Map. In order to use this
translator, the OBJECTTABLE function will need to be used to process (turn into tabular
form) the object into a result set.
As of right now, there are 3 translator options and how they access their cache:
- infinispanCache (can use either jndi to get container, or load via configuration file)
- infinispanRemoteCache (can use either jndi, configuration file, or specify a server
list)
- mapCache (use jndi)
There are 2 options for searching:
- simple key criteria searching (EQUI and IN)
- Hibernate/Lucen search (EQ, LT, GT, NE, Like, In, And/Or combinations)
The Infinispan translators support both options, where the mapCache only supports simple
seachings.
was (Author: van.halbert):
The initial code for the translator-object project has been committed. It will
support searching either an Infinispan cache or any cache of type Map. In order to use
this translator, the OBJECTTABLE function will need to be used to process (turn into
tabular form) the object into a result set.
As of right now, there are 3 translator options and how they access their cache:
- infinispanCache (can use either jndi to get container, or load via configuration file)
- infinispanRemoteCache (can use either jndi, configuration file, or specify a server
list)
- mapCache (use jndi)
There are 2 options for searching:
- simple key criteria searching (EQUI and IN)
- Hibernate/Lucen search
The Infinispan translators support both options, where the mapCache only supports simple
seachings.
Create Connector/Translator to support Infinispan as a data source
------------------------------------------------------------------
Key: TEIID-1992
URL: https://issues.jboss.org/browse/TEIID-1992
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Van Halbert
Assignee: Van Halbert
Attachments: ispn-integration.zip
Create a Connector/Translator in order for Teiid to support Infinispan as a read-only
data source on its initial release. Read Only because if someone is building an object
cache, the primary means for updating the cache would not be thru relational means.
However, if someone is wanting to add an object cache as a disparate data source for data
integration for exposing the content, then this connector/translator will enable that.
A goal here is to build an object translator framework that can easily plug in other
object cache sources. Example, add support for Coherence. There was a Coherence
connector/translator already created in the sandbox, for which, it will provide direction
for the object translator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:09 p.m.
[
https://issues.jboss.org/browse/TEIID-1992?page=com.atlassian.jira.plugin...
]
Van Halbert resolved TEIID-1992.
--------------------------------
Resolution: Done
I'm closing this jira because a lot of this was related to getting the feature in
7.7.1. I"ll create another jira to track all the tasks related to getting the
version of the object-translator into 8.x
Create Connector/Translator to support Infinispan as a data source
------------------------------------------------------------------
Key: TEIID-1992
URL: https://issues.jboss.org/browse/TEIID-1992
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Van Halbert
Assignee: Van Halbert
Attachments: ispn-integration.zip
Create a Connector/Translator in order for Teiid to support Infinispan as a read-only
data source on its initial release. Read Only because if someone is building an object
cache, the primary means for updating the cache would not be thru relational means.
However, if someone is wanting to add an object cache as a disparate data source for data
integration for exposing the content, then this connector/translator will enable that.
A goal here is to build an object translator framework that can easily plug in other
object cache sources. Example, add support for Coherence. There was a Coherence
connector/translator already created in the sandbox, for which, it will provide direction
for the object translator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:33 p.m.
[
https://issues.jboss.org/browse/TEIID-1992?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1992:
---------------------------------------
Van,
Were the capabilities of Justin's work integrated into the current translator?
Create Connector/Translator to support Infinispan as a data source
------------------------------------------------------------------
Key: TEIID-1992
URL: https://issues.jboss.org/browse/TEIID-1992
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Van Halbert
Assignee: Van Halbert
Attachments: ispn-integration.zip
Create a Connector/Translator in order for Teiid to support Infinispan as a read-only
data source on its initial release. Read Only because if someone is building an object
cache, the primary means for updating the cache would not be thru relational means.
However, if someone is wanting to add an object cache as a disparate data source for data
integration for exposing the content, then this connector/translator will enable that.
A goal here is to build an object translator framework that can easily plug in other
object cache sources. Example, add support for Coherence. There was a Coherence
connector/translator already created in the sandbox, for which, it will provide direction
for the object translator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:51 p.m.
[
https://issues.jboss.org/browse/TEIID-1992?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-1992:
------------------------------------
His methodology for performing searching is in the LuceneSearch component.
Create Connector/Translator to support Infinispan as a data source
------------------------------------------------------------------
Key: TEIID-1992
URL: https://issues.jboss.org/browse/TEIID-1992
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Van Halbert
Assignee: Van Halbert
Attachments: ispn-integration.zip
Create a Connector/Translator in order for Teiid to support Infinispan as a read-only
data source on its initial release. Read Only because if someone is building an object
cache, the primary means for updating the cache would not be thru relational means.
However, if someone is wanting to add an object cache as a disparate data source for data
integration for exposing the content, then this connector/translator will enable that.
A goal here is to build an object translator framework that can easily plug in other
object cache sources. Example, add support for Coherence. There was a Coherence
connector/translator already created in the sandbox, for which, it will provide direction
for the object translator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:43 p.m.
[
https://issues.jboss.org/browse/TEIID-1992?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-1992:
----------------------------------
Fix Version/s: 8.2
Affects Version/s: 8.2
Create Connector/Translator to support Infinispan as a data source
------------------------------------------------------------------
Key: TEIID-1992
URL: https://issues.jboss.org/browse/TEIID-1992
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Affects Versions: 8.2
Reporter: Van Halbert
Assignee: Van Halbert
Fix For: 8.2
Attachments: ispn-integration.zip
Create a Connector/Translator in order for Teiid to support Infinispan as a read-only
data source on its initial release. Read Only because if someone is building an object
cache, the primary means for updating the cache would not be thru relational means.
However, if someone is wanting to add an object cache as a disparate data source for data
integration for exposing the content, then this connector/translator will enable that.
A goal here is to build an object translator framework that can easily plug in other
object cache sources. Example, add support for Coherence. There was a Coherence
connector/translator already created in the sandbox, for which, it will provide direction
for the object translator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4179
days inactive
4408
days old
18 comments
5 participants
participants (5)
-
Justin Hayes (JIRA) -
Ken Johnson (JIRA)
-
Ramesh Reddy (JIRA)
-
Steven Hawkins (JIRA)
-
Van Halbert (JIRA)