You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "mosh (JIRA)" <ji...@apache.org> on 2019/04/10 05:17:00 UTC
[jira] [Comment Edited] (SOLR-12638) Support atomic updates of
nested/child documents for nested-enabled schema
[ https://issues.apache.org/jira/browse/SOLR-12638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814045#comment-16814045 ]
mosh edited comment on SOLR-12638 at 4/10/19 5:16 AM:
------------------------------------------------------
After inspecting the test results it seems like the only failure was due to [org.apache.solr.update.processor.CategoryRoutedAliasUpdateProcessorTest|https://builds.apache.org/job/PreCommit-SOLR-Build/367/testReport/org.apache.solr.update.processor/CategoryRoutedAliasUpdateProcessorTest/testSliceRouting/] reaching max GC overhead.
{code:java}
com.carrotsearch.randomizedtesting.UncaughtExceptionError: Captured an uncaught exception in thread: Thread[id=39740, name=Connection evictor, state=RUNNABLE, group=TGRP-CategoryRoutedAliasUpdateProcessorTest]
Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded{code}
This issue is probably unrelated to this patch, since SOLR-13370 was opened to address this issue.
[~dsmiley],
WDTY?
was (Author: moshebla):
After inspecting the test results it seems like the only failure was due to [org.apache.solr.update.processor.CategoryRoutedAliasUpdateProcessorTest.testSliceRouting|https://builds.apache.org/job/PreCommit-SOLR-Build/367/testReport/org.apache.solr.update.processor/CategoryRoutedAliasUpdateProcessorTest/testSliceRouting/] reaching max GC overhead.
{code:java}
com.carrotsearch.randomizedtesting.UncaughtExceptionError: Captured an uncaught exception in thread: Thread[id=39740, name=Connection evictor, state=RUNNABLE, group=TGRP-CategoryRoutedAliasUpdateProcessorTest]
Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded{code}
This issue is probably unrelated to this patch, since SOLR-13370 was opened to address this issue.
[~dsmiley],
WDTY?
> Support atomic updates of nested/child documents for nested-enabled schema
> --------------------------------------------------------------------------
>
> Key: SOLR-12638
> URL: https://issues.apache.org/jira/browse/SOLR-12638
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: mosh
> Assignee: David Smiley
> Priority: Major
> Attachments: SOLR-12638-delete-old-block-no-commit.patch, SOLR-12638-nocommit.patch, SOLR-12638.patch, SOLR-12638.patch
>
> Time Spent: 13h 50m
> Remaining Estimate: 0h
>
> I have been toying with the thought of using this transformer in conjunction with NestedUpdateProcessor and AtomicUpdate to allow SOLR to completely re-index the entire nested structure. This is just a thought, I am still thinking about implementation details. Hopefully I will be able to post a more concrete proposal soon.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org