Log bug in JIRA with a sample VDB (Dynamic VDB) and query you are using.
1 of 1 people found this helpful
The vdb will likely not be useful if it references sources. Just the ddl and system query would be sufficient - can you do an export of the relevant schema(s)?. I can see from our unit tests that a SELECT * FROM SYS.PROPERTIES will return all properties, multiple values on columns etc. So it's not clear what you are seeing.
Yes, even I can see those properties when I do "Select * from SYS.Properties"
However, there is an existing join query which selects data from sys.columns and sys.properties, which works with Teiid 8.1
"select c.TableName,c.Name ,c.SupportsUpdates, p.Name as PropertyName, p.Value as PropertyValue from sys.Columns c LEFT OUTER JOIN sys.Properties p ON p.UID=c.UID where c.SchemaName = '5000_10"
where '5000_10' is the model name.
But when I try to execute same query against Teiid 8.3, it gives out just one property per column.
I tried to modify the query but it was giving unexpected results with each combination I tried.
To my surprise, the query works fine for single table and with Like clause -
"select c.TableName, c.Name, c.SupportsUpdates, p.Name as PropertyName, p.Value as PropertyValue from sys.Columns c LEFT OUTER JOIN sys.Properties p ON p.UID=c.UID where c.TableName = 'Activity' and p.name like '5000_10%'
but fails for all tables with where clause = "where p.name like '5000_10%'" giving only one property per column.
Can you please let me know why the original query fails in case Teiid 8.3 ?
The fix will also be in CR1.