[JBoss JIRA] Updated: (TEIID-164) Connector api overhaul
by Steven Hawkins (JIRA)
[ https://jira.jboss.org/jira/browse/TEIID-164?page=com.atlassian.jira.plug... ]
Steven Hawkins updated TEIID-164:
---------------------------------
Component/s: Connector API
Documentation
Misc. Connectors
Query Engine
Fix Version/s: 6.0.0
Affects Version/s: 6.0.0
Repackaged and updated existing connectors. Still need to introduce the 5.5 compatibility layer.
> 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
15 years, 10 months
[JBoss JIRA] Work started: (TEIID-164) Connector api overhaul
by Steven Hawkins (JIRA)
[ https://jira.jboss.org/jira/browse/TEIID-164?page=com.atlassian.jira.plug... ]
Work on TEIID-164 started by Steven Hawkins.
> Connector api overhaul
> ----------------------
>
> Key: TEIID-164
> URL: https://jira.jboss.org/jira/browse/TEIID-164
> Project: Teiid
> Issue Type: Feature Request
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Critical
>
> 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
15 years, 10 months
[JBoss JIRA] Updated: (TEIID-309) System Host setup issues
by Steven Hawkins (JIRA)
[ https://jira.jboss.org/jira/browse/TEIID-309?page=com.atlassian.jira.plug... ]
Steven Hawkins updated TEIID-309:
---------------------------------
Component/s: Build/Kits
Fix Version/s: 6.1.0
Affects Version/s: 6.0.0
> System Host setup issues
> ------------------------
>
> Key: TEIID-309
> URL: https://jira.jboss.org/jira/browse/TEIID-309
> Project: Teiid
> Issue Type: Task
> Components: Build/Kits
> Affects Versions: 6.0.0
> Reporter: Ramesh Reddy
> Assignee: Van Halbert
> Fix For: 6.1.0
>
>
> 1) izpack does not make the startserver, stopserver, scripts as executable in the linux
> 2) There is no option for *not* starting the server (either way it does not look like starting the server). This option should be extended to "setupmm" driven process too, with additional property.
> 3) multicast port is not available in the IZpack + it is hard coded; Any two machines are seeing each other on the same multicast address. This needs to be fixed as soon as possible.(FEDERATE-340)
> 4) System name is always defaulting to $hostname, even when it is blank. I fixed this in install.
> 5) With "systenhostsetup.sh" I can not pass in the properties file, it is looking for the file in a fixed location.
> 6) systemhostsetup.sh creates the "metamatrix.properties" file, but does not write to the configuration about what it's config name is, thus never can be started.
--
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
15 years, 10 months