[teiid-issues] [JBoss JIRA] (TEIID-5928) Allow External and Internal materialization of multi-source to fail/update individually

[Steven Hawkins (Jira)]

    [ https://issues.redhat.com/browse/TEIID-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201395#comment-14201395 ] 

Steven Hawkins commented on TEIID-5928:
---------------------------------------

To clarify this was initially implemented for external materialization when the loadnum column is added and is explicit in that it requires two new properties to be set to indicate which view column is the partitioning column and a query to provide the partition values.

This can be expanded to internal materialization, but requires further changes to the systemadmin procedure.

Allowing this form of update without the loadnumber column is problematic with non-transactional sources as you have to delete, then upsert/insert each partition leaving a window where things are invalid.  Here again though we could expand the logic and document the risks.

> 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: 0 minutes
>          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)