[ 
https://issues.apache.org/jira/browse/SOLR-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118993#comment-13118993
 ] 

Martijn van Groningen commented on SOLR-2802:
---------------------------------------------

bq. And if we're going to require that they provide at least one of the field 
selectors, and we want to offer them syntactic sugar for "match all field" why 
not make it the shortest sugar possible?.
I'm doubting now about this as well... Maybe we should go with a default that 
processes all fields. I guess that this behaviour should be documented well. If 
a user doesn't want for example trimming then the 
TrimFieldUpdateProcessorFactory shouldn't have been configured in the first 
place. 

I think I don't completely follow the explicit ruling. I think Date/Number 
parsing should only be done on compatible fields only. I think if a subsequent 
parser moves / renames fields, then this processor should have been configured 
before the processor that does the Date/Number parsing. If processors also try 
to parse incompatible fields, then this might end up in an exception being 
thrown (depends on if exceptions get swallowed or not). 

bq. behavior on all but on field (unless we add some sort of exclusion 
option(s)). 
+1 We definitely need this! 
                
> Toolkit of UpdateProcessors for modifying document values
> ---------------------------------------------------------
>
>                 Key: SOLR-2802
>                 URL: https://issues.apache.org/jira/browse/SOLR-2802
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Hoss Man
>         Attachments: SOLR-2802_update_processor_toolkit.patch
>
>
> Frequently users ask about questions about things where the answer is "you 
> could do it with an UpdateProcessor" but the number of our of hte box 
> UpdateProcessors is generally lacking and there aren't even very good base 
> classes for the common case of manipulating field values when adding documents

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to