@skarpeck: I don't have experience in Lakebase. My first thought on this issue, corporate firewall blocking outgoing connection to the lakebase public endpoint.Could you please also review if firewall allows Lakebase endpoint host on port 5432?
@nkrish: Thank you for the responseIf you don't need Spark parallelism, can you review these options?Option-1: APIfy the exe in a separate windows vm/container - call the API from Databricks. this call will be executed from the driver. Option-2...
@siva_pusarla: We use the following pattern and it works,1) Calling notebook - constant location used by Job. + src/framework + notebook_executor.py2) Callee notebooks - dynamic + src/app/notebooks ...
@dj4: Are you in a corporate proxy environment?Databricks Browser UI uses Web Sockets and sometimes the performance issues happen due to the security checks in the traffic.
