Bug 1331173

Summary:	Pull back TEIID-2754 to add reportAsViews functionality
Product:	[JBoss] JBoss Data Virtualization 6	Reporter:	Marc Shirley <mshirley>
Component:	Teiid	Assignee:	Van Halbert <vhalbert>
Status:	CLOSED NOTABUG	QA Contact:	Filip Elias <felias>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	aszczucz, blafond, drieden, jolee, mbaluch, thauser
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-27 21:06:46 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 Marc Shirley 2016-04-27 20:52:15 UTC

Description of problem:
Need TEIID-2754 pulled back to enable reportAsViews functionality.  Currently it does not seem to work for DV 6.2.  This is to enable a consistent reporting of virtual objects.  Currently, a virtual table is reported as "table" type in JDBC and "view" type through ODBC.  With reportAsViews functionality, it can be set as true to have a consistent reporting of "view" across transports.

Version-Release number of selected component (if applicable):
DV 6.2

How reproducible:
Always

Steps to Reproduce:
1. Connect to VDB
2. Run "select type from SYS.TABLES where name = 'mytable'" to view JDBC data
3. Run "select relkind from pg_catalog.pg_class where relname = 'mytable'"

Actual results:
JDBC shows value "Table", while ODBC shows 'v' indicating a view.

Expected results:
Both JDBC and ODBC should report the same type of object in the metadata.

Additional info:
reportAsViews is reported to be set to a default of "true" in Teiid 9.0 and later to consistently report virtual table/view objects as view objects.

Comment 2 Marc Shirley 2016-04-27 21:06:46 UTC

Closing due to misunderstanding of the expectations when setting reportAsViews. Setting reportAsViews will not change the type reported in SYS.TABLES, but will change the actual type returned for the virtual table to VIEW.  So, appears to be working as expected.