# Rollover API for Transport Client

**URL:** <https://discuss.elastic.co/t/rollover-api-for-transport-client/180863>\
**Category:** Elasticsearch\
**Created:** [May 13, 2019, 6:38pm UTC](https://discuss.elastic.co/t/rollover-api-for-transport-client/180863 "2019-05-13T18:38:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chris\_Stack\_BB](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chris_stack_bb/32/46098_2.png) [@Chris\_Stack\_BB](https://discuss.elastic.co/u/Chris_Stack_BB)\
**Post date:** [May 13, 2019, 6:38pm UTC](https://discuss.elastic.co/t/rollover-api-for-transport-client/180863/1 "2019-05-13T18:38:41Z")

</div>

I'm working on upgrading to version 7, but due to time constraints am limited to continued use of the Transport Client. I did not see it announced as a breaking change, but the method I was using for conducting a rollover from the TransportClient seems unsupported now. I used to get a new RolloverRequestBuilder from RolloverAction.INSTANCE and then would set the alias and newIndexName, and then could perform a get call.

Is there anyway to perform a rollover from the TransportClient now?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 10, 2019, 6:38pm UTC](https://discuss.elastic.co/t/rollover-api-for-transport-client/180863/2 "2019-06-10T18:38:43Z")

</div>

Closed on June 10, 2019, 6:38pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
