lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (SOLR-7741) SolrIndexerConfig.toMap missing fields
Date Fri, 03 Jul 2015 16:01:04 GMT


ASF subversion and git services commented on SOLR-7741:

Commit 1689041 from [~andyetitmoves] in branch 'dev/trunk'
[ ]

SOLR-7741: Add missing fields to SolrIndexerConfig.toMap

> SolrIndexerConfig.toMap missing fields
> --------------------------------------
>                 Key: SOLR-7741
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: Trunk
>            Reporter: Mike Drob
>             Fix For: Trunk
>         Attachments: SOLR-7741.patch, SOLR-7741.patch
> From the mailing list:
> Mike Drob wrote:
> {quote}
> I was looking through code for unrelated reasons and this line stuck out to me:
> if(mergeSchedulerInfo != null) m.put("mergeScheduler",mergeSchedulerInfo.toMap()); if(mergePolicyInfo
!= null) m.put("mergeScheduler",mergePolicyInfo.toMap());
> Are they both supposed to be using the "mergeScheduler" key? If not, happy to open a
JIRA and provide the one-line patch.
> {quote}
> Christine Poerschke wrote:
> {quote}
> Follow-on question, also re: SolrIndexConfig's toMap method. The constructor reads "/mergedSegmentWarmer"
and "/infoStream" and "/infoStream/@file" elements but the toMap method does not write them.
> Would that be intended or is it maybe an unintended omission? If intended would be great
to have a comment in toMap to clarify why/which elements are skipped, so that if/when a new
element is added its easier to determine if toMap should write the new element also.
> {quote}

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message