# \[7.0.0\] Kibana controls visualization not returning all the possible choices (terminated\_early)

**URL:** <https://discuss.elastic.co/t/7-0-0-kibana-controls-visualization-not-returning-all-the-possible-choices-terminated-early/209630>\
**Category:** Kibana\
**Created:** [November 27, 2019, 8:19am UTC](https://discuss.elastic.co/t/7-0-0-kibana-controls-visualization-not-returning-all-the-possible-choices-terminated-early/209630 "2019-11-27T08:19:23Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Fabio-sama](https://avatars.discourse-cdn.com/v4/letter/f/b9e5f3/32.png) [@Fabio-sama](https://discuss.elastic.co/u/Fabio-sama)\
**Post date:** [November 27, 2019, 8:19am UTC](https://discuss.elastic.co/t/7-0-0-kibana-controls-visualization-not-returning-all-the-possible-choices-terminated-early/209630/1 "2019-11-27T08:19:23Z")

</div>

Hi there!

I'm facing a problem with Controls visualization in Kibana 7.0.0.

It basically returns only a limited set of the possible choices of a given field.  
I generally fix this problem in version \> 7.3.0 increasing the values of `kibana.autocompleteTimeout` and `kibana.autocompleteTerminateAfter` in the kibana.yml, but these parameters are not recognized by Kibana in versions \< 7.3.

Is there any equivalent settings in Kibana 7.0.0 or any other way I can make Controls visualizations returning all the possible choices?

Thank you!

---

<div class="post-metadata">

**Author:** ![markov00](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/markov00/32/33316_2.png) [@markov00](https://discuss.elastic.co/u/markov00)\
**Post date:** [November 27, 2019, 11:25am UTC](https://discuss.elastic.co/t/7-0-0-kibana-controls-visualization-not-returning-all-the-possible-choices-terminated-early/209630/2 "2019-11-27T11:25:02Z")

</div>

Unfortunately this parameters are only available starting from 7.3.

> <https://github.com/elastic/kibana/pull/37643>

All previous versions have hardcoded terminateAfter and timeout as:

```auto
timeout: '1s'
terminate_after: 100000

```

---

<div class="post-metadata">

**Author:** ![Fabio-sama](https://avatars.discourse-cdn.com/v4/letter/f/b9e5f3/32.png) [@Fabio-sama](https://discuss.elastic.co/u/Fabio-sama)\
**Post date:** [November 27, 2019, 11:47am UTC](https://discuss.elastic.co/t/7-0-0-kibana-controls-visualization-not-returning-all-the-possible-choices-terminated-early/209630/3 "2019-11-27T11:47:08Z")

</div>

Hi and thank you for the reply.

I imagined something like that, but can you tell me where they are hardcoded and whether I can change those values or not?

Thank you!

---

<div class="post-metadata">

**Author:** ![markov00](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/markov00/32/33316_2.png) [@markov00](https://discuss.elastic.co/u/markov00)\
**Post date:** [November 27, 2019, 11:59am UTC](https://discuss.elastic.co/t/7-0-0-kibana-controls-visualization-not-returning-all-the-possible-choices-terminated-early/209630/4 "2019-11-27T11:59:20Z")

</div>

You can find these values [here](https://github.com/elastic/kibana/pull/37643/files#diff-5f9178f79101170e3920ebbac93835f4L101-L102):

The file name is `src/legacy/core_plugins/input_control_vis/public/control/list_control_factory.js` you should find those values around row 101.

We doesn't encourage code changes into a released version (only in a development environment). If it's critical to your analysis but Kibana is not in a Production environment with a mission critical use case, you may try to change these parameter and see how things works. Please make a snapshot of your cluster and configurations before attempt any change.

---

<div class="post-metadata">

**Author:** ![Fabio-sama](https://avatars.discourse-cdn.com/v4/letter/f/b9e5f3/32.png) [@Fabio-sama](https://discuss.elastic.co/u/Fabio-sama)\
**Post date:** [November 27, 2019, 12:03pm UTC](https://discuss.elastic.co/t/7-0-0-kibana-controls-visualization-not-returning-all-the-possible-choices-terminated-early/209630/5 "2019-11-27T12:03:43Z")

</div>

Yeah I realized I could look for it inside the project before asking and then found it where you said.

Thank you anyway for your kindness.

Yeah, I supposed it might create some problems. Don't think it is so critical to justify taking such a risk. Especially since upgrade to 7.4 has been already scheduled.

Thank you so much for your help!

---

<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:** [December 25, 2019, 12:03pm UTC](https://discuss.elastic.co/t/7-0-0-kibana-controls-visualization-not-returning-all-the-possible-choices-terminated-early/209630/6 "2019-12-25T12:03:58Z")

</div>

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