[
https://issues.apache.org/jira/browse/SOLR-14868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17196565#comment-17196565
]
Chris M. Hostetter commented on SOLR-14868:
-------------------------------------------
Note that "delete by query" can be used as a work around to more efficiently
delete some nested documents (w/o complete re-indexing the root document) but...
* delete by query has it's own perf bottlenecks (distributed lock across all
shards)
* this exposes SOLR-14869
> nested document 'remove' operation should "delete in place"
> -----------------------------------------------------------
>
> Key: SOLR-14868
> URL: https://issues.apache.org/jira/browse/SOLR-14868
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Chris M. Hostetter
> Priority: Major
>
> Currently, if you use the "remove" atomic update operation for nested
> documents, it completely re-indexes the "root" document and all remaining
> child documents (after logically removing the specified child and i'ts
> descendants)
> ideally, unless this operation is combined with other atomic update
> operations, "remove" should be done "in place" -- just using the IndexWriter
> to mark the specified child document (and it's descendants) as deleted.
> (The full Re-Indexing of the 'root' level document can be very slow for large
> deeply nested documents)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
