# Search request's timeout doesn't work as expected

**URL:** <https://discuss.elastic.co/t/search-requests-timeout-doesnt-work-as-expected/328247>\
**Category:** Elasticsearch\
**Created:** [March 22, 2023, 12:45pm UTC](https://discuss.elastic.co/t/search-requests-timeout-doesnt-work-as-expected/328247 "2023-03-22T12:45:11Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Mark\_Harwood1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mark_harwood1/32/101255_2.png) [@Mark\_Harwood1](https://discuss.elastic.co/u/Mark_Harwood1)\
**Post date:** [March 24, 2023, 8:40am UTC](https://discuss.elastic.co/t/search-requests-timeout-doesnt-work-as-expected/328247/12 "2023-03-24T08:40:03Z")

</div>

Lucene has an option to store term vectors (the raw output of analysis) but that costs extra in disk storage and reading this expanded data from disk [is not substantially faster than re-analysis of the original text in many cases](https://discuss.elastic.co/t/fast-vector-highlighter-fvh-making-searches-slower/290634/4)

I’d recommend closing this GitHub issue as it is more of a question than a bug or proposed fix.

---

_[View the full topic](https://discuss.elastic.co/t/search-requests-timeout-doesnt-work-as-expected/328247)._