[teiid-issues] [JBoss JIRA] (TEIID-1832) Change to source model connection through AdminApi using assignToModel() does not reflect in jdbc queries to that source model

Ramesh Reddy (Commented) (JIRA) jira-events at lists.jboss.org
Fri Nov 18 15:10:40 EST 2011


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

Ramesh Reddy commented on TEIID-1832:
-------------------------------------

This is only partially implemented for the 7.6. This will support the above usecase where the update has been made through the Admin API, however if the modification is made through the "admin-console" then the VDBMetadata is updated, however it will not switch the sources until the next re-start of the server. When the update has been made through the "admin-console" there is no interception point in the Teiid code, that can do needed modifications to VDB. So, this needs to be KI for now.

Targeting to 8.0 for full fix. 
                
> Change to source model connection through AdminApi using assignToModel() does not reflect in jdbc queries to that source model
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TEIID-1832
>                 URL: https://issues.jboss.org/browse/TEIID-1832
>             Project: Teiid
>          Issue Type: Bug
>          Components: AdminApi
>    Affects Versions: 7.5
>         Environment: Windows server 2008 R2, JBoss 5.1
>            Reporter: Farrukh Ihtisham
>            Assignee: Ramesh Reddy
>             Fix For: 7.6
>
>
> When source model's connection is changed using following adminapi code;
> AdminFactory adminFactory = AdminFactory.getInstance();
> Admin admin = adminFactory.createAdmin("admin", "admin".toCharArray(), "mms://localhost:31443"); 
> admin.assignToModel("Sample", 1, "SQLSourceA", "SQLSourceA", "sqlserver", "SQLSourceA_2");
> Any jdbc query result would still be from the old data source. However when verified using following adminapi code;
> VDB vdb = admin.getVDB("sample", 1);
> Model m = vdb.getModel("SQLSourceA");
> String jndiName = m.getSourceConnectionJndiName("SQLSourceA");
> The jndiName shows that the connection is successfully updated.

--
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

        


More information about the teiid-issues mailing list