2 Replies Latest reply on Jan 21, 2014 7:16 AM by Sanjeev Gour

    Performance cost of setting SearchType.Unsearchable on column metadata

    Sanjeev Gour Novice

      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-




      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.