[
https://issues.apache.org/jira/browse/SOLR-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13784735#comment-13784735
]
ASF subversion and git services commented on SOLR-5264:
-------------------------------------------------------
Commit 1528699 from [~elyograg] in branch 'dev/trunk'
[ https://svn.apache.org/r1528699 ]
SOLR-5264 removing deprecated "oneOrMany" method from trunk
> New method on NamedList to return one or many config arguments as collection
> ----------------------------------------------------------------------------
>
> Key: SOLR-5264
> URL: https://issues.apache.org/jira/browse/SOLR-5264
> Project: Solr
> Issue Type: Improvement
> Components: clients - java
> Affects Versions: 4.5
> Reporter: Shawn Heisey
> Assignee: Shawn Heisey
> Priority: Minor
> Fix For: 5.0, 4.6
>
> Attachments: SOLR-5264.patch, SOLR-5264.patch, SOLR-5264.patch,
> SOLR-5264.patch, SOLR-5264.patch
>
>
> In the FieldMutatingUpdateProcessorFactory is a method called "oneOrMany"
> that takes all of the entries in a NamedList and pulls them out into a
> Collection. I'd like to use that in a custom update processor I'm building.
> It seems as though this functionality would be right at home as part of
> NamedList itself. Here's a patch that moves the method.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
