[
https://issues.apache.org/jira/browse/SOLR-7490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521907#comment-14521907
]
Praneeth commented on SOLR-7490:
--------------------------------
Thanks for the points. Its true that the all the document fields need to be
stored in order to implement this feature through atomic updates.
bq. could well result in a massive amount of work being done by Solr as the
result of a single call
Would this be significantly more work for Solr than what it does for
{{deleteByQuery}}?
I'm not very much familiar with working of DocValues and cannot at the moment
comment on doing it through updatable DocValues. I'll look further into it. As
you mentioned, optimistic locking is a primary concern here and could result in
a lot of work for Solr.
I think now I understand some of the primary concerns and I will look into
these areas and post back here.
> 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: [email protected]
For additional commands, e-mail: [email protected]
