[teiid-issues] [JBoss JIRA] Closed: (TEIID-164) Connector api overhaul

[Steven Hawkins (JIRA)]

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

Steven Hawkins closed TEIID-164.
--------------------------------

    Resolution: Done


All 6.0.0 issues are out of the way.  The documentation changes will be made with 6.1.0.

> Connector api overhaul
> ----------------------
>
>                 Key: TEIID-164
>                 URL: https://jira.jboss.org/jira/browse/TEIID-164
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Connector API, Documentation, Misc. Connectors, Query Engine
>    Affects Versions: 6.0.0
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>            Priority: Critical
>             Fix For: 6.0.0
>
>
> Proposed changes:
> Remove getMetadata from connection - if and when it is implemented it will be an optional interface.
> Rename Connection.release to close and PoolAwareConnection.releaseCalled to closeCalled
> Remove ConnectorCapabilities.supportsExecutionMode and replace Asynch/SynchQuery, Asynch/SynchQueryCommand, Batched Executions with ResultSetExecution, also remove BatchedUpdate and BulkInsert Executions, which can be generalized on UpdateExecution.  
> BatchedUpdate and BulkInsert support would be indicated by capabilities on ConnectorCapabilities.  
> Execution mode integer constants would no longer be used, instead the ICommand object would be passed to the Connection.createExecution method.
> Asynch Connectors are created by modifying execution logic to throw a DataNotAvailableException, which contains the next poll interval.  This removes the need for special executions.
> ResultSetExecution would use an iteration approach, which removes the need for Batch and BasicBatch (FEDERATE-311)
> Connector batch size would be available on the ExecutionContext, rather than explicitly being passed to the execute method.
> Additionally all deprecated classes would be removed and a 5.5. compatibility layer created.  Current deprecations are:
> Deprecated ConnectorCapabilities scope, and added GlobalCapabilitiesProvider
> Deprecated ConnectionPool/DisabledConnectionPool/ConnectionPoolException, since pooling can be provided automatically
> Deprecated Asynch/SynchQueryExecution, and added Asynch/SynchQueryCommandExecution

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira