[
https://issues.redhat.com/browse/TEIID-5928?page=com.atlassian.jira.plugi...
]
Steven Hawkins resolved TEIID-5928.
-----------------------------------
Resolution: Done
Marking as resolved. Added for external materialization when using the loadnumber
strategy, and for internal materialization - which has some additional caveats noted in
the docs. Additional work to smooth out the limitations or add support for external
without specifying the loadnumber is possible, but it would be best to get some usage out
of this first.
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
Fix For: 15.0
Original Estimate: 1 day, 4 hours
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)