[teiid-issues] [JBoss JIRA] (TEIID-5089) Using Teiid Conn. importer in Designer, the cache name is set to "default"
[
https://issues.jboss.org/browse/TEIID-5089?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-5089:
------------------------------------
When importing from a data source, there is no "cache name" defined. In that
JDG server instance, there could several caches. Maybe there's a way to determine
which cache name s associated with the .proto being imported from.
As for adding a cache name importer property, it could be added and picked up. along with
the probufName, when the metadata processor is performing this task. Right now, its
pulling the name from the "default" cache.
Using Teiid Conn. importer in Designer, the cache name is set to
"default"
--------------------------------------------------------------------------
Key: TEIID-5089
URL: https://issues.jboss.org/browse/TEIID-5089
Project: Teiid
Issue Type: Bug
Components: Infinispan
Affects Versions: 8.12.x-6.4
Reporter: Van Halbert
Assignee: Van Halbert
When using the Teiid Connection importer in Designer to reversen engineer the source
table from an existing JDG cache. The following is an example of the DDL returned by
teiid:
{code}
SET NAMESPACE 'http://www.teiid.org/translator/infinispan/2017' AS teiid_ispn;
CREATE FOREIGN TABLE Person (
id integer OPTIONS (ANNOTATION '@Id', SEARCHABLE 'Searchable',
NATIVE_TYPE 'int32', "teiid_ispn:TAG" '1'),
name string OPTIONS (SEARCHABLE 'Searchable', NATIVE_TYPE 'string',
"teiid_ispn:TAG" '2'),
salary double OPTIONS (SEARCHABLE 'Searchable', NATIVE_TYPE 'double',
"teiid_ispn:TAG" '3'),
CONSTRAINT PK_ID PRIMARY KEY(id)
) OPTIONS (ANNOTATION '@Indexed', NAMEINSOURCE 'JDGPersonCache.Person',
UPDATABLE TRUE, "teiid_ispn:CACHE" 'default');
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)