[
https://issues.redhat.com/browse/TEIID-5928?page=com.atlassian.jira.plugi...
]
Rafael Sampaio commented on TEIID-5928:
---------------------------------------
Yes, you nailed it... That's what I think it should happen on a refresh.
My situation a true multi-source source table, and a Materialized view on top that with
discriminator column in the view.
I believe that if the multi-source table could be materialized would be a nice approach,
due to the problem you stated which is not easy to detect the multi-source nature of the
underlying tables used to build the view.
Thanks for your quick response.
Allow External and Internal materialization of multi-source to
fail/update individually
---------------------------------------------------------------------------------------
Key: TEIID-5928
URL:
https://issues.redhat.com/browse/TEIID-5928
Project: Teiid
Issue Type: Enhancement
Components: Common
Affects Versions: 12.2.2
Reporter: Rafael Sampaio
Assignee: Steven Hawkins
Priority: Major
Time Spent: 30 minutes
Remaining Estimate: 0 minutes
Hi, all.
First of all thanks in advance for your attention, and efforts on such a great product.
Since I haven't found any docs or examples regarding my current usage (please if this
already exists or there's a better way of doing this, disregard this request and
advice) here goes my suggestion:
It would be nice to have a way to gracefully update/fail per source, if a view that has
Materialization enabled and target a multi-source source model, because things can get,
messy if I have to create a view per source and Materialize each one and only then create
a unified (UNION) view.
Using this approach also obligates me to implement custom insert/update/delete/based on
the discriminator column.
Thanks again.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)