Closed Shmuma closed 1 year ago
We have several createRelation methods in DefaultSource and every variant of those methods create ExasolConnectionManager instance, which supposed to be a singleton (caching jdbc connections). But we call those methods from each other (example: https://github.com/exasol/spark-connector/blob/main/exasol-jdbc/src/main/scala/com/exasol/spark/DefaultSource.scala#L138), so, it is possible to get several ConnectionManager instances.
createRelation
DefaultSource
After closer look in the code logic, it turned out not a problem, as ConnectionManager just creates new connections without pooling them.
We have several
createRelation
methods inDefaultSource
and every variant of those methods create ExasolConnectionManager instance, which supposed to be a singleton (caching jdbc connections). But we call those methods from each other (example: https://github.com/exasol/spark-connector/blob/main/exasol-jdbc/src/main/scala/com/exasol/spark/DefaultSource.scala#L138), so, it is possible to get several ConnectionManager instances.