Skip to content

Commit 54d0d77

Browse files
Merge pull request #184104 from johndeu/master
updated question on streaming locators in v2
2 parents 517d06e + ea26ea0 commit 54d0d77

File tree

4 files changed

+54
-34
lines changed

4 files changed

+54
-34
lines changed

articles/media-services/latest/TOC.yml

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -52,9 +52,9 @@
5252
href: setup-postman-rest-how-to.md
5353
- name: Try an SDK sample
5454
items:
55-
- name: GitHub code samples
55+
- name: GitHub samples by language
5656
href: samples-overview.md
57-
displayName: samples, SDK, Tutorial
57+
displayName: samples, SDK, tutorial, GitHub, .NET, Python, Nodejs, Node, Node.JS Java, Typescript, TS, Javascript, JS
5858
- name: Try Media Services in the portal
5959
items:
6060
- name: Live event with portal and Wirecast
@@ -145,12 +145,9 @@
145145
displayName: events, event grid, log analytics, tutorial, portal, monitoring, monitor
146146
- name: Samples
147147
items:
148-
- name: GitHub code samples
148+
- name: GitHub samples by language
149149
href: samples-overview.md
150-
displayName: samples, SDK, tutorial, GitHub
151-
- name: Media Services v3 GitHub samples
152-
displayName: .NET, Python, Nodejs, Java, samples, tutorials, SDK, GitHub
153-
href: https://github.com/Azure-Samples?q=media-services&type=&language=&sort=
150+
displayName: samples, SDK, tutorial, GitHub, .NET, C#, Python, Nodejs, Node, Node.JS Java, Typescript, TS, Javascript, JS
154151
- name: Media Services v3 GitHub REST samples
155152
href: https://github.com/Azure-Samples/media-services-v3-rest-postman
156153
- name: Concepts

articles/media-services/latest/frequently-asked-questions.yml

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -158,6 +158,13 @@ sections:
158158
159159
When you're scaling up with this approach, you should monitor the streaming endpoint's CPU load. If you're planning to go to production with a large library of MP4 files that are pre-encoded outside Media Services, file a support ticket to have your architecture reviewed and
160160
ask about ways to improve the origin server performance of pre-encoded MP4 content.
161+
- question: Will v2 streaming locators continue to work after February 2024?
162+
answer: |
163+
Streaming locators created with v2 API will continue to work after our v2 API is turned off. Once the Streaming Locator data is created in the Media Services backend database, there is no dependency on the v2 REST API for streaming. We will not remove v2 specific records from the database when v2 is turned off in February 2024.
164+
165+
There are some properties of assets and locators created with v2 that cannot be accessed or updated using the new v3 API. For example, v2 exposes an **Asset Files** API that does not have an equivalent feature in the v3 API. Often this is not a problem for most of our customers, since it is not a widely used feature and you can still stream old locators and delete them when they are no longer needed.
166+
167+
After migration, you should avoid making any calls to the v2 API to modify streaming locators or assets.
161168
162169
- name: Content protection
163170
questions:

articles/media-services/latest/migrate-v-2-v-3-migration-scenario-based-publishing.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,14 @@ Major changes to the way content is published in v3 API. The new publishing mode
3232

3333
See publishing concepts, tutorials and how to guides below for specific steps.
3434

35+
## Will v2 streaming locators continue to work after February 2024?
36+
37+
Streaming locators created with v2 API will continue to work after our v2 API is turned off. Once the Streaming Locator data is created in the Media Services backend database, there is no dependency on the v2 REST API for streaming. We will not remove v2 specific records from the database when v2 is turned off in February 2024.
38+
39+
There are some properties of assets and locators created with v2 that cannot be accessed or updated using the new v3 API. For example, v2 exposes an **Asset Files** API that does not have an equivalent feature in the v3 API. Often this is not a problem for most of our customers, since it is not a widely used feature and you can still stream old locators and delete them when they are no longer needed.
40+
41+
After migration, you should avoid making any calls to the v2 API to modify streaming locators or assets.
42+
3543
## Publishing concepts, tutorials and how to guides
3644

3745
### Concepts

0 commit comments

Comments
 (0)