[
https://issues.apache.org/jira/browse/SOLR-14701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433648#comment-17433648
]
Jan Høydahl commented on SOLR-14701:
------------------------------------
{quote}Deprecate the {{add-unknown-fields-to-the-schema}} URP chain from the
{{_default}} schema in 8.11, as well as the
{{solr.AddSchemaFieldsUpdateProcessorFactory}}. Remove them in 9.0
{quote}
+1 But should we make the URP available in some way in 9.x too? Like a contrib
or package for those who desperately need to keep some workflow a litte longer?
{quote}Keep the "transformational" URP stages like {{parse-date}} and wire into
the Schema Designer UI to let users toggle these features on/off for their URP
chain
{quote}
Yea, but would the UI then mutate the config for the user to insert those? I'm
not very fond of the whole config-overlay.json. We should have got rid of
solrconfig.xml and just have a (managed) solrconfig.json... For the specific
case of accepting more date formats, would it be an option to add that as a
feature to DatePointField itself? The FieldType already supports a few formats
including DateMath, so being able to specify what date format(s) a certain date
field can parse directly in the schema feels "cleaner", keeping the date config
in one place.
{quote}Continually improve the Schema Designer experience throughout Solr 9.x,
such as adding support for PDFs and other common rich document types
Update the ref guide to point users to the Schema Designer as a getting started
tool; also remove all the field guessing content
{quote}
This all sounds good. Have not looked closely at the schema designer code. Is
most logic in JS or can you do a round of "guessing" using REST calls as well?
> 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
> Priority: Blocker
> Fix For: main (9.0)
>
> 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...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
