[
https://issues.jboss.org/browse/TEIID-5101?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-5101:
-------------------------------------
Yes, you can mix and match the models that we supported, but one model two different
metadata types I am not sure that works. It not about generating the DDL, having that tag
reads the metadata from Infinispan's .proto file to amend the defined DDL such that
right data types, extension properties etc are generated by the metadata processor.
I am sure we can add in way to define "index" metadata and then also other
types, but this requires changes in the Teiid Server, I am not sure it is worth the time
as there is a good workaround and we want to retire the .vdb file.
.vdb with JDG data source, with NATIVE defined, throws exception
----------------------------------------------------------------
Key: TEIID-5101
URL:
https://issues.jboss.org/browse/TEIID-5101
Project: Teiid
Issue Type: Bug
Components: Infinispan
Affects Versions: 8.12.x-6.4
Reporter: Van Halbert
Assignee: Ramesh Reddy
Priority: Blocker
When a .vdb (created in designer), and the internal vdb.xml contains the <metadata
type="NATIVE"></metadata>, the vdb will not deploy.
However, it will work if the .vdb is exported to vdb xml, because the DDL and the NATIVE
tags are there.
Guessing that the translator doesn't know how to handle a .vdb file.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)