[
https://issues.apache.org/jira/browse/SOLR-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697998#comment-13697998
]
Shawn Heisey commented on SOLR-4987:
------------------------------------
Would we want the new API to be enabled by default, or something you have to
specifically turn on in the config?
If we want it always enabled, then we should log a warning if the user's schema
is incompatible with automated reindexing, and any attempt to use the API
should fail spectacularly. If it must be specifically enabled, then we should
throw an exception that prevents core startup. My initial bias is to make it
something you have to enable, so if the user enables it and has an incompatible
schema, they'll know it immediately because they won't be able to use their
index. I could be persuaded the other way with a good argument.
> Add reindex API
> ---------------
>
> Key: SOLR-4987
> URL: https://issues.apache.org/jira/browse/SOLR-4987
> Project: Solr
> Issue Type: New Feature
> Affects Versions: 4.3.1
> Reporter: Shawn Heisey
> Priority: Minor
>
> A lot of users ask "how do I reindex?" We have a wiki page that explains
> this:
> http://wiki.apache.org/solr/HowToReindex
> For many such users, this is not acceptable. They assume that once the
> information is in Solr, it should be possible for Solr to change how it's
> indexed at the touch of a button. I don't think they like it when they are
> told that it's not possible.
> Perhaps it's time to give these users what they want -- if they store all
> fields that are not copyField destinations.
> A note to people who find this issue: Until it is marked Resolved with a
> "Fixed" or "Implemented" notation, be aware that this has not yet happened,
> and there is no guarantee that it WILL happen.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
