[ https://issues.jboss.org/browse/TEIID-1485?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-1485: ---------------------------------- Affects Version/s: 6.0.0 Priority: Minor (was: Major) Description: Create a table that has an access pattern. Then create a virtual procedure that selects data from the table, but does not satisfy the access pattern. Validate the procedure -- it will validate successfully. We should catch access pattern errors during validation. Instead, this results in run-time errors. See attached screenshot for an example. was: Create a table that has an access pattern. Then create a virtual procedure that selects data from the table, but does not satisfy the access pattern. Validate the procedure -- it will validate successfully. This is a bug. We should catch access pattern errors during validation. Instead, this results in run-time errors. See attached screenshot for an example. Component/s: Query Engine This was moved from the designer since the validation of access patterns is performed in Teiid. Other than the simple case shown in this issue it is generally hard to determine if an access pattern will be violated when contained under view layers and with complex predicates. A possible validation could simply check only if there is sufficient (but to not actually assess pushdown) criteria against a physical table. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira