org.finra.herd.service.impl

Class JdbcServiceImpl

java.lang.Object

org.finra.herd.service.impl.JdbcServiceImpl

All Implemented Interfaces:

JdbcService

@Service
public class JdbcServiceImpl
extends Object
implements JdbcService

Default implementation of JdbcService which uses Spring's JDBC wrapper framework to handle connections and transactions.

Field Summary

Fields

Modifier and Type	Field and Description
static String	DRIVER_MYSQL
static String	DRIVER_ORACLE
static String	DRIVER_POSTGRES
static String	DRIVER_REDSHIFT

Constructor Summary

Constructors

Constructor and Description
JdbcServiceImpl()

Method Summary

Modifier and Type	Method and Description
JdbcExecutionResponse	executeJdbc(JdbcExecutionRequest jdbcExecutionRequest) This implementation uses a DriverManagerDataSource and DefaultTransactionDefinition.
protected JdbcExecutionResponse	executeJdbcImpl(JdbcExecutionRequest jdbcExecutionRequest) This implementation uses a DriverManagerDataSource.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Detail

DRIVER_REDSHIFT

public static final String DRIVER_REDSHIFT

See Also:

Constant Field Values

DRIVER_POSTGRES

public static final String DRIVER_POSTGRES

See Also:

Constant Field Values

DRIVER_ORACLE

public static final String DRIVER_ORACLE

See Also:

Constant Field Values

DRIVER_MYSQL

public static final String DRIVER_MYSQL

See Also:

Constant Field Values

Constructor Detail

JdbcServiceImpl

public JdbcServiceImpl()

Method Detail

executeJdbc

@Transactional(propagation=NOT_SUPPORTED)
public JdbcExecutionResponse executeJdbc(JdbcExecutionRequest jdbcExecutionRequest)

This implementation uses a DriverManagerDataSource and DefaultTransactionDefinition. It suspends the existing transaction and purposely runs this logic in "no transaction" to ensure we don't create a connection that would potentially become idle while all JDBC tasks execute. If the underlying connection pool has an abandoned connection timeout, it would reclaim and close the connection. Then when all the JDBC tasks below finish, this transaction would try to commit and would generate a "commit failed" exception because the connection is already closed. This approach is fine since we are not actually doing any "herd" DB operations below. When all the below JDBC operations are finished, nothing would happen here except the callers transaction would pick up where it left off which would be needed to write workflow variables, etc.

Specified by:

executeJdbc in interface JdbcService

Parameters:

jdbcExecutionRequest - The JDBC execution request

Returns:

The JDBC execution response

executeJdbcImpl

protected JdbcExecutionResponse executeJdbcImpl(JdbcExecutionRequest jdbcExecutionRequest)

This implementation uses a DriverManagerDataSource. Uses existing Spring ORM transaction.

Parameters:

jdbcExecutionRequest - JDBC execution request

Returns:

JdbcExecutionResponse