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

Andrzej Bialecki  commented on SOLR-11127:
------------------------------------------

The latest patch. This includes a {{.system}} compatibility check that is 
performed on {{Overseer}} leader startup. This verification only logs a warning 
about the potentially incompatible index data, providing details of schema 
fields that are likely incompatible. This should provide sufficient information 
for users to decide whether to re-index the collection.

If there are no objections I'd like to commit this shortly.

> Add a Collections API command to migrate the .system collection schema from 
> Trie-based (pre-7.0) to Points-based (7.0+)
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-11127
>                 URL: https://issues.apache.org/jira/browse/SOLR-11127
>             Project: Solr
>          Issue Type: Task
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Steve Rowe
>            Assignee: Andrzej Bialecki 
>            Priority: Blocker
>              Labels: numeric-tries-to-points
>             Fix For: 8.1, master (9.0)
>
>         Attachments: SOLR-11127.patch, SOLR-11127.patch, SOLR-11127.patch, 
> SOLR-11127.patch
>
>
> SOLR-11119 will switch the Trie fieldtypes in the .system collection's schema 
> to Points.
> Users with pre-7.0 .system collections will no longer be able to use them 
> once Trie fields have been removed (8.0).
> Solr should provide a Collections API command MIGRATESYSTEMCOLLECTION to 
> automatically convert a Trie-based .system collection to a Points-based one.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to