[
https://issues.apache.org/jira/browse/SOLR-14701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17169943#comment-17169943
]
Ishan Chattopadhyaya commented on SOLR-14701:
---------------------------------------------
Schemaless or data driven, whatever we call it, is enabled by default.
Arguments presented over time has been that this mode allows quick exploration.
If such exploration results in a bad experience, don't you think we have lost
the user to a competitive search engine?
I recommend we implement something like SOLR-11741, encourage that as a way for
exploration. And we remove data driven mode as the default, and possibly
deprecate it.
Regarding where to discuss this, I would've preferred we do it in the dev list,
but there's absolutely nothing wrong with doing it here. Thanks Marcus for
taking the initiative. I agree with Jan that provoking vetos etc are against
the spirit of ASF, community over code.
> 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]
