Basically what you are looking for is to push down parsetimestamp function to source. What kinds of source you are working with. If the source system supports it and Teiid translator for that source is configured as such then it can do that!
Thanks for your response.
My source is an oracle database.
No, I don't think this is a pushdown function issue.
When I query my view table as below,
select volume_id from viewmodel.volume where converted_date='2014-01-0100:00:00'
the generated source model query is:
SELECT g_0.volume_date_str, g_0.volume_id FROM source_s.volume AS g_0
This means, teiid is querying the string value from the source and then performing the filter on the resultset. The obvious reason is 'converted_date' in my viewmodel.volume is a computed value. So the above plan makes sense.
However, I want to explore if there is any way I can push that down to the source model query to allow the database to do the filtering.