[ 
https://issues.apache.org/jira/browse/SOLR-9530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998909#comment-15998909
 ] 

Steve Rowe commented on SOLR-9530:
----------------------------------

My Jenkins found a reproducing seed for several 
{{AtomicUpdateProcessorFactoryTest}} failures:

{noformat}
Checking out Revision 52b252cc6eddd7bcb71bdf2f9c533332fe228b0e 
(refs/remotes/origin/master)
[...]
   [junit4]   2> NOTE: reproduce with: ant test  
-Dtestcase=AtomicUpdateProcessorFactoryTest -Dtests.method=testBasics 
-Dtests.seed=9F9128B8E3E8FAA7 -Dtests.slow=true -Dtests.locale=th-TH 
-Dtests.timezone=US/Samoa -Dtests.asserts=true -Dtests.file.encoding=US-ASCII
   [junit4] ERROR   0.01s J11 | AtomicUpdateProcessorFactoryTest.testBasics <<<
   [junit4]    > Throwable #1: org.apache.solr.common.SolrException: Atomic 
document updates are not supported unless <updateLog/> is configured
   [junit4]    >        at 
__randomizedtesting.SeedInfo.seed([9F9128B8E3E8FAA7:A2498694DB06A4D7]:0)
   [junit4]    >        at 
org.apache.solr.update.processor.AtomicUpdateProcessorFactory.getInstance(AtomicUpdateProcessorFactory.java:88)
   [junit4]    >        at 
org.apache.solr.update.processor.AtomicUpdateProcessorFactoryTest.testBasics(AtomicUpdateProcessorFactoryTest.java:106)
[...]
   [junit4]   2> NOTE: reproduce with: ant test  
-Dtestcase=AtomicUpdateProcessorFactoryTest 
-Dtests.method=testWrongAtomicOpPassed -Dtests.seed=9F9128B8E3E8FAA7 
-Dtests.slow=true -Dtests.locale=th-TH -Dtests.timezone=US/Samoa 
-Dtests.asserts=true -Dtests.file.encoding=US-ASCII
   [junit4] FAILURE 0.00s J11 | 
AtomicUpdateProcessorFactoryTest.testWrongAtomicOpPassed <<<
   [junit4]    > Throwable #1: org.junit.ComparisonFailure: 
expected:<[Unexpected param(s) for AtomicUpdateProcessor, invalid atomic op 
passed: 'delete']> but was:<[Atomic document updates are not supported unless 
<updateLog/> is configured]>
   [junit4]    >        at 
__randomizedtesting.SeedInfo.seed([9F9128B8E3E8FAA7:4E887D44E42A13F4]:0)
   [junit4]    >        at 
org.apache.solr.update.processor.AtomicUpdateProcessorFactoryTest.testWrongAtomicOpPassed(AtomicUpdateProcessorFactoryTest.java:57)
[...]
   [junit4]   2> NOTE: reproduce with: ant test  
-Dtestcase=AtomicUpdateProcessorFactoryTest -Dtests.method=testMultipleThreads 
-Dtests.seed=9F9128B8E3E8FAA7 -Dtests.slow=true -Dtests.locale=th-TH 
-Dtests.timezone=US/Samoa -Dtests.asserts=true -Dtests.file.encoding=US-ASCII
   [junit4] ERROR   0.01s J11 | 
AtomicUpdateProcessorFactoryTest.testMultipleThreads <<<
   [junit4]    > Throwable #1: org.apache.solr.common.SolrException: Atomic 
document updates are not supported unless <updateLog/> is configured
   [junit4]    >        at 
__randomizedtesting.SeedInfo.seed([9F9128B8E3E8FAA7:B3A35F356F2C8C23]:0)
   [junit4]    >        at 
org.apache.solr.update.processor.AtomicUpdateProcessorFactory.getInstance(AtomicUpdateProcessorFactory.java:88)
   [junit4]    >        at 
org.apache.solr.update.processor.AtomicUpdateProcessorFactoryTest$1.run(AtomicUpdateProcessorFactoryTest.java:233)
   [junit4]    >        at 
org.apache.solr.update.processor.AtomicUpdateProcessorFactoryTest.testMultipleThreads(AtomicUpdateProcessorFactoryTest.java:240)
[...]
   [junit4]   2> NOTE: reproduce with: ant test  
-Dtestcase=AtomicUpdateProcessorFactoryTest -Dtests.method=testNoUniqueIdPassed 
-Dtests.seed=9F9128B8E3E8FAA7 -Dtests.slow=true -Dtests.locale=th-TH 
-Dtests.timezone=US/Samoa -Dtests.asserts=true -Dtests.file.encoding=US-ASCII
   [junit4] FAILURE 0.00s J11 | 
AtomicUpdateProcessorFactoryTest.testNoUniqueIdPassed <<<
   [junit4]    > Throwable #1: org.junit.ComparisonFailure: expected:<[Document 
passed with no unique field: 'id']> but was:<[Atomic document updates are not 
supported unless <updateLog/> is configured]>
   [junit4]    >        at 
__randomizedtesting.SeedInfo.seed([9F9128B8E3E8FAA7:62C4243917AB64F1]:0)
   [junit4]    >        at 
org.apache.solr.update.processor.AtomicUpdateProcessorFactoryTest.testNoUniqueIdPassed(AtomicUpdateProcessorFactoryTest.java:79)
[...]
   [junit4]   2> NOTE: test params are: 
codec=FastDecompressionCompressingStoredFields(storedFieldsFormat=CompressingStoredFieldsFormat(compressionMode=FAST_DECOMPRESSION,
 chunkSize=10, maxDocsPerChunk=8, blockSize=5), 
termVectorsFormat=CompressingTermVectorsFormat(compressionMode=FAST_DECOMPRESSION,
 chunkSize=10, blockSize=5)), sim=RandomSimilarity(queryNorm=true): {}, 
locale=th-TH, timezone=US/Samoa
   [junit4]   2> NOTE: Linux 4.1.0-custom2-amd64 amd64/Oracle Corporation 
1.8.0_77 (64-bit)/cpus=16,threads=1,free=238618688,total=523239424
{noformat}

> Add an Atomic Update Processor 
> -------------------------------
>
>                 Key: SOLR-9530
>                 URL: https://issues.apache.org/jira/browse/SOLR-9530
>             Project: Solr
>          Issue Type: New Feature
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Varun Thacker
>            Assignee: Noble Paul
>             Fix For: 6.6, master (7.0)
>
>         Attachments: assertU(...)-works.png, commit()-doesn't-work.png, 
> SOLR-9530.patch, SOLR-9530.patch, SOLR-9530.patch, SOLR-9530.patch, 
> SOLR-9530.patch, SOLR-9530.patch, SOLR-9530.patch, SOLR-9530.patch, 
> SOLR-9530.patch, SOLR-9530.patch, SOLR-9530.patch, SOLR-9530.patch, 
> SOLR-9530.patch
>
>
> I'd like to explore the idea of adding a new update processor to help ingest 
> partial updates.
> Example use-case - There are two datasets with a common id field. How can I 
> merge both of them at index time?
> So the first JSON dump could be ingested against 
> {{http://localhost:8983/solr/gettingstarted/update/json}}
> And then the second JSON could be ingested against
> {{http://localhost:8983/solr/gettingstarted/update/json?processor=atomic}}
> The Atomic Update Processor could support all the atomic update operations 
> currently supported.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to