Browse files

remove reference to velocityresponsewriter in solrconfig.xml

it is not longer part of solr-core api
  • Loading branch information...
reger24 committed Jun 15, 2017
1 parent 4be4bfb commit 9220ccbec7a7d6f2b81fecc6c0de565b098f7db7
Showing with 2 additions and 39 deletions.
  1. +2 −39 defaults/solr/solrconfig.xml
@@ -738,7 +738,7 @@
<lst name="defaults">
<str name="echoParams">explicit</str>
<int name="rows">10</int>
<str name="df">text</str>
<str name="df">text_t</str>
<!-- In addition to defaults, "appends" params can be specified
to identify values which should be appended to the list of
@@ -804,37 +804,7 @@
<!-- A Robust Example
This example SearchHandler declaration shows off usage of the
SearchHandler with many defaults declared
Note that multiple instances of the same Request Handler
(SearchHandler) can be registered multiple times with different
names (and different init parameters)
<requestHandler name="/browse" class="solr.SearchHandler">
<lst name="defaults">
<str name="echoParams">explicit</str>
<!-- VelocityResponseWriter settings -->
<str name="wt">velocity</str>
<str name="v.template">browse</str>
<str name="v.layout">layout</str>
<!-- Query settings -->
<str name="defType">edismax</str>
<str name="q.alt">*:*</str>
<str name="rows">10</str>
<str name="fl">*,score</str>
<!-- Faceting defaults -->
<str name="facet">on</str>
<str name="facet.mincount">1</str>
<initParams path="/update/**,/query,/select,/tvrh,/elevate,/spell,/browse">
<initParams path="/update/**,/query,/select,/tvrh,/elevate,/spell">
<lst name="defaults">
<str name="df">text</str>
@@ -1328,13 +1298,6 @@
<str name="content-type">text/plain; charset=UTF-8</str>
Custom response writers can be declared as needed...
<queryResponseWriter name="velocity" class="solr.VelocityResponseWriter" startup="lazy">
<str name="template.base.dir">${velocity.template.base.dir:}</str>
<!-- XSLT response writer transforms the XML output by any xslt file found
in Solr's conf/xslt directory. Changes to xslt files are checked for

2 comments on commit 9220ccb


This comment has been minimized.


luccioman replied Jul 18, 2017

Thanks again @reger24 for your care to maintain YaCy up to date and stable.

After the upgrade to Solr 6.6, you maybe noticed a warning still remains at startup

org.apache.solr.schema.ManagedIndexSchemaFactory The schema has been upgraded to managed, but the non-managed schema schema.xml is still loadable. PLEASE REMOVE THIS FILE.

(also reported by otter on YaCy forum )

Don't you think we should configure YaCy to explicitly use the ClassicIndexSchemaFactory as we would still eventually need to edit manually the remaining schema.xml in the future? Unless there are really good reasons to definitely abandon this and switch to the new default Managed schema?

Personally I probably won't have time for YaCy before a few weeks, but maybe you would be interested to check this point.

See you later


This comment has been minimized.


reger24 replied Jul 23, 2017

Hi @luccioman ,
yep.... noticed it too, with the Solr schema.xml, locally tried it without (deleted) schema. Works fine either way, but didn't closely study the docu of possible impacts, but agree warnings are things to fix but also have still some time constrains. Will've a 2nd look.

Please sign in to comment.