Azure / Azure/azure-rest-api-specs

Kusto Cluster: Language Extensions property is not working within PUT operation

Open
#9,910 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Azure Data Explorer customer-reported question Service Attention
Dominant language
TypeSpec
Stars
3.1k
Forks
6k
Avg merge
2d 22h
Merged PRs (30d)
444

Description

Specified language extensions (PYTHON, R) are not considered during a Kusto Cluster PUT operation using the azure-sdk-for-go client.

Used client: https://github.com/Azure/azure-sdk-for-go/blob/master/services/kusto/mgmt/2020-02-15/kusto

PUT specification:
https://github.com/Azure/azure-rest-api-specs/blob/master/specification/azure-kusto/resource-manager/Microsoft.Kusto/stable/2020-02-15/kusto.json#L59

Language extensions are not read-only property, hence they should be usable within a PUT:
https://github.com/Azure/azure-rest-api-specs/blob/master/specification/azure-kusto/resource-manager/Microsoft.Kusto/stable/2020-02-15/kusto.json#L2514

Expected behavior:
Cluster is created and selected language extensions are enabled during PUT operation.

Actual behavior:
Cluster is created, but language extensions won't be activated.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the PUT definition near line 59 and the language extensions property near line 2514 in specification/azure-kusto/resource-manager/Microsoft.Kusto/stable/2020-02-15/kusto.json. Compare how the property is represented for PUT with the reported azure-sdk-for-go request. Done means a PUT-created cluster activates the selected PYTHON and R extensions.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, go, openapi
Domain
api, backend-api-design, cloud
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.