[
https://issues.apache.org/jira/browse/SOLR-13292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793540#comment-16793540
]
ASF subversion and git services commented on SOLR-13292:
--------------------------------------------------------
Commit f7e41ef86896d726b16391af8f44c4290fa07da5 in lucene-solr's branch
refs/heads/branch_8x from Andrzej Bialecki
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=f7e41ef ]
SOLR-13292: Fix a logic bug when point types are present, add more details to
the unit test.
> 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: 8.x, master (9.0)
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Priority: Major
> Fix For: 8.1, master (9.0)
>
> Attachments: SOLR-13292.patch, SOLR-13292.patch, adminSegments.json,
> adminSegments.json, colstatus.json, colstatus.json
>
>
> 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]
