Cluster actions always go through the v1.2 of the API #144
Comments
vogxn
pushed a commit
to vogxn/qds-sdk-py
that referenced
this issue
Mar 22, 2016
When creating clusters with the v1.3 of the API we still use the v1.2 endpoint during cluster creation. The _parse_create_update method accepts the api-version only to distinguish the request parameters. But the create, update and clone methods still use the default configuration of Qubole.agent(..) which is set to v1.2 unless all the actions in the session are configure(..)`ed with the v1.3 of the API. If you want to perform some of the unsupported actions with v1.3 of the cluster API but fall back to v1.2 for commands APIs we explicitly switch the version in the create(..)/update(..)/clone(..) calls which thereby alter the version for that API call alone and leave the cached_agent as is for the v1.2 APIs.
vogxn
pushed a commit
to vogxn/qds-sdk-py
that referenced
this issue
Mar 25, 2016
When creating clusters with the v1.3 of the API we still use the v1.2 endpoint during cluster creation. The _parse_create_update method accepts the api-version only to distinguish the request parameters. But the create, update and clone methods still use the default configuration of Qubole.agent(..) which is set to v1.2 unless all the actions in the session are configure(..)`ed with the v1.3 of the API. If you want to perform some of the unsupported actions with v1.3 of the cluster API but fall back to v1.2 for commands APIs we explicitly switch the version in the create(..)/update(..)/clone(..) calls which thereby alter the version for that API call alone and leave the cached_agent as is for the v1.2 APIs.
vogxn
pushed a commit
to vogxn/qds-sdk-py
that referenced
this issue
Mar 28, 2016
tests failures because the mock object receives the api_version that should have been removed as part of the payload sent in the request
harshashah16
pushed a commit
to harshashah16/qds-sdk-py
that referenced
this issue
Apr 18, 2016
…Request qubole#144. When creating clusters with the v1.3 of the API we still use the v1.2 endpoint during cluster creation. The _parse_create_update method accepts the api-version only to distinguish the request parameters. But the create, update and clone methods still use the default configuration of Qubole.agent(..) which is set to v1.2 unless all the actions in the session are configure(..)`ed with the v1.3 of the API. If you want to perform some of the unsupported actions with v1.3 of the cluster API but fall back to v1.2 for commands APIs we explicitly switch the version in the create(..)/update(..)/clone(..) calls which thereby alter the version for that API call alone and leave the cached_agent as is for the v1.2 APIs.
|
This is now merged |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When creating clusters with the
v1.3of the API we still use thev1.2endpoint during cluster creation. The_parse_create_updatemethod accepts the api-version only to distinguish the request parameters. But thecreate,updateandclonemethods still use the default configuration ofQubole.agent(..)which is set tov1.2unless all the actions in the session areconfigure(..)`ed with the v1.3 of the API.In my case I want to perform some of the unsupported actions with
v1.3of the cluster API but fall back tov1.2for commands APIs. One way to do this is to explicitly switch the version in thecreate(..)/update(..)/clone(..)calls which thereby alter the version for that API call alone and leave thecached_agentas is for the v1.2 APIs.The text was updated successfully, but these errors were encountered: