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

Noble Paul commented on SOLR-14701:
-----------------------------------

[~hossman]

I like  SOLR-11741 

 . I have  a problem with a URP adding a field type in the same request and 
adding the document to the index. It usually makes the wrong guesses and 
eventually the user cannot change the field because the document is already 
indexed . Most users have no idea how to even change the field type. it's all 
magic and it's useless.

[~arafalov]

We do not need to support all data formats on this request handler. Even if we 
just do JSON , that helps 99% of the users.

{quote}If we are keeping the URPChain, we will need in this new UpdateHandler 
{quote}

My suggestion is , just throw away the current URP ball and chain. The code is 
a mess. Just build a simple request handler , do something simple and 
eventually deprecate this 

> 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: 4h 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

Reply via email to