# Deprecation info missing in the docs?

**URL:** <https://discuss.elastic.co/t/deprecation-info-missing-in-the-docs/345744>\
**Category:** Elasticsearch\
**Created:** [October 25, 2023, 2:45pm UTC](https://discuss.elastic.co/t/deprecation-info-missing-in-the-docs/345744 "2023-10-25T14:45:01Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bunste](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bunste/32/95865_2.png) [@bunste](https://discuss.elastic.co/u/bunste)\
**Post date:** [October 25, 2023, 2:45pm UTC](https://discuss.elastic.co/t/deprecation-info-missing-in-the-docs/345744/1 "2023-10-25T14:45:01Z")

</div>

I saw the following deprecation warning today:

```
[ignore_throttled] parameter is deprecated because frozen indices have been deprecated. Consider cold or frozen tiers in place of frozen indices.

```

So far so good, finding and fixing the responsible piece of code shouldn't be that hard. What surprises me though: According to the [pull request #77479](https://github.com/elastic/elasticsearch/pull/77479) this change was introduced in version 7.16 - the [release notes](https://www.elastic.co/guide/en/elasticsearch/reference/7.16/release-notes-7.16.0.html) of 7.16 confirm this as well.

And yet, to this day, there is nothing in the current [Search API documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-search.html) about the `ignore_throttled` parameter being deprecated. Was this simply forgotten? Or am I confusing something?

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [October 25, 2023, 6:47pm UTC](https://discuss.elastic.co/t/deprecation-info-missing-in-the-docs/345744/2 "2023-10-25T18:47:35Z")

</div>

> [@bunste](#):
>
> And yet, to this day, there is nothing in the current [Search API documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-search.html) about the `ignore_throttled` parameter being deprecated. Was this simply forgotten? Or am I confusing something?

I think you're right, this should be mentioned in the docs and it isn't. Would you open a docs bug report on [Github](https://github.com/elastic/elasticsearch/issues) about this please?

---

<div class="post-metadata">

**Author:** ![bunste](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bunste/32/95865_2.png) [@bunste](https://discuss.elastic.co/u/bunste)\
**Post date:** [October 25, 2023, 8:59pm UTC](https://discuss.elastic.co/t/deprecation-info-missing-in-the-docs/345744/3 "2023-10-25T20:59:16Z")

</div>

All right, issue has just been created ✅

> <https://github.com/elastic/elasticsearch/issues/101348>
>
> As I have already described \[here\](https://discuss.elastic.co/t/deprecation-info…-missing-in-the-docs/345744/1) in the forum, I recently encountered the following deprecation warning:
> 
> \[ignore\_throttled\] parameter is deprecated because frozen indices have been deprecated. Consider cold or frozen tiers in place of frozen indices.
> 
> According to the \[release notes\](https://www.elastic.co/guide/en/elasticsearch/reference/7.16/release-notes-7.16.0.html) this change was introduced in version 7.16.
> 
> However, a corresponding deprecation info is still missing in some places in the 8.10 (which is \_current\_ at the time of this writing) documentation, for example for the \[Search API\](https://www.elastic.co/guide/en/elasticsearch/reference/8.10/search-search.html).
> 
> The search function finds all relevant documentation pages relatively quickly.

---

<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:** [November 22, 2023, 8:59pm UTC](https://discuss.elastic.co/t/deprecation-info-missing-in-the-docs/345744/4 "2023-11-22T20:59:54Z")

</div>

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