[
https://issues.redhat.com/browse/TEIID-5928?page=com.atlassian.jira.plugi...
]
Steven Hawkins commented on TEIID-5928:
---------------------------------------
So basically this is a request to automate the approach above - on a refresh instead of a
full snapshot, walk through or in parallel issue the individual refreshes to update each
source partition. That may be possible, but it will likely need some restrictions.
Is this a situation where you've partitioned the view manually? Or is this a true
multi-source scenario where you've added a materialized view directly above a source
multi-source table and the discriminator column is still exposed? The latter case can be
more complicated for us to deal with if we have to detect the multi-source nature through
multiple layers of views. If that is the case, something that we've talked about
before was allowing source tables to be marked as materialized which would further
simplify this detection.
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)