[
https://issues.apache.org/jira/browse/STORM-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694638#comment-14694638
]
ASF GitHub Bot commented on STORM-974:
--------------------------------------
Github user caofangkun commented on a diff in the pull request:
https://github.com/apache/storm/pull/679#discussion_r36938292
--- Diff:
external/storm-elasticsearch/src/test/java/org/apache/storm/elasticsearch/bolt/EsPercolateBoltTest.java
---
@@ -21,6 +21,7 @@
import backtype.storm.tuple.Values;
import org.apache.storm.elasticsearch.common.EsConfig;
import org.apache.storm.elasticsearch.common.EsTestUtil;
+import org.apache.storm.elasticsearch.common.EsTupleMapper;
import org.elasticsearch.action.count.CountResponse;
import org.elasticsearch.action.percolate.PercolateResponse;
import org.elasticsearch.index.query.TermQueryBuilder;
--- End diff --
Line 25 27 28 unneeded imports
> [storm-elasticsearch] Introduces Tuple -> ES document mapper to get rid of
> constant field mapping (source, index, type)
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: STORM-974
> URL: https://issues.apache.org/jira/browse/STORM-974
> Project: Apache Storm
> Issue Type: Improvement
> Reporter: Jungtaek Lim
> Assignee: Jungtaek Lim
>
> For now EsIndexBolt uses constant field mapping (source, index, type) which
> is not flexible.
> We can introduce tuple -> ES document mapper interface to let users define
> their relationship, as other external modules did.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
