Bah, I should have said when you create a collection. You get the
following if you create your collection using the default schema:
WARNING: Using _default configset with data driven schema
functionality. NOT RECOMMENDED for production use.
To turn off: bin/solr config -c eoe -p 8982 -action
set-user-property -property update.autoCreateFields -value false
But as Shawn says, if you have add-unknown-fields-to-the-schema
configured in your update processor chain in solrconfig.xml, you're
using schemaless mode.
Best,
Erick
On Thu, Oct 11, 2018 at 9:58 AM Shawn Heisey <apa...@elyograg.org> wrote:
>
> On 10/11/2018 10:07 AM, Mikhail Ibraheem wrote:
> > Hi Erick,Thanks for your reply.No, we aren't using schemaless mode.
> > <schemaFactory/> is not explicitly declared in our solrconfig.xml
>
> Schemaless mode is not turned on by the schemaFactory config element.
>
> The default configurations that Solr ships with have schemaless mode
> enabled. It is handled with an update processor chain named
> add-unknown-fields-to-the-schema. As Erick mentioned, we *STRONGLY*
> recommend that you disable this in production. In version 7.5, you only
> need to change whether that update chain is set to the default chain.
> This can be handled with a property (update.autoCreateFields) but you
> can just also edit solrconfig.xml to change the "default" attribute to
> false.
>
> The exception you're getting is
> org.apache.zookeeper.KeeperException$BadVersionException which comes
> from zookeeper. Can you share the *entire* error? It will likely be a
> few dozen lines in length and may contain multiple "Caused by" sections,
> each with their own stacktrace. With the entire error, we can narrow
> down what part of Solr code is executing when the error happens.
>
> Thanks,
> Shawn
>
