From 8bebf2599ee0f1ab270e95a709477e8d59709bc1 Mon Sep 17 00:00:00 2001 From: Nik Everett Date: Fri, 5 Aug 2016 11:01:22 -0400 Subject: [PATCH] Add note explaining analysis caching for plugins ``` Elasticsearch doesn't have any automatic mechanism to share these components between indexes. If any component is heavy enough to warrant such sharing then it is the Pugin's responsibility to do it in their {@link AnalysisProvider} implementation. We recommend against doing this unless absolutely necessary because it can be difficult to get the caching right given things like behavior changes across versions. ``` Closes #19814 --- .../main/java/org/elasticsearch/plugins/AnalysisPlugin.java | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/core/src/main/java/org/elasticsearch/plugins/AnalysisPlugin.java b/core/src/main/java/org/elasticsearch/plugins/AnalysisPlugin.java index ffd278a5653..8c23e530e49 100644 --- a/core/src/main/java/org/elasticsearch/plugins/AnalysisPlugin.java +++ b/core/src/main/java/org/elasticsearch/plugins/AnalysisPlugin.java @@ -45,6 +45,10 @@ import static java.util.Collections.emptyMap; * } * } * } + * + * Elasticsearch doesn't have any automatic mechanism to share these components between indexes. If any component is heavy enough to warrant + * such sharing then it is the Pugin's responsibility to do it in their {@link AnalysisProvider} implementation. We recommend against doing + * this unless absolutely necessary because it can be difficult to get the caching right given things like behavior changes across versions. */ public interface AnalysisPlugin { /**