Last updated Nov 19, 2021

Deprecation notice for page size of APIs to get the mappings by pages

From 19 May 2022,

  • the app migration platform will reduce the maximum and default page size from 5000 to 1200 for GET /migration/mapping/{transferId}/page API to get the mappings in pages from cloud app.
  • the app migration platform will reduce the maximum page size to 1200 for getPaginatedMapping method to get the mappings in pages from server app.

Existing behaviour

Currently, the app migration platform supports following ways to get the mappings in pages.

  • Rest API GET /migration/mapping/{transferId}/page for cloud apps with the maximum and default page size of 5000.
  • Method getPaginatedMapping for server apps supporting page size greater than 1200.

Replacement

Before 19 May 2022, you will need to do the following:

  • If your cloud app currently uses the GET /migration/mapping/{transferId}/page API to get the mappings in pages with page size greater than 1200, then you must make the required changes to use the maximum page size of 1200 instead. If this change in default page size have an impact on your cloud app, then you must make the required changes to use the default page size of 1200 instead.

  • If your server app currently uses the getPaginatedMapping method to get mappings in pages with page size greater than 1200, then you must make the required changes to use the maximum page size of 1200 instead.

You can find related information about this deprecation announcement in the Changelog.

Reason for change

We are making this change to address the scalability and latency requirements of the app migration platform.

Rate this page: