[teiid-issues] [JBoss JIRA] (TEIID-3658) VDBs may start before transport service

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13102766#comment-13102766 ] 

Steven Hawkins commented on TEIID-3658:
---------------------------------------

> It depends on VDB repository service, but not on VDB Service. A VDB Service represents a individual VDB. Either case that would be bad dependency to add.

Sorry I was mixing up vdb service and vdbrepository service.  As for adding the transports as dependencies to a vdb service that is something that seems more like a feature than a bug fix - as we could then also restrict the access of the vdb to only a subset of transports.

> I think we should consider removing this restriction, this is system metadata, just in different form, can't think of good reason why we should not include all the time, considering our pg transport will give us access to various other clients.

It's just continuity for those who have never enabled odbc access - then this metadata will not show up anywhere.  As it could in theory cause an unintended issue for someone that previous did not have odbc access enabled and has a pg source that exposes pg system tables.  Now user queries would need qualification where none was needed before.

It seems like we can:
1. add a listener to the vdbrepository service based TranportAdd
2. or make the odbc metadata enabled configuration part of the teiid subsystem and default to true, so that we would preserve the option to disable it

> VDBs may start before transport service
> ---------------------------------------
>
>                 Key: TEIID-3658
>                 URL: https://issues.jboss.org/browse/TEIID-3658
>             Project: Teiid
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 8.0
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>            Priority: Critical
>             Fix For: 8.12
>
>
> VDBs may start before transport services, which is an issue for ODBC access as the enabled flag on the vdbrepository is toggled in by the transport.  Any vdbs loaded prior to that point will not be properly accessible.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)