# MultisearchBody and seq\_no\_primary\_term

**URL:** <https://discuss.elastic.co/t/multisearchbody-and-seq-no-primary-term/297595>\
**Category:** Elasticsearch\
**Created:** [February 18, 2022, 10:44am UTC](https://discuss.elastic.co/t/multisearchbody-and-seq-no-primary-term/297595 "2022-02-18T10:44:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pingouin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pingouin/32/70394_2.png) [@Pingouin](https://discuss.elastic.co/u/Pingouin)\
**Post date:** [February 18, 2022, 10:44am UTC](https://discuss.elastic.co/t/multisearchbody-and-seq-no-primary-term/297595/1 "2022-02-18T10:44:40Z")

</div>

I am currently updating my code from High Level Rest java client to new Java client.  
It seems that it is no longer possible to activate "seq\_no\_primary\_term" for multi search request.  
With High Level REST Api, it only needs to call seqNoAndPrimaryTerm(true) on all inner SearchSourceBuilder.  
I don't see any equivalent into MultisearchBody (which it's used by RequestItem.Builder), did i miss something or is it normal behaviour ?

---

<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:** [March 18, 2022, 10:45am UTC](https://discuss.elastic.co/t/multisearchbody-and-seq-no-primary-term/297595/2 "2022-03-18T10:45:05Z")

</div>

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