-
1. Re: Is materializing entire models possible?
rareddy May 6, 2016 4:49 AM (in response to m.ardito)Marco,
Yeah, we implemented a long time ago and did not work out as we expected with users and customers then we switched to using materializing on individual tables.
Ramesh..
-
2. Re: Is materializing entire models possible?
m.ardito May 6, 2016 5:03 AM (in response to rareddy)Thanks.
but is there a way to materialize even a single table without having to create a view that basically just reads all table fields, in order to materialize it? I just know this method, I'll dig more through docs....
but please point me in useful directions, if you feel..
Marco
-
3. Re: Is materializing entire models possible?
shawkins May 14, 2016 1:03 PM (in response to m.ardito)> but is there a way to materialize even a single table without having to create a view that basically just reads all table fields, in order to materialize it?
Not currently as there are some implementation limitations that make it easier to have the view requirement. Typically you do want to be selective about materialization as it's best applied as close as possible to the user queries - after federation and other processing.
It is possible to introduce a delegating or custom translator to pragmatically add materialized views at import time based upon the underlying metadata.
-
4. Re: Is materializing entire models possible?
m.ardito May 16, 2016 6:33 AM (in response to shawkins)Steven Hawkins ha scritto:
>Not currently as there are some implementation limitations that make it easier to have the view requirement.
ok
>Typically you do want to be selective about materialization as it's best applied as close as possible to the user queries - after federation and other processing.
of course, I was thinking about corner cases, like simple one-file datasources like google spreadsheets (of course ) which are abit slow to load, on my internet connection
I thought that if they could be auto-materialized, when users may want to add/remove/rename a new column (I could lock the fundamental ones) , their change could be reflected automatically, somehow.
>It is possible to introduce a delegating or custom translator to pragmatically add materialized views at import time based upon the underlying metadata.
Interesting, any example around?
As always, thanks,
Marco
-
5. Re: Is materializing entire models possible?
rareddy May 16, 2016 8:48 AM (in response to m.ardito)Take look at teiid/BaseDelegatingExecutionFactory.java at master · rareddy/teiid · GitHub and documentation at Delegating Translators | Teiid Documentation
Basically it is wrapper over any translator for cross cutting concerns, so here you would develop a class extending the BaseDelegatingExecutionFactory, and override the getMetadata method and create automatic view tables based on the metadata gathered from super.getMetadata method.