Details
-
New Feature
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
-
0
-
SDK49
Description
A new feature request that came up is that in addition to specifying the connection up front, it should be possible to provide the connection information on a per-operation basis.
The proposal is to latch this onto the new ConnectionIdentifier feature, and if it is a URI/Connection String, extract all the necessary information from there and spin up a connection. A UUID/hashCode connection identifier that is temporary can be chosen as an example.
One important property is that if the connection identifier / URI Is the same, it should be reused like the other connections and shut down when the application is terminated.
Attachments
For Gerrit Dashboard: SPARKC-168 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
183911,3 | SPARKC-168: Allow ad-hoc connections on a per-operation basis | master | couchbase-spark-connector | Status: MERGED | +2 | +1 |
184461,3 | SPARKC-168: Allow ad-hoc connections on a per-operation basis | master | couchbase-spark-connector | Status: MERGED | +2 | +1 |