: Hi Erick,Thanks for your reply.No, we aren't using schemaless
: mode. is not explicitly declared in
: our solrconfig.xmlAlso we have only one replica and one shard.
ManagedIndexSchemaFactory has been the default since 6.0 unless an
explicit schemaFactory is defined...
https://lucene.apac
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 -act
On 10/11/2018 10:07 AM, Mikhail Ibraheem wrote:
Hi Erick,Thanks for your reply.No, we aren't using schemaless mode.
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 s
Erick,
I don't get any such message when I start solr - could you share what
that curl command should be?
You suggest modifying solrconfig.xml - could you be more explicit on
what changes to make?
Terry
On 10/11/2018 11:52 AM, Erick Erickson wrote:
> bq: Also why solr updates and persists the
Hi Erick,Thanks for your reply.No, we aren't using schemaless mode.
is not explicitly declared in our solrconfig.xmlAlso we have
only one replica and one shard.
Any help?
ThanksMikhail
On Thursday, 11 October 2018, 17:53:01 EET, Erick Erickson
wrote:
bq: Also why solr updates and pe
bq: Also why solr updates and persists the managed-schema while ingesting data?
I'd guess you are using "schemaless mode", which is expressly
recommended _against_ for production systems. See "Schemaless Mode" in
the reference guide.
I'd disable schemaless mode (when you start Solr there should b
Hi,We upgraded to Solr 7.5, we try to ingest to solr using solrJ in concurrent
updates (Many threads).We are getting this exception:o.a.s.s.ManagedIndexSchema
Bad version when trying to persist schema using 1 due to:
org.apache.zookeeper.KeeperException$BadVersionException: KeeperErrorCode =
Ba
