# Continued support for annotated text plugin?

**URL:** <https://discuss.elastic.co/t/continued-support-for-annotated-text-plugin/218688>\
**Category:** Elasticsearch\
**Created:** [February 10, 2020, 11:15pm UTC](https://discuss.elastic.co/t/continued-support-for-annotated-text-plugin/218688 "2020-02-10T23:15:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![benarar](https://avatars.discourse-cdn.com/v4/letter/b/a9a28c/32.png) [@benarar](https://discuss.elastic.co/u/benarar)\
**Post date:** [February 10, 2020, 11:15pm UTC](https://discuss.elastic.co/t/continued-support-for-annotated-text-plugin/218688/1 "2020-02-10T23:15:44Z")

</div>

Hi,

I am hoping to use the Mapper Annotated Text Plugin ([Mapper Annotated Text Plugin | Elasticsearch Plugins and Integrations [7.5] | Elastic](https://www.elastic.co/guide/en/elasticsearch/plugins/7.5/mapper-annotated-text.html)) but noticed this warning:

> This functionality is experimental and may be changed or removed completely in a future release. Elastic will take a best effort approach to fix any issues, but experimental features are not subject to the support SLA of official GA features.

I am concerned that if I build a product using this that it may not be supported in a future version. Do you know if Elastic has plans to make this a permanent feature?

---

<div class="post-metadata">

**Author:** ![Mark\_Harwood](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mark_harwood/32/10538_2.png) [@Mark\_Harwood](https://discuss.elastic.co/u/Mark_Harwood)\
**Post date:** [March 6, 2020, 9:31am UTC](https://discuss.elastic.co/t/continued-support-for-annotated-text-plugin/218688/2 "2020-03-06T09:31:29Z")

</div>

Hi @benarar ,  
I've only just seen this so apologies for the delay.

> [@benarar](#):
>
> I am concerned that if I build a product using this that it may not be supported in a future version

We use the experimental marker for new features where we're unsure if the design is fully settled and hence reserve the right to make breaking changes or remove the feature completely.

Feedback from users is crucial to understanding if the feature is:

a) being used and  
b) fit for purpose.

If we get a "yes" to both of those questions a feature will typically have the experimental marker removed and you can rely on it.  
Your input would be welcomed on this. Entity extraction is not performed by the majority of users so any feedback is good.  
One piece of feedback I have had is that some entity extractors produce nested observations e.g. The string `President of Mexico` might identify a person but the last word might also be identified as a country. There were questions as to whether we should extend the syntax to support nesting of annotations which take us closer to requiring something like XML. A workaround using the existing format is to encode flattened as follows: `[President of](Andrés+Obrador) [Mexico](Andrés+Obrador&Mexico)`.  
Is this an issue you have grappled with?

---

<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:** [April 3, 2020, 9:31am UTC](https://discuss.elastic.co/t/continued-support-for-annotated-text-plugin/218688/3 "2020-04-03T09:31:31Z")

</div>

Closed on April 3, 2020, 9:31am UTC

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