[jira] [Updated] (SOLR-13292) Provide extended per-segment status of a collection
[
https://issues.apache.org/jira/browse/SOLR-13292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Risden updated SOLR-13292:
Affects Version/s: (was: 8.x)
8.0
> 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.0, 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-13292) Provide extended per-segment status of a collection
[
https://issues.apache.org/jira/browse/SOLR-13292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrzej Bialecki updated SOLR-13292:
-
Attachment: adminSegments.json
> 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, 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-13292) Provide extended per-segment status of a collection
[
https://issues.apache.org/jira/browse/SOLR-13292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrzej Bialecki updated SOLR-13292:
-
Attachment: colstatus.json
> 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, 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-13292) Provide extended per-segment status of a collection
[
https://issues.apache.org/jira/browse/SOLR-13292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrzej Bialecki updated SOLR-13292:
-
Attachment: SOLR-13292.patch
> 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, SOLR-13292.patch, adminSegments.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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-13292) Provide extended per-segment status of a collection
[
https://issues.apache.org/jira/browse/SOLR-13292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrzej Bialecki updated SOLR-13292:
-
Attachment: colstatus.json
> 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, adminSegments.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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-13292) Provide extended per-segment status of a collection
[
https://issues.apache.org/jira/browse/SOLR-13292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrzej Bialecki updated SOLR-13292:
-
Attachment: adminSegments.json
> 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, adminSegments.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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-13292) Provide extended per-segment status of a collection
[
https://issues.apache.org/jira/browse/SOLR-13292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrzej Bialecki updated SOLR-13292:
-
Attachment: SOLR-13292.patch
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
