I am currently able to connect to a spark connection (Databricks) on Broadsea v2.0 by connecting to the webapi.source and webapi.source_daemon tables with the relevant connection details. When attempting to upgrade to Broadsea v3.0, I have updated those same tables with the same details, but am now receiving an error within my Simba driver “[Simba]SparkJDBCDriver Error initialized or created transport for authentication: problem accessing trust store.”
Looking this error up online, this appears to be a credentials issue, but I know this driver and connection details work because I am able to connect via DatabaseConnector from the Hades environment (in the Broadsea v3.0 container), but not when attempting to load the Atlas tool. These are also the same credentials from the previous version, so I believe my steps should still be correct. I am wondering if this is due to the Broadsea upgrade and how it communicates with webapi.
One last FYI, Broadsea v2.0’s flyway password for the webapi section of the docker-compose.yml
file needs to be updated for it to work. It looks like that password was changed to match the datasource password with the new release.