Minor updates to ADL specs#253
Conversation
These clients don't need a subscriptionId.
Will add extensions that make it optional in C# and zero it out to an empty stream.
Issue: Azure/autorest#884 is tracking support for this being an optional param properly and not resulting in a null reference. So I will keep this spec as is.
Makes this more obvious to end users and easier to understand.
This API version changes the format for dates and timespan objects to be ISO compliant.
We need a way to have template parameters not be required when they are in the host. I will work with Amar for this next week.
This reverts commit be8b7bf.
Switch over to MSLISTSTATUS which gives more flexibility for listing files/folders.
explicitly calling out our chunked transfer APIs until issue: Azure/autorest#903 is resolved.
| } | ||
| }, | ||
| "x-ms-parameterized-host": { | ||
| "hostTemplate": "{accountName}.{adlaJobDnsSuffix}", |
There was a problem hiding this comment.
accountName will be added in the beginning by default. Please specify the positionInOperation: last.
Take a look at the documentation over here: https://github.com/Azure/autorest/blob/master/Documentation/swagger-extensions.md#x-ms-parameterized-host
I think, when the extension was designed initially, it was adding the path parameter in the end. Hence, when the extension was updated, datalake specs were updated accordingly. This seems like a new spec.
There was a problem hiding this comment.
I saw that, and we made the (painful) decision to take advantage of your change and move accountName back to the front, since it is much more consistent and in line with what we had in Hyak land. If it makes it more explicit, I can include the positionInOperation: first tag, if you like?
There was a problem hiding this comment.
the first is default. So you are good for now.
| "in": "query", | ||
| "required": false, | ||
| "type": "string", | ||
| "description": "The return format. Return the response in particular formatxii without access to request headers for standard content-type negotiation (e.g Orders?$format=json). Optional." |
There was a problem hiding this comment.
@begoldsm - formatxii. Make the change in your fork, so next time when you send the PR its fixed. Or may be send one; upto you.
3 participants
This set of changes has already been merged as the SDK pieces for node and .NET. Here are the changes: