Yes, that much fine grained capabilities support is not available. Generally you need to detect that situation in code and issue an exception. You can define a column searchable or not, if it is searchable it will be eligible for pushdown for EQUALS and IN and Compare etc.
I am using unsearchable for some fields. The tricky thing is with filter capabilities that depend on the column. What I am thinking of is the ability to specify some capabilities on the columns themselves. For example, column X supports RANGED and EQUALS; columns Y and Z support EQUALS and IN.
Edit: Really just a clarification of my original post.
1 of 1 people found this helpful
There have been other users with similar requirements, but typically it has been satisfied with a combination of searchability/capabilities. This still seems to somewhat be straddling the notion of procedural access vs. a view - but that ultimately you want the client to access as a view correct?
Somewhat related to [TEIID-236] Procedural access pattern - JBoss Issue Tracker there is a case to be made for a restriction to just equality, in, is null, which would get you most of the way toward what you are looking for.