[
https://issues.apache.org/jira/browse/STREAMS-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169448#comment-14169448
]
ASF GitHub Bot commented on STREAMS-194:
----------------------------------------
GitHub user robdouglas opened a pull request:
https://github.com/apache/incubator-streams/pull/103
STREAMS-194 | Added constructor to allow for the overriding of the defau...
...lt Elasticsearch percolate field
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/robdouglas/incubator-streams STREAMS-194
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-streams/pull/103.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #103
----
commit b386a52e248b45436b017c0ac2d63361cb35195a
Author: Robert Douglas <[email protected]>
Date: 2014-10-13T16:09:01Z
STREAMS-194 | Added constructor to allow for the overriding of the default
Elasticsearch percolate field
----
> PercolateTagProcessor should allow the user to set the percolate field
> ----------------------------------------------------------------------
>
> Key: STREAMS-194
> URL: https://issues.apache.org/jira/browse/STREAMS-194
> Project: Streams
> Issue Type: Improvement
> Reporter: Robert Douglas
>
> As a developer, I should not be limited to only being able to percolate over
> the default "_all" field. Instead, I should have the option to pass in any
> field that I want, and if a field is omitted, to default to a sane standard
> ("_all")
> Acceptance Criteria:
> - Developer can pass in custom percolate field
> - If that field is omitted, a sane default is selected
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
