[
https://issues.apache.org/jira/browse/SOLR-13259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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: [email protected]
For additional commands, e-mail: [email protected]
