[
https://issues.apache.org/jira/browse/SOLR-13292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783616#comment-16783616
]
Andrzej Bialecki commented on SOLR-13292:
------------------------------------------
This patch adds a new COLSTATUS command and an extended support in
{{SegmentsInfoRequestHandler}} for reporting low-level details of Lucene
segments and their compliance with the current schema.
Example requests:
{code:java}
http://localhost:8983/solr/gettingstarted/admin/segments?coreInfo=true&fieldInfo=true
http://localhost:8983/solr/admin/collections?action=COLSTATUS&fieldInfo=true&segments=true{code}
Responses are attached.
> Provide extended per-segment status of a collection
> ---------------------------------------------------
>
> Key: SOLR-13292
> URL: https://issues.apache.org/jira/browse/SOLR-13292
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: master (9.0), 8x
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Priority: Major
> Attachments: SOLR-13292.patch
>
>
> When changing a collection configuration or schema there may be non-obvious
> conflicts between existing data and the new configuration or the newly
> declared schema. A similar situation arises when upgrading Solr to a new
> version while keeping the existing data.
> Currently the {{SegmentsInfoRequestHandler}} provides insufficient
> information to detect such conflicts. Also, there's no collection-wide
> command to gather such status from all shard leaders.
> This issue proposes extending the {{/admin/segments}} handler to provide more
> low-level Lucene details about the segments, including potential conflicts
> between existing segments' data and the current declared schema. It also adds
> a new COLSTATUS collection command to report an aggregated status from all
> shards, and optionally for all collections.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
