[
https://issues.apache.org/jira/browse/SOLR-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13698364#comment-13698364
]
Upayavira commented on SOLR-4987:
---------------------------------
Implement update by query on top of atomic updates, then you can reindex really
easily.
You do an atomic update of <query>*:*</query> without specifying any fields to
be updated, and it would iterate over every document matching the query (much
like a delete by query does now), pull the fields back, make a new document,
and post it.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
