[teiid-issues] [JBoss JIRA] (TEIID-1803) VDB deployment in EDS can be extremely slow based upon indexing needs

[Steven Hawkins (Resolved) (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-1803.
-----------------------------------

           Labels:   (was: teiid)
    Fix Version/s: 7.6
       Resolution: Done


Changed the index loading logic to perform only a single scan over the index files, then build the metadata in memory.
                
> VDB deployment in EDS can be extremely slow based upon indexing needs
> ---------------------------------------------------------------------
>
>                 Key: TEIID-1803
>                 URL: https://issues.jboss.org/browse/TEIID-1803
>             Project: Teiid
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 7.1.1, 7.2, 7.3, 7.4
>         Environment: JBoss Enterprise Data Services Platform 5.1.0
>            Reporter: Johnathon Lee
>            Assignee: Steven Hawkins
>             Fix For: 7.6
>
>         Attachments: IndexMetadata.patch.txt
>
>
> Problem:
> The index metadata loading logic is not well optimized. In short, each time a call to IndexMetadataFactory.queryIndex is made the blocks are fully scanned.  For small VDBs there isn't much of an issue because of the block caching logic, but during a vdb deploy we could be constantly re-reading data from the files.
> Possible solution:
> The IndexMetadataFactory loading strategy should be made aware of the index file per schema strategy so that scans can be made per schema rather than against all index files. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira