[teiid-issues] [JBoss JIRA] (TEIID-5751) Please add optimization support for foreign keys in materialized tables

[Steven Hawkins (Jira)]

     [ https://issues.redhat.com/browse/TEIID-5751?focusedWorklogId=12450343&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-12450343 ]

Steven Hawkins logged work on TEIID-5751:
-----------------------------------------

                Author: Steven Hawkins
            Created on: 27/Feb/20 5:11 PM
            Start Date: 27/Feb/20 5:11 PM
    Worklog Time Spent: 2 hours 

Issue Time Tracking
-------------------

    Remaining Estimate: 30 minutes  (was: 2 hours, 30 minutes)
            Time Spent: 2 hours
            Worklog Id:     (was: 12450343)


> Please add optimization support for foreign keys in materialized tables
> -----------------------------------------------------------------------
>
>                 Key: TEIID-5751
>                 URL: https://issues.redhat.com/browse/TEIID-5751
>             Project: Teiid
>          Issue Type: Enhancement
>          Components: Query Engine
>    Affects Versions: 12.2
>            Reporter: Christoph John
>            Assignee: Steven Hawkins
>            Priority: Minor
>             Fix For: 13.1
>
>   Original Estimate: 2 hours, 30 minutes
>          Time Spent: 2 hours
>  Remaining Estimate: 30 minutes
>
> The issues came up in the following discussion
> https://developer.jboss.org/message/989502#989502
> > 1a) Are the constraints (indexes, foreign keys) now used to optimize queries in materialized tables or not?
>  
> Pk, Unique Key, and Indexes on the view will result in the creation of an index on the materialization target table and are fully utilized in planning decisions.  Things are a little more complicated with foreign keys.  {color:red}Currently they are not propagated onto the generated materialization target table metadata, so they are only considered in pre-planner activities, such as rewrite, before the view reference is replaced with the materialization target - but there aren't meaningful optimizations being made at that time based upon foreign key.  There are couple of narrow situations where that information would be useful{color}, so it probably should be added.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)