[teiid-issues] [JBoss JIRA] Updated: (TEIID-871) Refactor system vdb
Steven Hawkins (JIRA)
jira-events at lists.jboss.org
Tue Oct 13 11:45:05 EDT 2009
[ https://jira.jboss.org/jira/browse/TEIID-871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steven Hawkins updated TEIID-871:
---------------------------------
Description:
1. We should remove the system physical model - it's undocumented, exposes too much metadata cruft, and requires too much logic in the index connector to support it.
2. We should remove System.datatypeelements and System.datatypeelementproperties - the transformations are invalid (they will always return no rows) and they are redundant
3. There should be a new system table ProcedureParamProperties that exposes annotations for procedure params.
with System.element/datatype and the corresponding properties tables.
4. This one is open to debate, but I would also like to remove System.describe - since annotations are available directly on the appropriate type table, there doesn't seem to be a good reason to introduce a procedure that operates over all metadata records to return the same information.
5. The OA ODBC views should be moved into a separate vdb that can be optionally including along with the system vdb
was:
1. We should remove the system physical model - it's undocumented, exposes too much metadata cruft, and requires too much logic in the index connector to support it.
2. We should remove System.datatypeelements and System.datatypeelementproperties - the transformations are invalid (they will always return no rows) and they are redundant
3. There should be a new system table ProcedureParamProperties that exposes annotations for procedure params.
with System.element/datatype and the corresponding properties tables.
4. This one is open to debate, but I would also like to remove System.describe - since annotations are available directly on the appropriate type table, there doesn't seem to be a good reason to introduce a procedure that operates over all metadata records to return the same information.
> Refactor system vdb
> -------------------
>
> Key: TEIID-871
> URL: https://jira.jboss.org/jira/browse/TEIID-871
> Project: Teiid
> Issue Type: Sub-task
> Components: Query Engine
> Affects Versions: 6.3
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 6.3
>
>
> 1. We should remove the system physical model - it's undocumented, exposes too much metadata cruft, and requires too much logic in the index connector to support it.
> 2. We should remove System.datatypeelements and System.datatypeelementproperties - the transformations are invalid (they will always return no rows) and they are redundant
> 3. There should be a new system table ProcedureParamProperties that exposes annotations for procedure params.
> with System.element/datatype and the corresponding properties tables.
> 4. This one is open to debate, but I would also like to remove System.describe - since annotations are available directly on the appropriate type table, there doesn't seem to be a good reason to introduce a procedure that operates over all metadata records to return the same information.
> 5. The OA ODBC views should be moved into a separate vdb that can be optionally including along with the system vdb
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the teiid-issues
mailing list