Azure Media Services V3 - How to get ParentAssets (available in IAsset from V2)
up vote
0
down vote
favorite
How to get ParentAssets in Azure Media Services V3?
ParentAssets are available in legacy V2 APIs both .NET & REST apis.
Reference
https://urstream.restv2.westus.media.azure.net/api/Assets('asset id')/ParentAssets".
IAsset.ParentAssets https://docs.microsoft.com/en-us/dotnet/api/microsoft.windowsazure.mediaservices.client.iasset?view=azure-dotnet
azure-media-services
add a comment |
up vote
0
down vote
favorite
How to get ParentAssets in Azure Media Services V3?
ParentAssets are available in legacy V2 APIs both .NET & REST apis.
Reference
https://urstream.restv2.westus.media.azure.net/api/Assets('asset id')/ParentAssets".
IAsset.ParentAssets https://docs.microsoft.com/en-us/dotnet/api/microsoft.windowsazure.mediaservices.client.iasset?view=azure-dotnet
azure-media-services
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
How to get ParentAssets in Azure Media Services V3?
ParentAssets are available in legacy V2 APIs both .NET & REST apis.
Reference
https://urstream.restv2.westus.media.azure.net/api/Assets('asset id')/ParentAssets".
IAsset.ParentAssets https://docs.microsoft.com/en-us/dotnet/api/microsoft.windowsazure.mediaservices.client.iasset?view=azure-dotnet
azure-media-services
How to get ParentAssets in Azure Media Services V3?
ParentAssets are available in legacy V2 APIs both .NET & REST apis.
Reference
https://urstream.restv2.westus.media.azure.net/api/Assets('asset id')/ParentAssets".
IAsset.ParentAssets https://docs.microsoft.com/en-us/dotnet/api/microsoft.windowsazure.mediaservices.client.iasset?view=azure-dotnet
azure-media-services
azure-media-services
asked Nov 12 at 3:07
Carlos Online
13
13
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Unfortunately, it is not supported in the Azure media service v3 currently,
we could find all of the supported Rest APIs from the rest-api-specs. But now there is no ParentAssets related information in the rest-api-specs.
For more information about Azure Media Services v3 release notes, please refer to this document.
Currently, not all of v2 features are migrated to v3, if you still want to get ParentAssets, I recommend that you could still use the v2 to instead of v3 currently.
Thanks, is the rest-api-specs link a swagger file? How do I read it in a human form viewer? Can I use the V2 Rest API to get V3 Parents?
– Carlos Online
Nov 12 at 16:43
How are you actually using Parents in the V2 API today? Can you explain the scenario? We actually have not moved that over to V3 as we saw little to no usage of the feature - and it made the API a bit too much like a CMS layer.
– johndeu
Nov 12 at 18:19
2 uses. 1. map caption asset, produced via indexer job, to original source asset. 2. Map mp4 asset, produced by encoder job, to original live asset. I have worked around out by storing parent in the alternativeid. Can the size limit for alternativeid be increased to 4K? I am using it for easy metadata.
– Carlos Online
Nov 12 at 23:06
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Unfortunately, it is not supported in the Azure media service v3 currently,
we could find all of the supported Rest APIs from the rest-api-specs. But now there is no ParentAssets related information in the rest-api-specs.
For more information about Azure Media Services v3 release notes, please refer to this document.
Currently, not all of v2 features are migrated to v3, if you still want to get ParentAssets, I recommend that you could still use the v2 to instead of v3 currently.
Thanks, is the rest-api-specs link a swagger file? How do I read it in a human form viewer? Can I use the V2 Rest API to get V3 Parents?
– Carlos Online
Nov 12 at 16:43
How are you actually using Parents in the V2 API today? Can you explain the scenario? We actually have not moved that over to V3 as we saw little to no usage of the feature - and it made the API a bit too much like a CMS layer.
– johndeu
Nov 12 at 18:19
2 uses. 1. map caption asset, produced via indexer job, to original source asset. 2. Map mp4 asset, produced by encoder job, to original live asset. I have worked around out by storing parent in the alternativeid. Can the size limit for alternativeid be increased to 4K? I am using it for easy metadata.
– Carlos Online
Nov 12 at 23:06
add a comment |
up vote
0
down vote
Unfortunately, it is not supported in the Azure media service v3 currently,
we could find all of the supported Rest APIs from the rest-api-specs. But now there is no ParentAssets related information in the rest-api-specs.
For more information about Azure Media Services v3 release notes, please refer to this document.
Currently, not all of v2 features are migrated to v3, if you still want to get ParentAssets, I recommend that you could still use the v2 to instead of v3 currently.
Thanks, is the rest-api-specs link a swagger file? How do I read it in a human form viewer? Can I use the V2 Rest API to get V3 Parents?
– Carlos Online
Nov 12 at 16:43
How are you actually using Parents in the V2 API today? Can you explain the scenario? We actually have not moved that over to V3 as we saw little to no usage of the feature - and it made the API a bit too much like a CMS layer.
– johndeu
Nov 12 at 18:19
2 uses. 1. map caption asset, produced via indexer job, to original source asset. 2. Map mp4 asset, produced by encoder job, to original live asset. I have worked around out by storing parent in the alternativeid. Can the size limit for alternativeid be increased to 4K? I am using it for easy metadata.
– Carlos Online
Nov 12 at 23:06
add a comment |
up vote
0
down vote
up vote
0
down vote
Unfortunately, it is not supported in the Azure media service v3 currently,
we could find all of the supported Rest APIs from the rest-api-specs. But now there is no ParentAssets related information in the rest-api-specs.
For more information about Azure Media Services v3 release notes, please refer to this document.
Currently, not all of v2 features are migrated to v3, if you still want to get ParentAssets, I recommend that you could still use the v2 to instead of v3 currently.
Unfortunately, it is not supported in the Azure media service v3 currently,
we could find all of the supported Rest APIs from the rest-api-specs. But now there is no ParentAssets related information in the rest-api-specs.
For more information about Azure Media Services v3 release notes, please refer to this document.
Currently, not all of v2 features are migrated to v3, if you still want to get ParentAssets, I recommend that you could still use the v2 to instead of v3 currently.
edited Nov 12 at 8:29
answered Nov 12 at 8:23
Tom Sun
16k2921
16k2921
Thanks, is the rest-api-specs link a swagger file? How do I read it in a human form viewer? Can I use the V2 Rest API to get V3 Parents?
– Carlos Online
Nov 12 at 16:43
How are you actually using Parents in the V2 API today? Can you explain the scenario? We actually have not moved that over to V3 as we saw little to no usage of the feature - and it made the API a bit too much like a CMS layer.
– johndeu
Nov 12 at 18:19
2 uses. 1. map caption asset, produced via indexer job, to original source asset. 2. Map mp4 asset, produced by encoder job, to original live asset. I have worked around out by storing parent in the alternativeid. Can the size limit for alternativeid be increased to 4K? I am using it for easy metadata.
– Carlos Online
Nov 12 at 23:06
add a comment |
Thanks, is the rest-api-specs link a swagger file? How do I read it in a human form viewer? Can I use the V2 Rest API to get V3 Parents?
– Carlos Online
Nov 12 at 16:43
How are you actually using Parents in the V2 API today? Can you explain the scenario? We actually have not moved that over to V3 as we saw little to no usage of the feature - and it made the API a bit too much like a CMS layer.
– johndeu
Nov 12 at 18:19
2 uses. 1. map caption asset, produced via indexer job, to original source asset. 2. Map mp4 asset, produced by encoder job, to original live asset. I have worked around out by storing parent in the alternativeid. Can the size limit for alternativeid be increased to 4K? I am using it for easy metadata.
– Carlos Online
Nov 12 at 23:06
Thanks, is the rest-api-specs link a swagger file? How do I read it in a human form viewer? Can I use the V2 Rest API to get V3 Parents?
– Carlos Online
Nov 12 at 16:43
Thanks, is the rest-api-specs link a swagger file? How do I read it in a human form viewer? Can I use the V2 Rest API to get V3 Parents?
– Carlos Online
Nov 12 at 16:43
How are you actually using Parents in the V2 API today? Can you explain the scenario? We actually have not moved that over to V3 as we saw little to no usage of the feature - and it made the API a bit too much like a CMS layer.
– johndeu
Nov 12 at 18:19
How are you actually using Parents in the V2 API today? Can you explain the scenario? We actually have not moved that over to V3 as we saw little to no usage of the feature - and it made the API a bit too much like a CMS layer.
– johndeu
Nov 12 at 18:19
2 uses. 1. map caption asset, produced via indexer job, to original source asset. 2. Map mp4 asset, produced by encoder job, to original live asset. I have worked around out by storing parent in the alternativeid. Can the size limit for alternativeid be increased to 4K? I am using it for easy metadata.
– Carlos Online
Nov 12 at 23:06
2 uses. 1. map caption asset, produced via indexer job, to original source asset. 2. Map mp4 asset, produced by encoder job, to original live asset. I have worked around out by storing parent in the alternativeid. Can the size limit for alternativeid be increased to 4K? I am using it for easy metadata.
– Carlos Online
Nov 12 at 23:06
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53255481%2fazure-media-services-v3-how-to-get-parentassets-available-in-iasset-from-v2%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown