[
https://issues.apache.org/jira/browse/SOLR-14701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17169865#comment-17169865
]
Jan Høydahl commented on SOLR-14701:
------------------------------------
First, I am surprised by the proposed development practices suggested here.
Let's instead continue to seek broad consensus and discussing with our peers,
and if you cannot reach consensus, maybe there is a slight chance that the
proposal can be improved :) Provoking vetos and conflict is not in the spirit
of the ASF and does not create the type of community we want to welcome folks
into.
{quote}It doesn't work as named or documented ... If you use it in production
reliably and in a way that cannot be accomplished another way...
{quote}
I question the background for your conclusion. The feature is documented as "_a
set of Solr features that, when used together, allow users to rapidly construct
an effective schema by simply indexing sample data, without having to manually
edit the schema_". And there is a fat warning against relying on this in
produciton: "_You are *strongly* urged to disable schemaless mode for
production systems. Schemaless mode makes assumptions when deciding the type
and use of a field the first time that field is encountered in a document.
These assumptions are likely sub-optimal in many cases._".
So nobody is promising this is a silver bullet, but it is a fast way to
prototype and bootstrap a project, with follow-on hand polishing of the schema.
Thus, which promise do you claim we are breaking? Users will always misuse a
product or not care to read documentation. For those, we even have a fat CLI
warning once you "bin/solr create" a collection with schemaless mode.
> Deprecate Schemaless Mode (Discussion)
> --------------------------------------
>
> Key: SOLR-14701
> URL: https://issues.apache.org/jira/browse/SOLR-14701
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Schema and Analysis
> Reporter: Marcus Eagan
> Priority: Major
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
