Re: solr 7 optimize with Tlog/Pull replicas

Thanks Erick, it's very helpful. So for bulking indexing in a Tlog or Tlog/Pull cloud, when we optimize at the end of updates, segments on the leader replica will change rapidly and the follower replicas will be continuously pulling from the leader, effectively downloading the whole index. Is

Re: All replicas created on the same node

I think the attachment didn't get through. You may need to upload your attachment to a sharing site and share the link. Regards, Edwin On Wed, 13 Mar 2019 at 03:03, Tannen, Lev (USAEO) [Contractor] wrote: > I run the same url on both IE11 and Google Chrome. Attached are the left > panels of

Re: RegexReplaceProcessorFactory pattern to detect multiple \n

Hi, We have managed to resolve the issue, by changing the \s to \W. The reason could be due to that some of the spaces and white space instead of just a space. Using \s will only remove the spaces and not the white spaces, but using \W will remove the white spaces as well. We have used this

Re: Help with a DIH config file

Some addition: You can also strip HTML in DIH using the HTML Strip transformer: https://wiki.apache.org/solr/DataImportHandler#HTMLStripTransformer In that way you can probably live without a UpdateRequestProcessorChain On Tue, Mar 12, 2019 at 10:24 PM Jörn Franke wrote: > Would it be possible

Re: Help with a DIH config file

Would it be possible to share the DIH config file? I am not sure if I get all your points correctly. Ad 1) is this about a value in a field? Then use the regex transformer: https://wiki.apache.org/solr/DataImportHandler#RegexTransformer Alternatively, use a RegexReplaceProcessorFactoryin

RE: All replicas created on the same node

I run the same url on both IE11 and Google Chrome. Attached are the left panels of the screens. The right panel for IE11 is empty. -Original Message- From: Erick Erickson Sent: Tuesday, March 12, 2019 1:16 PM To: solr-user@lucene.apache.org Subject: Re: All replicas created on the

Help with a DIH config file

I have a previous post that looks like this: I am pulling a large amount of data from a local source D:\foo\resource\. I am using tika through a DIH to index the multiple file formats with text and metadata. I have almost all the information being pulled that I want, however, I am having a

Re: All replicas created on the same node

Could you add what parts didn’t work for you to: SOLR-12857? Thanks. > On Mar 12, 2019, at 8:09 AM, Tannen, Lev (USAEO) [Contractor] > wrote: > > Thank you Erick Erickson and Kevin Risden, > > I upgraded to 7.7.1 and the problem has disappeared. > > However: After upgrading, Solr admin in

streaming from /export sorts fields, /select does not

Hi! I've encountered something surprising in solr on the stream handler. When I use the expression: select( search(s2, q="author:"Florian Lindemann"", fl="id, author, title", sort="id desc", qt=/select), indexOf(author, "Florian Lindemann") as idx, author, title ) .. response (snippet)

Embedding XPathEntityProcessor inside TikaEntityProcessor

I am pulling a large amount of data from a local source D:\foo\resource\. I am using tika through a DIH to index the multiple file formats with text and metadata. I have almost all the information being pulled that I want, however, I am having a couple of issues: 1. I need to run a regex

RE: All replicas created on the same node

Thank you Erick Erickson and Kevin Risden, I upgraded to 7.7.1 and the problem has disappeared. However: After upgrading, Solr admin in IE11 stopped working correctly. I switched to Google Chrome and it works. -Original Message- From: Erick Erickson Sent: Friday, March 08, 2019

NPE deleting expired docs (SOLR-13281)

Has anyone else observed NPEs attempting to have expired docs removed? I'm seeing the following exceptions: 2019-02-28 04:06:34.849 ERROR (autoExpireDocs-30-thread-1) [ ] o.a.s.u.p.DocExpirationUpdateProcessorFactory Runtime error in periodic deletion of expired docs: null

7.7.1 FlattenGraphFilterFactory at query-time?

Hello, Due to reading 'This filter must be included on index-time analyzer..' in the documentation, i never considered adding it to a query-time analyser. However, we had problems with a set of three two-word synonyms never yielding the same number of results with SynonymGraph. When switching