[jira] [Updated] (SOLR-6909) Allow pluggable atomic update merging logic
[ https://issues.apache.org/jira/browse/SOLR-6909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Davids updated SOLR-6909: --- Attachment: SOLR-6909.patch Updated patch to add a 'doSet' and 'doAdd' method which allows clients to override specific implementations of any atomic update command. Allow pluggable atomic update merging logic --- Key: SOLR-6909 URL: https://issues.apache.org/jira/browse/SOLR-6909 Project: Solr Issue Type: Improvement Reporter: Steve Davids Fix For: 5.0, Trunk Attachments: SOLR-6909.patch, SOLR-6909.patch Clients should be able to introduce their own specific merging logic by implementing a new class that will be used by the DistributedUpdateProcessor. This is particularly useful if you require a custom hook to interrogate the incoming document with the document that is already resident in the index as there isn't the ability to perform that operation nor can you currently extend the DistributedUpdateProcessor to provide the modifications. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-6909) Allow pluggable atomic update merging logic
[ https://issues.apache.org/jira/browse/SOLR-6909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Davids updated SOLR-6909: --- Attachment: SOLR-6909.patch Attached a patch which pulls the current merging implementation out from the DistributedUpdateProcessor into a new AtomicUpdateDocumentMerger class. This DistributedUpdateProcessorFactory instantiates a new AtomicUpdateDocumentMerger and passes it to the DistributedUpdateProcessor. This approach allows clients to extend the DistributedUpdateProcessorFactory and instantiate their own custom AtomicUpdateDocumentMerger which is then passed along to the DistributedUpdateProcessor. One thing that I'm not thrilled about is having a static 'isAtomicUpdate' method (currently in the code), I tried to remove the static but a couple other classes require that static method to be there and having a merger member variable didn't quite make sense in those cases so I left it a static. Allow pluggable atomic update merging logic --- Key: SOLR-6909 URL: https://issues.apache.org/jira/browse/SOLR-6909 Project: Solr Issue Type: Improvement Reporter: Steve Davids Fix For: 5.0, Trunk Attachments: SOLR-6909.patch Clients should be able to introduce their own specific merging logic by implementing a new class that will be used by the DistributedUpdateProcessor. This is particularly useful if you require a custom hook to interrogate the incoming document with the document that is already resident in the index as there isn't the ability to perform that operation nor can you currently extend the DistributedUpdateProcessor to provide the modifications. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
