You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2013/10/01 17:12:24 UTC
[jira] [Commented] (SOLR-5292) Add SKIP_MUTATE_SINGLETON to
FieldValueMutatingUpdateProcessor
[ https://issues.apache.org/jira/browse/SOLR-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783039#comment-13783039 ]
Hoss Man commented on SOLR-5292:
--------------------------------
Shawn: i feel like i'm missing something here... other then the slightly diff logging in your patch, how would returning this new singleton be any diff then just returning the input value in the code today?
> Add SKIP_MUTATE_SINGLETON to FieldValueMutatingUpdateProcessor
> --------------------------------------------------------------
>
> Key: SOLR-5292
> URL: https://issues.apache.org/jira/browse/SOLR-5292
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 4.5
> Reporter: Shawn Heisey
> Assignee: Shawn Heisey
> Priority: Minor
> Fix For: 5.0, 4.6
>
> Attachments: SOLR-5292.patch
>
>
> While trying to solve a problem, I came up with something that didn't work for what I was trying to do, but seemed like it might be useful for somebody. This allows somebody to decide during the course of a mutateValue method that they'd rather skip the mutate entirely - leave the source field value completely unchanged.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org