[ https://issues.apache.org/jira/browse/SOLR-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205126#comment-13205126 ]
Robert Muir commented on SOLR-2802: ----------------------------------- {quote} but failing hard is definitely better – at least by default. {quote} Thanks, I think this makes it a lot less scary! {quote} UpdateProcessors deal with SolrInputDocuments & SolrInputFields that are just bags of objects {quote} ok, looking around I can see this is a larger type-safety issue that shouldn't be addressed on this issue. Thanks for fixing the change (and fixing the eclipse compile). > 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 > Assignee: Hoss Man > Fix For: 4.0 > > Attachments: SOLR-2802_update_processor_toolkit.patch, > SOLR-2802_update_processor_toolkit.patch, > SOLR-2802_update_processor_toolkit.patch, > SOLR-2802_update_processor_toolkit.patch, > 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