[
https://issues.apache.org/jira/browse/SOLR-8586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-8586:
-------------------------------
Attachment: SOLR-8586.patch
Here's an updated patch that implements fingerprinting on the request side.
Example:
{code}
$curl
"http://localhost:8983/solr/techproducts/get?getVersions=5&fingerprint=true";
{
"versions":[1524634308552163328,
1524634308550066176,
1524634308544823296,
1524634308538531840,
1524634308533288960],
"fingerprint":{
"maxVersionSpecified":9223372036854775807,
"maxVersionEncountered":1524634308552163328,
"maxInHash":1524634308552163328,
"versionsHash":1830505675324363667,
"numVersions":32,
"numDocs":32,
"maxDoc":32}}
{code}
> Implement hash over all documents to check for shard synchronization
> --------------------------------------------------------------------
>
> Key: SOLR-8586
> URL: https://issues.apache.org/jira/browse/SOLR-8586
> Project: Solr
> Issue Type: Improvement
> Reporter: Yonik Seeley
> Attachments: SOLR-8586.patch, SOLR-8586.patch
>
>
> An order-independent hash across all of the versions in the index should
> suffice. The hash itself is pretty easy, but we need to figure out
> when/where to do this check (for example, I think PeerSync is currently used
> in multiple contexts and this check would perhaps not be appropriate for all
> PeerSync calls?)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
