[
https://issues.jboss.org/browse/TEIID-4896?page=com.atlassian.jira.plugin...
]
Ramesh Reddy resolved TEIID-4896.
---------------------------------
Resolution: Done
The issue is when DDL is provided instead of .proto file as the metadata, internally the
DDL is first converted to .proto file and then DDL is generated back. However, during the
regeneration previously defined extension metadata on the DDL based tables is not restored
back to the original values, thus the error about duplicate/non-existing marshallers.
This fix copies the extension metadata back again on to the generated schema.
TEIID-4948 is duplicate
Two VDB's referencing same teiid_ispn:cache is not using the same
cache
-----------------------------------------------------------------------
Key: TEIID-4896
URL:
https://issues.jboss.org/browse/TEIID-4896
Project: Teiid
Issue Type: Bug
Components: Infinispan
Affects Versions: 9.3
Reporter: Van Halbert
Assignee: Ramesh Reddy
Fix For: 9.3.1
Attachments: jdg-remote-cache-ddl-vdb.xml,
jdg-remote-cache-registered-pb-vdb.xml
I have 2 VDB's where they both reference the same cache using OPTIONS property:
"teiid_ispn:cache" 'datasourceCache'
However, when I insert into one VDB, its not seen by the other VDB.
This was testing out the translators ability to use an already registered protobuf in
Infinispan.
The first VDB (jdg-remote-cache-vdb.xml) was deployed and then inserted and selected the
results. This registered the protobuf.
The second VDB (jdg-remote-cache-registered-pb-vdb.xml) was then deployed and was
expecting to be able to read the same cache. The metadata was derived correctly, but it
appears that one of the two are using the default cache, not the specified cache.
I'll attach the vdb's.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)