...
Edit solr-4.6.0/example/solr/collection1/conf/solrconfig.xml, un-commenting the schemaFactory element in lines 134-37, and commenting out the schemaFactory element in line 151, as shown below:
| Code Block |
|---|
| language | xml |
|---|
| firstline | 132 |
|---|
| title | solrconfig.xml |
|---|
| firstline | 132 |
|---|
| linenumbers | true |
|---|
|
<!-- To enable dynamic schema REST APIs, use the following for <schemaFactory>: -->
<schemaFactory class="ManagedIndexSchemaFactory">
<bool name="mutable">true</bool>
<str name="managedSchemaResourceName">managed-schema</str>
</schemaFactory>
<!-- When ManagedIndexSchemaFactory is specified, Solr will load the schema from
the resource named in 'managedSchemaResourceName', rather than from schema.xml.
Note that the managed schema resource CANNOT be named schema.xml. If the managed
schema does not exist, Solr will create it after reading schema.xml, then rename
'schema.xml' to 'schema.xml.bak'.
Do NOT hand edit the managed schema - external modifications will be ignored and
overwritten as a result of schema modification REST API calls.
When ManagedIndexSchemaFactory is specified with mutable = true, schema
modification REST API calls will be allowed; otherwise, error responses will be
sent back for these requests.
-->
<!-- <schemaFactory class="ClassicIndexSchemaFactory"/> --> |
| Warning |
|---|
The fcrepo-message-consumer SolrIndexer implementation does not commit upon updates. In order to see the changes, you must configure Solr to have a commit strategy that is appropriate for your use. Resource removal events do trigger a commit. |
| Code Block |
|---|
| language | xml |
|---|
| firstline | 349 |
|---|
| title | solrconfig.xml | firstline | 349 |
|---|
|
<!-- AutoCommit
Perform a hard commit automatically under certain conditions.
Instead of enabling autoCommit, consider using "commitWithin"
when adding documents.
http://wiki.apache.org/solr/UpdateXmlMessages
maxDocs - Maximum number of documents to add since the last
commit before automatically triggering a new commit.
maxTime - Maximum amount of time in ms that is allowed to pass
since a document was added before automatically
triggering a new commit.
openSearcher - if false, the commit causes recent index changes
to be flushed to stable storage, but does not cause a new
searcher to be opened to make those changes visible.
If the updateLog is enabled, then it's highly recommended to
have some sort of hard autoCommit to limit the log size.
-->
<autoCommit>
<maxTime>${solr.autoCommit.maxTime:15000}</maxTime>
<openSearcher>false</openSearcher>
</autoCommit> |
...