You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Andrzej Bialecki (JIRA)" <ji...@apache.org> on 2019/03/04 18:12:00 UTC
[jira] [Created] (SOLR-13292) Provide extended per-segment status
of a collection
Andrzej Bialecki created SOLR-13292:
----------------------------------------
Summary: 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
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org