On 3/20/2017 9:22 AM, Issei Nishigata wrote:
> Is my understanding correct that managed-schema is not limited that it
> can be modified only via Schema API, but that we usually modify it via
> Schema API, and we also can modify what Schema API can't do by
> hand-editing? Needless to say, I understa
Thank you for these information.
but I am still confusing about specification of managed-schema.
I recognize that I cannot modify "unique id" or "Similarity" by Schema API
now.
* https://issues.apache.org/jira/browse/SOLR-7242
Isn't there any other way than hand-editing in this particular case?
2/27/2017 4:46 AM, Issei Nishigata wrote:
> Thank you for your reply. If I was to say which one, I'd maybe be
> talking about the concept for Solr. I understand we should use
> "ClassicSchemaFactory" when we want to hand-edit, but why are there
> two files, schema.xml and managed-schema, in spite t
see:
https://cwiki.apache.org/confluence/display/solr/Schema+Factory+Definition+in+SolrConfig#SchemaFactoryDefinitioninSolrConfig-Switchingfromschema.xmltoManagedSchema
bq: If we can modify the schema.xml
through Schema API
You can't do this by default, but if you insist you can change
the Schem
Thank you for your reply.
If I was to say which one, I'd maybe be talking about the concept for Solr.
I understand we should use "ClassicSchemaFactory" when we want to
hand-edit, but why are there two files, schema.xml and managed-schema, in
spite that we can hand-edit managed-schema? If we can mo
This is the sequence that gets you in trouble:
> start solr
> hand edit the schema _without_ reloading your collection or restarting all
> your Solr instances.
> use the managed-schema API to make modifications.
In this scenario your hand-edits can be lost since the in-memory version of the
schem
