-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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.
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
(Public swagger update) Add TeradataSource,TeradataPartitionSettings,TeradataTableDataset,TeradataTableDatasetTypeProperties #6346
Changes from 7 commits
f756788
3015288
2727b7c
047db66
1a04dc6
7e6a62e
d2b6a0a
0fb95a0
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1182,6 +1182,36 @@ | |
} | ||
} | ||
}, | ||
"TeradataTableDatasetTypeProperties": { | ||
"description": "Teradata dataset properties.", | ||
"properties": { | ||
"database": { | ||
"type": "object", | ||
"description": "The database name of Teradata. Type: string (or Expression with resultType string)." | ||
}, | ||
"table": { | ||
"type": "object", | ||
"description": "The table name of Teradata. Type: string (or Expression with resultType string)." | ||
} | ||
} | ||
}, | ||
"TeradataTableDataset": { | ||
"x-ms-discriminator-value": "TeradataTable", | ||
"description": "The Teradata database dataset.", | ||
"type": "object", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
I see that you're modeling a lot of properties as object without referencing a definition. In the c# generated SDK, the property type will be There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Discussed on a call. C# SDK has a class that users can new up and pass in for the property value. Also backend supports multiple types. In reply to: 295494222 [](ancestors = 295494222) |
||
"allOf": [ | ||
{ | ||
"$ref": "#/definitions/Dataset" | ||
} | ||
], | ||
"properties": { | ||
"typeProperties": { | ||
"description": "Teradata dataset properties.", | ||
"x-ms-client-flatten": true, | ||
"$ref": "#/definitions/TeradataTableDatasetTypeProperties" | ||
} | ||
} | ||
}, | ||
"AzureMySqlTableDataset": { | ||
"x-ms-discriminator-value": "AzureMySqlTable", | ||
"description": "The Azure MySQL database dataset.", | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am really confused about these changes. The new definitions aren't really referenced in any paths, so this will result in no change to the API contract. Autorest might generate types for all the new definitions, but the clients won't get any new methods to utilize them.
What is the intent here? If you are planning to add paths later, will you be introducing a new API version? #Closed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I missed that we're using discriminator value.
In reply to: 295493306 [](ancestors = 295493306)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The users know that they're expected to update to latest SDK to use newest types of data sets.
In reply to: 295580149 [](ancestors = 295580149,295493306)