[
https://issues.jboss.org/browse/TEIID-4908?page=com.atlassian.jira.plugin...
]
Steve Tran updated TEIID-4908:
------------------------------
Steps to Reproduce:
1) Define a source table with three columns: COL_A, COL_B, COL_C
2) Define a View with three columns : colA, colB, colC
3) Create an Access Pattern, with COL_A, and COL_B.
4) Add view to VDB and Deploy
5) Access VDB through OData. Only supply $filter=colA eq '123456' to break the
access pattern rule.
6) The error message will list out the Access Pattern, but only use the true column names
instead of colA or ColB.
Access Pattern Messaging
------------------------
Key: TEIID-4908
URL:
https://issues.jboss.org/browse/TEIID-4908
Project: Teiid
Issue Type: Bug
Affects Versions: 8.12.8.6_3
Environment: JDV 6.3.2
Windows 7
Reporter: Steve Tran
Assignee: Steven Hawkins
When accessing a table that has an Access Pattern defined, the columns defined in the
access pattern don't necessarily match the columns being exposed by the view.
I'm aliasing the output of the query with friendly column names, while the Access
Pattern defines the access based on the real column names. When the user sees the Access
Pattern warning message, it can be confusing as to what columns they actually need to
supply.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)