[Datafactory] Add Tumbling Window dependsOn property to Trigger.json for Tumbling Window Trigger and self-dependent Tumbling Window Trigger#3356
[Datafactory] Add Tumbling Window dependsOn property to Trigger.json for Tumbling Window Trigger and self-dependent Tumbling Window Trigger#3356alexsaff wants to merge 11 commits intoAzure:masterfrom alexsaff:master
Conversation
Automation for azure-sdk-for-pythonNothing to generate for azure-sdk-for-python |
Automation for azure-sdk-for-nodeNothing to generate for azure-sdk-for-node |
Automation for azure-sdk-for-rubyNothing to generate for azure-sdk-for-ruby |
Automation for azure-sdk-for-javaA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
|
@alexsaff please ping me directly when this PR will be ready for review and merge. |
Automation for azure-sdk-for-goA PR has been created for you: |
| "description": "Referenced trigger", | ||
| "$ref": "#/definitions/TriggerReference" | ||
| }, | ||
| "offset": { |
There was a problem hiding this comment.
offset and size can be moved to a separate type and reused in both self dependency and tumbling widow dependency reference classes. Please refer to the mail thread and the doc Nailini created. #Resolved
There was a problem hiding this comment.
Also it will be better to create another class derived from DependencyReference as Nalini had in her doc and put referenceTrigger in that class, because in future if you support ScheduledTriggerReference, it will be derived from this new class along with TumblingWindowTriggerDependencyReference. Only in case of self rereference you don't need to have referenceTrigger property, in all other cases you will need it. If we don't do these changes now, later they will breaking changes. #Resolved
There was a problem hiding this comment.
Offset is required for self-dependency, so it makes not much sense to create a separate type for offset and size. #Resolved
There was a problem hiding this comment.
TriggerDependencyReference has been added #Resolved
| }, | ||
| "dependsOn": { | ||
| "type": "array", | ||
| "description": "Tumbling window triggers that this trigger depends on. Only tumbling window triggers are supported.", |
There was a problem hiding this comment.
Tumbling window [](start = 30, length = 16)
Remove this tumbling window part from here:
Triggers that this trigger depends on. Only tumbling window triggers are supported. #Resolved
| ] | ||
| }, | ||
| "DependencyReference": { | ||
| "description": "Referenced dependency", |
There was a problem hiding this comment.
Need dot at the end, otherwise validation will fail. #Resolved
| "discriminator": "type", | ||
| "properties": { | ||
| "type": { | ||
| "description": "The type of dependency reference", |
| ] | ||
| }, | ||
| "TriggerDependencyReference": { | ||
| "description": "Trigger referenced dependency", |
| ], | ||
| "properties": { | ||
| "referenceTrigger": { | ||
| "description": "Referenced trigger", |
| ] | ||
| }, | ||
| "TumblingWindowTriggerDependencyReference": { | ||
| "description": "Referenced tumbling window trigger dependency", |
| ], | ||
| "properties": { | ||
| "offset": { | ||
| "description": "Timespan applied to the start time of a tumbling window when evaluating dependency, pattern: ((\\d+)\\.)?(\\d\\d):(60|([0-5][0-9])):(60|([0-5][0-9])).", |
There was a problem hiding this comment.
((\d+)\.)?(\d\d):(60|([0-5][0-9])):(60|([0-5][0-9])) [](start = 119, length = 56)
I think you can add this as validation, then SDK will have a code for that. Check the parameters section in https://github.com/Azure/azure-rest-api-specs/blob/master/specification/datafactory/resource-manager/Microsoft.DataFactory/stable/2018-06-01/datafactory.json
| } | ||
| }, | ||
| "SelfDependencyTumblingWindowTriggerReference": { | ||
| "description": "Self referenced tumbling window trigger dependency", |
|
@AutorestCI regenerate azure-sdk-for-go |
|
Replace by #3414 |
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information
api-versionin the path should match theapi-versionin the spec).Quality of Swagger