[
https://issues.jboss.org/browse/TEIID-4896?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-4896:
-------------------------------------
I see "CACHE" extension metadata usage is consistent as designed, it does make
sure that during the selection or updates it does use the name to grab the correct cache
from CacheFactory.
I will change the code such that during the metadata import the cache name is set, such
that extra DDL statement is not required. It will be set to the default cache name that is
defined in the configuration. If it that is different from the default, then we can use
the DDL ALTER option to set to correct one. This will cut down one extra step.
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)