Skip to content
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

[Data Factory]Add ORC Dataset/Copy Source/Copy Sink #7040

Merged
merged 4 commits into from
Sep 3, 2019

Conversation

TinaHu1
Copy link
Contributor

@TinaHu1 TinaHu1 commented Aug 26, 2019

Latest improvements:

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Contribution checklist:

  • I have reviewed the documentation for the workflow.
  • Validation tools were run on swagger spec(s) and have all been fixed in this PR.
  • The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

  • Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
  • adding/removing APIs.
  • adding/removing properties.
  • adding/removing API-version.
  • adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

  • If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
    Please follow the link to find more details on API review process.

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Aug 26, 2019

In Testing, Please Ignore

[Logs] (Generated from 864a2b3, Iteration 3)

Failed .NET: test-repo-billy/azure-sdk-for-net [Logs] [Diff]
Succeeded Python: test-repo-billy/azure-sdk-for-python [Logs] [Diff]
Failed Java: test-repo-billy/azure-sdk-for-java [Logs] [Diff]
  • Failed datafactory/resource-manager/v2017_09_01_preview [Logs] [Generation PR]
  • Failed datafactory/resource-manager/v2018_06_01 [Logs]
Failed Go: test-repo-billy/azure-sdk-for-go [Logs] [Diff]
Failed JavaScript: test-repo-billy/azure-sdk-for-js [Logs] [Diff]
  • No packages generated.

@AutorestCI
Copy link

AutorestCI commented Aug 26, 2019

Automation for azure-sdk-for-python

A 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:
Azure/azure-sdk-for-python#7023

@AutorestCI
Copy link

AutorestCI commented Aug 26, 2019

Automation for azure-sdk-for-go

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-go#5679

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@@ -776,6 +776,21 @@
}
}
},
"OrcSource": {
"description": "A copy activity ORC source.",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One more thing is that where OrcSource and OrcSink are used in your swagger file.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is the similiar usage.
Take Source as an example:
In specification/datafactory/resource-manager/Microsoft.DataFactory/stable/2018-06-01/entityTypes/Pipeline.json
"OrcSource" is to add a new type for "CopySource" with the defination "discriminator" in copy source(line 914). Then "CopySource" is referenced by "CopyActivityTypeProperties"(line 885)=>"CopyActivity"(line 859)=>extend a type for "Activity"(line 21)=>"Pipeline"(line 9)

In specification/datafactory/resource-manager/Microsoft.DataFactory/stable/2018-06-01/datafactory.json
"Pipeline" was reference by "PipelineResource"(line 4106)=>used in several API.

Sink is almost the same as Source.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do you use x-ms-discriminator-value in "OrcDataset" not in "OrcSource"?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because the real value we want for customer to use is "Orc" but not "OrcDataset".
@Juliehzl It will be very helpful if we can merge this PR before tomorrow, thanks.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@TinaHu1 Thanks for your detailed explanation. Just ensure everything is in the right way. 😊

@ravbhatnagar
Copy link
Contributor

yes, @anthony-c-martin we have discussed this in the past. And although this is a breaking change, ADF scenario is bit more nuanced. So, we have let this through in the past with the expectation that we will bring this up with MarkRus and other folks and seek guidance for such scenarios.
So for now, this should be ok to sign off.

@anthony-c-martin anthony-c-martin added ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Aug 29, 2019
@anthony-c-martin anthony-c-martin self-requested a review August 29, 2019 17:02
Copy link
Member

@anthony-c-martin anthony-c-martin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As per Gaurav's comment, signing off even though this is a breaking change.

@TinaHu1
Copy link
Contributor Author

TinaHu1 commented Aug 30, 2019

@Juliehzl Could you help merge this PR? Thanks

@Juliehzl
Copy link
Contributor

@TinaHu1 I am waiting for your answer. With your clear explanation, I can understand "OrcDataset" now. I wonder why OrcSource and OrcSink are not used but you defined.

@Juliehzl Juliehzl merged commit 935dfad into Azure:master Sep 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants