Bug 780531 (SOA-2966)

Summary:	Teiid assumes fqns in transformations, but they are no longer required to be there
Product:	[JBoss] JBoss Enterprise SOA Platform 5	Reporter:	Steven Hawkins <shawkins>
Component:	EDS	Assignee:	Van Halbert <vhalbert>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	5.1.0 GA
Target Milestone:	---
Target Release:	5.2.0 ER1
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-2966
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-10-12 16:07:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Steven Hawkins 2011-03-08 13:55:11 UTC

Workaround: Workaround Exists
Workaround Description: If using hidden models or potentially conflicting session level temp table names, then use only fully qualified table/procedure names in Designer transformations.
project_key: SOA

It looks like with the uuid refactoring we no long maintain that the designer indexed transformations will contain only fully qualified group names.  

This will cause a good deal of problems at runtime as partially qualified names are subject to visibility rules and can conflict with session level tables.

I would prefer to address this on the teiid though better metadata logic, rather than requiring fqns in transformation queries.

Comment 1 Van Halbert 2011-03-08 13:55:12 UTC

Link: Added: This issue Cloned from TEIID-1489

Comment 2 Van Halbert 2011-03-08 13:55:56 UTC

Security: Added: Public

Comment 4 David Le Sage 2011-09-01 04:28:19 UTC

Release Notes Docs Status: Added: Documented as Resolved Issue
Writer: Added: dlesage
Release Notes Text: Added: https://issues.jboss.org/browse/TEIID-1489

Fully-qualified names were causing a variety of problems at runtime as partially-qualified names were subject to visibility rules and could conflict with session-level tables. To rectify this, fully-qualified names are no longer used.

Comment 5 Steven Hawkins 2011-09-01 12:58:58 UTC

Release Notes Text: Removed: https://issues.jboss.org/browse/TEIID-1489

Fully-qualified names were causing a variety of problems at runtime as partially-qualified names were subject to visibility rules and could conflict with session-level tables. To rectify this, fully-qualified names are no longer used. Added: https://issues.jboss.org/browse/TEIID-1489

Partially-qualified names were subject to visibility rules and could conflict with session-level tables. To rectify this, the runtime metadata was adjusted to resolve transformations as if it were the design-time metadata.

Comment 6 Paul Nittel 2011-10-12 16:07:58 UTC

Closed following discussion with engineering.