Finally, since you are trying to really tweak the schema and
general
configuration right from the start, you may find some of my
presentations
useful, as they show the minimal configuration. Not perfect for
your needs,
as I do skip _version, but as an additional data point. The
recent one is:
Shawn Heisey writes:
On 1/23/2019 3:49 AM, Aleksandar Dimitrov wrote:
Hi Alex,
thanks for you answer. I took the lines directly from the
managed-schema, deleted the managed-schema, and pasted those
lines into
my schema.xml.
Unless you have changed the solrconfig.xml to refer to the
On 1/23/2019 3:49 AM, Aleksandar Dimitrov wrote:
Hi Alex,
thanks for you answer. I took the lines directly from the
managed-schema, deleted the managed-schema, and pasted those lines into
my schema.xml.
Unless you have changed the solrconfig.xml to refer to the classic
schema, the file named
If you do not use API or Admin to change schema, it will not get
automatically rewritten. So you can just stay with managed-shema file and
version that. You can even disable write changes in solrconfig.xml:
Hi Alex,
thanks for you answer. I took the lines directly from the
managed-schema, deleted the managed-schema, and pasted those lines
into
my schema.xml.
If I have other errors in the schema.xml (such as a missing field
type),
solr complains about those until I fix them. So I would guess
What do you mean schema.xml from managed-schema? schema.xml is old
non-managed approach. If you have both, schema.xml will be ignored.
I suspect you are not running with the schema you think you do. You can
check that with API or in Admin UI if you get that far.
Regards,
Alex
On Tue, Jan
Hi,
I'm using solr 7.5, in my schema.xml I have this, which I took
from the
managed-schema:
stored="false" />
docValues="true" />
However, on startup, solr complains:
Caused by: org.apache.solr.common.SolrException: _version_ field
must exist in schema and be searchable (indexed
