# "\[ignore\_throttled\] parameter is deprecated because frozen indices have been deprecated **URL:** \ **Category:** Elasticsearch\ **Created:** [March 8, 2022, 9:20pm UTC](https://discuss.elastic.co/t/ignore-throttled-parameter-is-deprecated-because-frozen-indices-have-been-deprecated/299144 "2022-03-08T21:20:33Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![joschi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joschi/32/44946_2.png) [@joschi](https://discuss.elastic.co/u/joschi)\ **Post date:** [March 10, 2022, 7:53am UTC](https://discuss.elastic.co/t/ignore-throttled-parameter-is-deprecated-because-frozen-indices-have-been-deprecated/299144/5 "2022-03-10T07:53:55Z")
> [@warkolm](#): > > Uhh, not sure how you got that sorry? Unfortunately that's exactly what's happening when using ES 7.16.0 or higher and the Java High Level REST Client (even in the same version). > [@Default IndicesOptions in SearchRequest and disable specific deprecation warnings](https://discuss.elastic.co/t/default-indicesoptions-in-searchrequest-and-disable-specific-deprecation-warnings/299242/3): > > @DavidTurner Yes, we're using the Java High Level REST Client in version 7.16.3. I would not have expected that it's causing the deprecation warning without any possibility whatsoever to disable it, either by not sending the deprecated parameter or by disabling the warning message. So out of the box you cannot use Elasticsearch 7.16.x or later with the Java High Level REST Client without producing the deprecation warning, which makes up ~95% of log messages in our ES clusters. exploding_head … Sorry for hijacking this thread, I'll stop posting in this topic now. --- _[View the full topic](https://discuss.elastic.co/t/ignore-throttled-parameter-is-deprecated-because-frozen-indices-have-been-deprecated/299144)._