I'm jumping into this conversation a little bit late. Sorry for any
problems that causes.
On 1/4/2019 9:52 AM, Alexandre Rafalovitch wrote:
What about if a system schema was loaded at a startup implicitly.
Then, if a new schema is loaded and type definition is missing, it is
copied - at that time - into the specific schema. So, on the first
rewrite those - and only those used - types will be written out.
Looking at what came before, my preference would have been implicitly
defined default types -- things like int, string, etc, defined in code.
The only problem with that comes at Solr upgrade time ... what if we
decide for a later version (even if it's limited to a major release)
that IntPointField shouldn't be the implicit class for "int"? Someone
who upgrades an index using that implicit type to the new version will
find that Solr will no longer work. Which makes the idea unworkable.
A file-based system schema where implicit types are explicitly defined
is an interesting idea that I think would get around the problem
described above. We would need to decide exactly what can be defined in
the system schema -- my initial bias would be to only allow types, not
fields or other schema config, to be defined there. Probably a good
location for the system schema file would be the ZK chroot or the solr
home, depending on whether the system is in cloud mode.
Thanks,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
