[
https://issues.apache.org/jira/browse/SOLR-14701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17194922#comment-17194922
]
Alexandre Rafalovitch commented on SOLR-14701:
----------------------------------------------
Ok, I believe the Schemaless alternative is ready (see the PR). The schema
modifications are done in the commit phase, so that creates a tiny bit of
awkwardness, but also some benefits (e.g. index a directory of files, then do
commit). The test files and schema/solrconfig.xml show how it needs to be
configured. Basically it is the same as before with updated URP name, but the
default is gone (just have String mapped as per latest setup anyway, just
without default flag). Also, the types can be singular (pdate, not pdates), but
it will work just the same without change, will just be effectively
double-declaring multivalued.
To trigger the schema guessing, pass guess-schema parameter with any value. So:
{noformat}
bin/post -c guess -params "guess-schema=true" example/films/films.json
{noformat}
As bin/post runs commit at the end, it will trigger the schema update then. But
no data will be entered. So, then, the real indexing command can run without
the flag. Obviously, this will need to be explained in RefGuide properly and
the whole thing will live in a dedicated example.
Please give it a spin and give some feedback.
> Deprecate Schemaless Mode (Discussion)
> --------------------------------------
>
> Key: SOLR-14701
> URL: https://issues.apache.org/jira/browse/SOLR-14701
> Project: Solr
> Issue Type: Improvement
> Components: Schema and Analysis
> Reporter: Marcus Eagan
> Assignee: Alexandre Rafalovitch
> Priority: Major
> Attachments: image-2020-08-04-01-35-03-075.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I know this won't be the most popular ticket out there, but I am growing more
> and more sympathetic to the idea that we should rip many of the freedoms out
> that cause users more harm than not. One of the freedoms I saw time and time
> again to cause issues was schemaless mode. It doesn't work as named or
> documented, so I think it should be deprecated.
> If you use it in production reliably and in a way that cannot be accomplished
> another way, I am happy to hear from more knowledgeable folks as to why
> deprecation is a bad idea.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
