[
https://issues.apache.org/jira/browse/SOLR-7490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14522198#comment-14522198
]
Praneeth commented on SOLR-7490:
--------------------------------
Ya but isn't update also effectively a mark for delete and then index the
document ? So, I thought it wouldn't cost much on the solr side to index a
stream of documents.
Considering a query that qualifies everything, Solr ends up re-importing the
whole data from itself which is basically an optimize operation I think, where
we end up rewriting the whole index? But it seems to make it easy to change the
schema without having to do anything after (basically change the schema and
issue an update by query qualifying the whole index) which basically supports
uptime re-indexing of a solr collection with new schema I guess.
With atomic updates, as you say, we will be exposing the freedom of updating a
huge set of documents in one request. We will be pushing Solr too much unless
it is used wisely.
> Update by query feature
> -----------------------
>
> Key: SOLR-7490
> URL: https://issues.apache.org/jira/browse/SOLR-7490
> Project: Solr
> Issue Type: New Feature
> Reporter: Praneeth
> Priority: Minor
>
> An update feature similar to the {{deleteByQuery}} would be very useful. Say,
> the user wants to update a field of all documents in the index that match a
> given criteria. I have encountered this use case in my project and it looks
> like it could be a useful first class solr/lucene feature. I want to check if
> this is something we would want to support in coming releases of Solr and
> Lucene, are there scenarios that will prevent us from doing this,
> feasibility, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
