Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improve semantics of Qubole.configure #92

Open
rjainqb opened this issue Mar 18, 2015 · 1 comment
Open

Improve semantics of Qubole.configure #92

rjainqb opened this issue Mar 18, 2015 · 1 comment

Comments

@rjainqb
Copy link
Contributor

rjainqb commented Mar 18, 2015

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

  1. Disallow the user to run Qubole.configure more than once
    or
  2. If we allow it, then we should change cached_agent accordingly.
@rtvkiz
Copy link

rtvkiz commented Jul 16, 2021

Hi,
Is there any solution available to this yet?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rjainqb @rtvkiz