rzo1 opened a new pull request, #2326:
URL: https://github.com/apache/stormcrawler/pull/2326

   Fixes #2304. A DISCOVERED tuple for a URL already in the `status` collection 
replaced its record, e.g. after a topology restart or once the status cache 
entry expired.
   
   - DISCOVERED documents are sent with `_version_ = -1`, so Solr only adds 
them if the URL is not there yet, as `create` does for OpenSearch
   - update requests carry `failOnVersionConflicts=false`, so a known URL does 
not fail the rest of the batch
   - tests for the URL client (4 shards) and the cloud client (2 shards); the 
cloud test classes now share one cluster
   
   ### For all changes
   
   - [x] Is there a issue associated with this PR? Is it referenced in the 
commit message?
   
   - [x] Does your PR title start with `#XXXX` where `XXXX` is the issue number 
you are trying to resolve?
   
   - [x] Has your PR been rebased against the latest commit within the target 
branch (typically main)?
   
   - [x] Is your initial contribution a single, squashed commit?
   
   - [x] Is the code properly formatted with `mvn git-code-format:format-code 
-Dgcf.globPattern="**/*" -Dskip.format.code=false`?
   
   ### For code changes
   
   - [ ] Have you ensured that the full suite of tests is executed via `mvn 
clean verify`? (ran the solr module)
   - [x] Have you written or updated unit tests to verify your changes?
   - [x] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [x] If applicable, have you updated the LICENSE file, including the main 
LICENSE file?
   - [x] If applicable, have you updated the NOTICE file, including the main 
NOTICE file?
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to