Performance cost of setting SearchType.Unsearchable on column metadata

[sanjeev.gour]

We have a data source that supports filtering only on few specific columns and not on all. To get around this we are using the SearchType.Unsearchable to instruct Teiid to do the filtering on those columns which the data source cannot filter, like the following-

column.setSearchType(SearchType.Unsearchable);

We have certain load tests which run fine without this change, however, after making the change they seem to impact the performance and cause higher CPU consumption. The interesting thing is that those tests do not contain any of these columns (on which we have set the search type) in the where clause. It appears Teiid is still doing additional work on these columns. We need some information on this facility as to when it is suitable to use and what can be done in our case to make it efficient.

Appreciate any help.

Thanks.

Sanjeev.

[shawkins]

> The interesting thing is that those tests do not contain any of these columns (on which we have set the search type) in the where clause.

That would be unexpected.  You'll want to compare the query plans from the searchable and non-searchable versions of one of these queries.  From your description they should be the same.  If they are different the "set showplan debug" full debug log can help identify what has changed.

Steve

[sanjeev.gour]

Thanks Steve.

We have a bunch of queries executing in the test, we are trying to figure out the exact query causing the problem, once we have that, will post the query plan.