Currently user can run Qubole.configure as many times as possible. It modifies auth_token, url, api_version etc. But these changes not reflected in the connection agent, because it is cached once and reused thereafter. So the semantics of Qubole.configure is incorrect. We should either
Disallow the user to run Qubole.configure more than once
or
If we allow it, then we should change cached_agent accordingly.
Currently user can run Qubole.configure as many times as possible. It modifies auth_token, url, api_version etc. But these changes not reflected in the connection agent, because it is cached once and reused thereafter. So the semantics of Qubole.configure is incorrect. We should either