I have the same problem in my Solr8. I think it's because in the first way, TrimFieldUpdateProcessorFactory and RemoveBlankFieldUpdateProcessorFactory is not taking effect.
On SolrCloud, TrimFieldUpdateProcessorFactory, RemoveBlankFieldUpdateProcessorFactory and other processors only run on the first node that receives an update request. Consequently, it's necessary to execute TrimFieldUpdateProcessorFactory and RemoveBlankFieldUpdateProcessorFactory after giving the document to the replica node using the DistributedUpdateProcessor, so we need to use the second way that he described otherwise it won't operate properly. But even with this way, both I and he are worried whether it will be cause of SOLR-8030. I also want to know about this, does anyone have any comment about this? Best, Issei 2020年7月17日(金) 18:34 Jörn Franke <jornfra...@gmail.com>: > What does „not work correctly mean“? > > Have you checked that all fields are stored or doc values? > > > Am 17.07.2020 um 11:26 schrieb yo tomi <yosshii0...@gmail.com>: > > > > Hi All > > > > Sorry, above settings are contrary with each other. > > Actually, following setting does not work properly. > > --- > > <updateRequestProcessorChain name="skip-empty"> > > <processor class="TrimFieldUpdateProcessorFactory" /> > > <processor class="RemoveBlankFieldUpdateProcessorFactory" /> > > <processor class="solr.LogUpdateProcessorFactory" /> > > <processor class="solr.RunUpdateProcessorFactory" /> > > </updateRequestProcessorChain> > > --- > > And follows is working as expected. > > --- > > <updateRequestProcessorChain name="skip-empty"> > > <processor class="solr.DistributedUpdateProcessorFactory"/> > > <processor class="TrimFieldUpdateProcessorFactory" /> > > <processor class="RemoveBlankFieldUpdateProcessorFactory" /> > > <processor class="solr.LogUpdateProcessorFactory" /> > > <processor class="solr.RunUpdateProcessorFactory" /> > > </updateRequestProcessorChain> > > --- > > > > Thanks, > > Yoshiaki > > > > > > 2020年7月17日(金) 16:32 yo tomi <yosshii0...@gmail.com>: > > > >> Hi, All > >> When I did AtomicUpdate on SolrCloud by the following setting, it does > not work properly. > >> > >> --- > >> <updateRequestProcessorChain name="skip-empty"> > >> <processor class="solr.DistributedUpdateProcessorFactory"/> > >> <processor class="TrimFieldUpdateProcessorFactory" /> > >> <processor class="RemoveBlankFieldUpdateProcessorFactory" /> > >> <processor class="solr.LogUpdateProcessorFactory" /> > >> <processor class="solr.RunUpdateProcessorFactory" /> > >> </updateRequestProcessorChain> > >> --- > >> When changed as follows and made it work, it became as expected. > >> --- > >> <updateRequestProcessorChain name="skip-empty"> > >> <processor class="TrimFieldUpdateProcessorFactory" /> > >> <processor class="RemoveBlankFieldUpdateProcessorFactory" /> > >> <processor class="solr.LogUpdateProcessorFactory" /> > >> <processor class="solr.RunUpdateProcessorFactory" /> > >> </updateRequestProcessorChain> > >> --- > >> The later setting and the way of using post-processor could make the > same result, I though, > >> but using post-processor, bug of SOLR-8030 makes me not feel like using > it. > >> By the latter setting even, is there any possibility of SOLR-8030 to > become? Seeing the source code, tlog which is from leader comes to Replica > seems to be processed correctly with UpdateRequestProcessor, > >> the latter setting had not been the right one for the bug, I > though.Anyone knows the most appropriate way to configure AtomicUpdate on > SolrCloud? > >> > >> Thanks, > >> Yoshiaki > >> > >> >
