ASF GitHub Bot commented on NUTCH-2654:

r0ann3l commented on issue #468: NUTCH-2654: The obsolete configuration of 
index writers has been removed.
URL: https://github.com/apache/nutch/pull/468#issuecomment-526946398
   In this PR the schema.xml file has not been deleted. I assume that this file 
is kept in Nutch distribution as reference of how Solr has to be configured. 
But I believe this file has to be removed as well, because:
   - Maybe this file was necessary when Nutch had only the Solr index writer 
out-of-the-box. But now, there are more index writers available in Nutch 
distribution. So, why do we have to keep this file? Why we don't have 
references of the configuration of other indexers available in Nutch too?
   - In the mail list I've seen some people a little confuse about the use of 
this file. Sometimes the users think that this file has to match with the 
schema.xml file in Solr side, when actually this file is never used by Nutch at 
   So, what do you think about it folks?
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Remove obsolete index-writer configuration in conf/
> ---------------------------------------------------
>                 Key: NUTCH-2654
>                 URL: https://issues.apache.org/jira/browse/NUTCH-2654
>             Project: Nutch
>          Issue Type: Improvement
>          Components: indexer
>    Affects Versions: 1.15
>            Reporter: Sebastian Nagel
>            Assignee: Roannel Fernández Hernández
>            Priority: Major
>             Fix For: 1.16
> The configuration folder conf/ still contains stuff obsolete after NUTCH-1480:
> - properties to configure indexer plugins in nutch-default.xml
> - solrindex-mapping.xml (looks like obsolete)
> - (still read) elasticsearch.conf
> All obsolete files and properties should be removed.

This message was sent by Atlassian Jira

Reply via email to