If you have done the steps in "External Materialization" section correctly it will work as designed. Note that apart from setting a view table is "materialized", you need to also point to source table where you can load from. I suggest you go through the steps more carefully.
If not you would have to provide us with more debugging info on this to diagnose. Our internal tests work fine.
I was trying a few times based on the instruction but the view is still caching (internal). As such right now, no choice I point the view to the vw_<table> directly (without materialization) and using original source table to load the view similar to the instruction for external materialization. I might be missing something?
If you set the Materialized Table property on a materialized view, then internal materialization will not be used. With that property set, all queries without a nocache hint will go the materialized table rather than using the view query or internal materialization.
Basically I have a source view (Oracle) called MySourceView.
- I imported MySourceView to source schema called SRC (source)
- I created external schema with VW_MyExtTable called VWE and imported this is VWE schema (source)
- I created a view schema caled VIEW (view)
- I then created a view called MyTeiidView in schema VIEW in which transformation query is basically select * from SRC.MySourceView
- I then clicked on MyTeiidView, chose Materialized = true, chosen Materialized table = VWE.VW_MyExtTable
After deployed, when I query VIEW.MyTeiidView (select * from VIEW.MyTeiidView) the data is from SRC.MySourceView. From server log, internal materialization is called.
Can you provide the log?