Hello Shawn, Yes! That was exactly what happened... After your recommendation the insert using solrj was successful.
Many thanks! Best regards, Pedro Figueiredo Senior Engineer pjlfigueir...@criticalsoftware.com M. 934058150 Rua Engº Frederico Ulrich, nº 2650 4470-605 Moreira da Maia, Portugal T. +351 229 446 927 | F. +351 229 446 929 www.criticalsoftware.com PORTUGAL | UK | GERMANY | USA | BRAZIL | MOZAMBIQUE | ANGOLA A CMMI® LEVEL 5 RATED COMPANY CMMI® is registered in the USPTO by CMU" -----Original Message----- From: Shawn Heisey [mailto:apa...@elyograg.org] Sent: 12 March 2015 22:45 To: solr-user@lucene.apache.org Subject: Re: error message This IndexSchema is not mutable with a classicSchemaIndexFactory On 3/12/2015 12:43 PM, Pedro Figueiredo wrote: > I saw an issue in Jira > (https://issues.apache.org/jira/browse/SOLR-7234) > with status Resolved, but the resolution is not identified in the issue. > > I am facing the exact same problem.. and not able to identified the > solution. I believe the problem is that you are using ClassicSchemaIndexFactory, but you did not remove AddSchemaFieldsUpdateProcessorFactory from the updateRequestProcessorChain config. That update processor requires the managed schema factory. Chances are that you started with the data-driven example config set and then realized you did not need/want the managed schema, so you switched to the classic factory. If you do not want the managed schema, you should probably start with the techproducts example rather than the data-driven example. I think we need to add some info to the schemaFactory comment in the data-driven example config so that people know they need to also modify the update processor chain when they want to disable the Schema API. Thanks, Shawn
