# Unable to display large text fields in Kibana Markdown visualization

**URL:** https://discuss.elastic.co/t/unable-to-display-large-text-fields-in-kibana-markdown-visualization/324981
**Category:** Kibana
**Tags:** visualisation
**Created:** [February 8, 2023, 7:42am UTC](https://discuss.elastic.co/t/unable-to-display-large-text-fields-in-kibana-markdown-visualization/324981 "2023-02-08T07:42:21Z")
**Posts on this page:** 12
**Page:** 1

<div class="post-metadata">

### Author: ![Alice\_Ionescu](https://avatars.discourse-cdn.com/v4/letter/a/ac91a4/32.png) [@Alice\_Ionescu](https://discuss.elastic.co/u/Alice_Ionescu)
#### Post date: [February 8, 2023, 7:42am UTC](https://discuss.elastic.co/t/unable-to-display-large-text-fields-in-kibana-markdown-visualization/324981/1 "2023-02-08T07:42:21Z")

</div>

Hello,  
I have one field store in ES that has a big length, around 35.000 - 40.000 characters.  
They are stored correctly in ES, I can see them in Discover page, but when I want to use them in a markdown visualization (Time Series) it is said that no data is depicted in, no records found.  
Is there a property to change?  
To consider large String fields?  
Thanks!

---

<div class="post-metadata">

### Author: ![Marco\_Liberati](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marco_liberati/32/82953_2.png) [@Marco\_Liberati](https://discuss.elastic.co/u/Marco_Liberati)
#### Post date: [February 21, 2023, 1:55pm UTC](https://discuss.elastic.co/t/unable-to-display-large-text-fields-in-kibana-markdown-visualization/324981/2 "2023-02-21T13:55:00Z")

</div>

Hi @Alice_Ionescu

is the field mapped as `keyword` as well?

---

<div class="post-metadata">

### Author: ![Alice\_Ionescu](https://avatars.discourse-cdn.com/v4/letter/a/ac91a4/32.png) [@Alice\_Ionescu](https://discuss.elastic.co/u/Alice_Ionescu)
#### Post date: [February 23, 2023, 1:40pm UTC](https://discuss.elastic.co/t/unable-to-display-large-text-fields-in-kibana-markdown-visualization/324981/3 "2023-02-23T13:40:44Z")

</div>

Yes, it is

---

<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 23, 2023, 1:41pm UTC](https://discuss.elastic.co/t/unable-to-display-large-text-fields-in-kibana-markdown-visualization/324981/4 "2023-03-23T13:41:22Z")

</div>

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

---

<div class="post-metadata">

### Author: ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)
#### Post date: [June 12, 2023, 3:29pm UTC](https://discuss.elastic.co/t/unable-to-display-large-text-fields-in-kibana-markdown-visualization/324981/5 "2023-06-12T15:29:47Z")

</div>



---

<div class="post-metadata">

### Author: ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)
#### Post date: [June 12, 2023, 3:31pm UTC](https://discuss.elastic.co/t/unable-to-display-large-text-fields-in-kibana-markdown-visualization/324981/6 "2023-06-12T15:31:22Z")

</div>

Thread is open now @Alice_Ionescu but it does not seem that it is getting much response.

Perhaps re-add a bit of detail...

Unfortunatly... Not all questions get answered we do our best.

---

<div class="post-metadata">

### Author: ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)
#### Post date: [June 13, 2023, 1:56pm UTC](https://discuss.elastic.co/t/unable-to-display-large-text-fields-in-kibana-markdown-visualization/324981/7 "2023-06-13T13:56:36Z")

</div>

Heya @Marco_Liberati any thoughts on this? We have a couple users asking the same question.

---

<div class="post-metadata">

### Author: ![Marco\_Liberati](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marco_liberati/32/82953_2.png) [@Marco\_Liberati](https://discuss.elastic.co/u/Marco_Liberati)
#### Post date: [June 14, 2023, 8:37am UTC](https://discuss.elastic.co/t/unable-to-display-large-text-fields-in-kibana-markdown-visualization/324981/8 "2023-06-14T08:37:40Z")

</div>

@Alice_Ionescu can you share the mapping of the field?

I am wondering if there's any `ignore_above` property configured on that field mapping which could prevent data from being stored.

---

<div class="post-metadata">

### Author: ![Alice\_Ionescu](https://avatars.discourse-cdn.com/v4/letter/a/ac91a4/32.png) [@Alice\_Ionescu](https://discuss.elastic.co/u/Alice_Ionescu)
#### Post date: [June 14, 2023, 9:02am UTC](https://discuss.elastic.co/t/unable-to-display-large-text-fields-in-kibana-markdown-visualization/324981/9 "2023-06-14T09:02:27Z")

</div>

Hello,

I did increase the ignore\_above limit to the field to the max supported by ES. But with no success. The field is still not displayed, even though his length is smaller than 32766  
Here is the mapping of my field.

> ```
> "jpegPhoto": {
> "type": "text",
> "fields": {
> "keyword": {
> "type": "keyword",
> "ignore_above": 32766
> }
> }
> },
> 
> ```

Thanks!

---

<div class="post-metadata">

### Author: ![Marco\_Liberati](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marco_liberati/32/82953_2.png) [@Marco\_Liberati](https://discuss.elastic.co/u/Marco_Liberati)
#### Post date: [June 14, 2023, 10:00am UTC](https://discuss.elastic.co/t/unable-to-display-large-text-fields-in-kibana-markdown-visualization/324981/10 "2023-06-14T10:00:09Z")

</div>

If the string is 35000-40000 chars long is bigger than the limit of 32766.

---

<div class="post-metadata">

### Author: ![Alice\_Ionescu](https://avatars.discourse-cdn.com/v4/letter/a/ac91a4/32.png) [@Alice\_Ionescu](https://discuss.elastic.co/u/Alice_Ionescu)
#### Post date: [June 14, 2023, 10:18am UTC](https://discuss.elastic.co/t/unable-to-display-large-text-fields-in-kibana-markdown-visualization/324981/11 "2023-06-14T10:18:17Z")

</div>

> [@Alice\_Ionescu](#):
>
> 32766

yes, indeed.  
But with what I've tested is smaller than "ignore\_above": 32766

---

<div class="post-metadata">

### Author: ![Marco\_Liberati](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marco_liberati/32/82953_2.png) [@Marco\_Liberati](https://discuss.elastic.co/u/Marco_Liberati)
#### Post date: [June 14, 2023, 10:22am UTC](https://discuss.elastic.co/t/unable-to-display-large-text-fields-in-kibana-markdown-visualization/324981/12 "2023-06-14T10:22:33Z")

</div>

Mind that discover will show `text` values, if the main mapping has that, not `keyword` if it's a subfield.

In Lens can you open the `Inspect` panel and check the response from ES?  
The visualization will retrieve values from there.

 ![Screenshot 2023-06-14 at 12.21.51](https://us1.discourse-cdn.com/elastic/original/3X/6/3/6340c051ff785c1b1a4bef71f62302d0b964598a.png)

 ![Screenshot 2023-06-14 at 12.22.03](https://us1.discourse-cdn.com/elastic/original/3X/9/3/9389f135dec199ae8bdcc018e4dc1b0bdf30cd13.png)
