There seems to be a misunderstanding here. Based upon internal timelines we will still
need to have designer releases along with the 6.x series of Teiid. However I don't
think that was clearly communicated. Given that, my statements are just around assuring
there is minimal impact from these changes - as had been previous discussed with the
integration liaison (Dan).
----- Original Message -----
From: "Barry Lafond" <blafond(a)redhat.com>
To: "Steven Hawkins" <shawkins(a)redhat.com>
Cc: "teiid-dev" <teiid-dev(a)lists.jboss.org>
Sent: Thursday, July 9, 2009 9:42:03 AM GMT -06:00 US/Canada Central
Subject: Re: [teiid-dev] Connector supplied metadata
Note that we have yet to formally discuss any details of a 6.2 Designer release, so you
might want to be careful about making assumptions about what may or may not be available
for 6.2 Teiid tooling.
----- Original Message -----
From: "Steven Hawkins" <shawkins(a)redhat.com>
To: "teiid-dev" <teiid-dev(a)lists.jboss.org>
Sent: Wednesday, July 8, 2009 12:06:25 PM GMT -06:00 US/Canada Central
Subject: [teiid-dev] Connector supplied metadata
covers allowing connectors to supply
metadata. An initial check-in of this feature was added last night. For those that are
interested have a look at TestVDBLessExecution in the test-integration module.
Through just a ConfigurationInfo.def file:
<Property Name="Name" Value="VDBLess" />
<Property Name="Version" Value="4" />
<Property Name="UseConnectorMetadata" Value="true" />
<Property Name="Name" Value="SummitData" />
<Connector Name="Text Connector" />
<Connector Name="Text Connector" ComponentType="Text File
The text connector supplies the metadata for the SummitData model (through the
TextDescriptor file). I'll have the wiring added for the JDBC connector shortly along
with additional metadata features, such as keys and procedures.
Note that the changes have heavily refactored the metadata module. The intention is for
6.2 Designer to specifically fork the the 6.1 version of the metadata code to provide
their own implementation of the QueryMetadataInterface with their legacy usage of
MetadataRecords. This does not require any api level changes on their part or changes to
the current preview integration mechanism. There are currently no plans to incorporate
this work into Designer as this is currently envisioned for ease of use of stand-alone
An issue that is open for discussion is that the connector api now exposes the
MetadataRecord objects as well as it the MetadataObject interfaces (Group, Element, etc).
A case could be made for expanding the MetadataObject interfaces to include getters and
setters for all relevant fields on MetadataRecords (there are currently many fields that
the user doesn't need to modify that are only used by index logic or are handled by
the MetadataFactory). We still however would need to have separate implementations of the
interfaces since the Designer preview feature would still provide metadata through its QMI
in the from of legacy MetadataRecords. If we do expand the interfaces in this way, we
would also probably want to add logic to ensure that no modifications can be performed
when the records are supplied as RuntimeMetadata.
One warning that should be added is that since the metadata is non-persistent direct usage
of uuid values in system tables should be discouraged.
teiid-dev mailing list