[
https://issues.apache.org/jira/browse/SOLR-14701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17202961#comment-17202961
]
Alexandre Rafalovitch commented on SOLR-14701:
----------------------------------------------
I don't see why we need another endpoint that takes a custom JSON and tries to
do something with it. That's what /update/json/docs are.
I also don't see any point arguing further about it. *The code is a mess* does
not seem to be a comment about my code specifically. For all I can tell, nobody
but me actually tried to run it. My code also does not do field typing and
adding document in one pass. So, it is just hand waving in the wrong direction.
Or quoting out of context.
I am going to mark this issue as a blocker for 9.0 and unassign myself. Like I
mentioned earlier, I am exercising my commiter *-1* on shipping current
implementation as part of default schema.
If nobody has any better idea by 9.0 checkpoint, we rip schemaless completely
from default schema, remove documentation, tell people it was a bad idea and
move on. The Add.. class can stay in the code base and anybody's existing
schema will just keep on working and can check 8.6 documentation if stuck.
> 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
