[jira] [Commented] (SOLR-13259) Ref Guide: Add explicit docs on when to reindex after field/schema changes
[ https://issues.apache.org/jira/browse/SOLR-13259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806887#comment-16806887 ] ASF subversion and git services commented on SOLR-13259: Commit a9b62caf7dded486d7522ef85eef44b2bcbd70e2 in lucene-solr's branch refs/heads/branch_8_0 from Cassandra Targett [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=a9b62ca ] SOLR-13259: clarify language around *must* reindex vs *should* reindex > Ref Guide: Add explicit docs on when to reindex after field/schema changes > -- > > Key: SOLR-13259 > URL: https://issues.apache.org/jira/browse/SOLR-13259 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation >Reporter: Cassandra Targett >Assignee: Cassandra Targett >Priority: Major > Fix For: 8.0, master (9.0) > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Many changes to field definitions, field types, or other things defined in > the schema require documents to be reindexed, but some can be OK if the > consequences of not reindexing are acceptable, and still other changes do not > require a reindex at all. > It would be nice if the Ref Guide had some definitive information about these > types of changes to assist users with planning changes to the schema. -- 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] [Commented] (SOLR-13259) Ref Guide: Add explicit docs on when to reindex after field/schema changes
[ https://issues.apache.org/jira/browse/SOLR-13259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806886#comment-16806886 ] ASF subversion and git services commented on SOLR-13259: Commit 71cdf793ac7a6b0b5cc5c29c640aab820a736285 in lucene-solr's branch refs/heads/branch_8x from Cassandra Targett [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=71cdf79 ] SOLR-13259: clarify language around *must* reindex vs *should* reindex > Ref Guide: Add explicit docs on when to reindex after field/schema changes > -- > > Key: SOLR-13259 > URL: https://issues.apache.org/jira/browse/SOLR-13259 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation >Reporter: Cassandra Targett >Assignee: Cassandra Targett >Priority: Major > Fix For: 8.0, master (9.0) > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Many changes to field definitions, field types, or other things defined in > the schema require documents to be reindexed, but some can be OK if the > consequences of not reindexing are acceptable, and still other changes do not > require a reindex at all. > It would be nice if the Ref Guide had some definitive information about these > types of changes to assist users with planning changes to the schema. -- 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] [Commented] (SOLR-13259) Ref Guide: Add explicit docs on when to reindex after field/schema changes
[ https://issues.apache.org/jira/browse/SOLR-13259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806884#comment-16806884 ] ASF subversion and git services commented on SOLR-13259: Commit cc23cd9d558ecd4a86184685daff0c6c6e935a82 in lucene-solr's branch refs/heads/master from Cassandra Targett [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=cc23cd9 ] SOLR-13259: clarify language around *must* reindex vs *should* reindex > Ref Guide: Add explicit docs on when to reindex after field/schema changes > -- > > Key: SOLR-13259 > URL: https://issues.apache.org/jira/browse/SOLR-13259 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation >Reporter: Cassandra Targett >Assignee: Cassandra Targett >Priority: Major > Fix For: 8.0, master (9.0) > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Many changes to field definitions, field types, or other things defined in > the schema require documents to be reindexed, but some can be OK if the > consequences of not reindexing are acceptable, and still other changes do not > require a reindex at all. > It would be nice if the Ref Guide had some definitive information about these > types of changes to assist users with planning changes to the schema. -- 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] [Commented] (SOLR-13259) Ref Guide: Add explicit docs on when to reindex after field/schema changes
[ https://issues.apache.org/jira/browse/SOLR-13259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783622#comment-16783622 ] ASF subversion and git services commented on SOLR-13259: Commit 876fcb7f7b56b71020c5ed05a122bcfe766a10c0 in lucene-solr's branch refs/heads/master from Cassandra Targett [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=876fcb7 ] SOLR-13259: Add new section on Reindexing in Solr (#594) Add new reindexing.adoc page; standardize on "reindex" vs "re-index" > Ref Guide: Add explicit docs on when to reindex after field/schema changes > -- > > Key: SOLR-13259 > URL: https://issues.apache.org/jira/browse/SOLR-13259 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation >Reporter: Cassandra Targett >Assignee: Cassandra Targett >Priority: Major > Fix For: 8.0, master (9.0) > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Many changes to field definitions, field types, or other things defined in > the schema require documents to be reindexed, but some can be OK if the > consequences of not reindexing are acceptable, and still other changes do not > require a reindex at all. > It would be nice if the Ref Guide had some definitive information about these > types of changes to assist users with planning changes to the schema. -- 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] [Commented] (SOLR-13259) Ref Guide: Add explicit docs on when to reindex after field/schema changes
[ https://issues.apache.org/jira/browse/SOLR-13259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783624#comment-16783624 ] ASF subversion and git services commented on SOLR-13259: Commit 8d92a542bb64c5e52eb5727e0413b7deb1d0c212 in lucene-solr's branch refs/heads/branch_8_0 from Cassandra Targett [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=8d92a54 ] SOLR-13259: Add new section on Reindexing in Solr (#594) Add new reindexing.adoc page; standardize on "reindex" vs "re-index" > Ref Guide: Add explicit docs on when to reindex after field/schema changes > -- > > Key: SOLR-13259 > URL: https://issues.apache.org/jira/browse/SOLR-13259 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation >Reporter: Cassandra Targett >Assignee: Cassandra Targett >Priority: Major > Fix For: 8.0, master (9.0) > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Many changes to field definitions, field types, or other things defined in > the schema require documents to be reindexed, but some can be OK if the > consequences of not reindexing are acceptable, and still other changes do not > require a reindex at all. > It would be nice if the Ref Guide had some definitive information about these > types of changes to assist users with planning changes to the schema. -- 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] [Commented] (SOLR-13259) Ref Guide: Add explicit docs on when to reindex after field/schema changes
[ https://issues.apache.org/jira/browse/SOLR-13259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783623#comment-16783623 ] ASF subversion and git services commented on SOLR-13259: Commit 68adeab46a08fdc66c6d613e5761413f16b45c0e in lucene-solr's branch refs/heads/branch_8x from Cassandra Targett [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=68adeab ] SOLR-13259: Add new section on Reindexing in Solr (#594) Add new reindexing.adoc page; standardize on "reindex" vs "re-index" > Ref Guide: Add explicit docs on when to reindex after field/schema changes > -- > > Key: SOLR-13259 > URL: https://issues.apache.org/jira/browse/SOLR-13259 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation >Reporter: Cassandra Targett >Assignee: Cassandra Targett >Priority: Major > Fix For: 8.0, master (9.0) > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Many changes to field definitions, field types, or other things defined in > the schema require documents to be reindexed, but some can be OK if the > consequences of not reindexing are acceptable, and still other changes do not > require a reindex at all. > It would be nice if the Ref Guide had some definitive information about these > types of changes to assist users with planning changes to the schema. -- 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] [Commented] (SOLR-13259) Ref Guide: Add explicit docs on when to reindex after field/schema changes
[ https://issues.apache.org/jira/browse/SOLR-13259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16780863#comment-16780863 ] Hoss Man commented on SOLR-13259: - A few thoughts on some of the wording in the current patch... [https://github.com/apache/lucene-solr/commit/2bcc9f5d03962f3e3a80dd3181a076339f03534f.patch] bq. Reindexing is recommended during upgrades ... That may be a little overly strong? perhaps just say "Reindexing is recommended during major upgrades" ... bug fixes, and minor version upgrades shouldn't _usually_ require reindexing, and we don't want people avoiding bug fix upgrades out of a fear that they'll need to re-index. (elsewhere in the doc when "upgrade" is mentioned we should probably also substitute "major upgrade") In the section on field / field type properties there is this good note... bq. In some cases, it can be possible to change a field/field type property value and it will only apply to documents indexed _after_ the change. This is not recommended to ensure consistent behavior, but may be acceptable for your use case as a temporary condition before a full reindexing can be scheduled. ... a similar comment would probably make sense in the section on adding fields? i tend to find this type of "temporary condition until fully reindexed" more applicable when adding a field (and gradually re-indexing) then when changing a field property ... but they are both equally viable. We may want to explicitly call out changing the schema "version" property as a reason to re index, nothing that doing this is effectivally the same as altering the field type properties of many field types? > Ref Guide: Add explicit docs on when to reindex after field/schema changes > -- > > Key: SOLR-13259 > URL: https://issues.apache.org/jira/browse/SOLR-13259 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation >Reporter: Cassandra Targett >Assignee: Cassandra Targett >Priority: Major > Fix For: 8.0, master (9.0) > > Time Spent: 10m > Remaining Estimate: 0h > > Many changes to field definitions, field types, or other things defined in > the schema require documents to be reindexed, but some can be OK if the > consequences of not reindexing are acceptable, and still other changes do not > require a reindex at all. > It would be nice if the Ref Guide had some definitive information about these > types of changes to assist users with planning changes to the schema. -- 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
