[jira] [Commented] (SOLR-14701) Deprecate Schemaless Mode (Discussion)

["Ishan Chattopadhyaya (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-14701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17169474#comment-17169474 ] 

Ishan Chattopadhyaya commented on SOLR-14701:
---------------------------------------------

+1, this is the default experience today and is totally broken. We should either fix it or remove it. BTW, we need to revive SOLR-11741.
Thanks for starting this discussion Marcus. Even though dev@ list may have been a better place, but now that this issue exists, we should document some examples where schemaless is broken and confuses users.

> 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: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org