On Fri, Jan 4, 2019 at 12:51 PM Shawn Heisey <[email protected]> wrote:
> 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. > I addressed this earlier -- search for "luceneMatchVersion" which is key. RE a file based system schema (what Alexandre suggested)... that sounds workable but a more complex idea that would take more code & documentation -- at least relative to the very simple idea of some built-ins in the code (my proposal). See SOLR-12768.patch <https://issues.apache.org/jira/secure/attachment/12953284/SOLR-12768.patch> changes to IndexSchema. -- Lucene/Solr Search Committer (PMC), Developer, Author, Speaker LinkedIn: http://linkedin.com/in/davidwsmiley | Book: http://www.solrenterprisesearchserver.com
