Re: Solr 8.5.1 Using Port 10001 doesn't work in Dashboard

Unless someone knows something concrete, I am going to move forward and assume that it is Google Chrome. Thank you Sylvain. > On May 1, 2020, at 3:42 PM, Sylvain James > wrote: > > Hi Phil, > > I encountered something similar recently, and after switched to

Re: Solr 8.5.1 Using Port 10001 doesn't work in Dashboard

Hi Phil, I encountered something similar recently, and after switched to Firefox, all urls were fine. May be a encoding side effect. It seems to me that a new solr ui is in development. May be this issue will be fixed for the release of this ui. Sylvain Le ven. 1 mai 2020 à 22:52, Phill

RE: Possible issue with Stemming and nouns ended with suffix 'ion'

I tried KStem but some other scenarios were broken, so I reverted id. However, it might have happened for some misconfiguration. I will try that once more. Thanks. Jhonny Lopez Technical Architect Avenida Calle 26 No. 92 - 32, Edificio BTS3 APDO. 128-1255 Bogota T: +57 300 6805461

Re: Solr 8.5.1 Using Port 10001 doesn't work in Dashboard

The browser is Chrome. I forgot to state that before. That got me to thinking and so I ran it from Fire Fox. Everything seems to be fine there! Interesting. Since this is my development environment I do not run any plugins on any of my browsers. > On May 1, 2020, at 2:41 PM, Phill Campbell >

Solr 8.5.1 Using Port 10001 doesn't work in Dashboard

Today I installed Solr 8.5.1 to replace an 8.2.0 installation. It is a clean install, not a migration, there was no data that I needed to keep. I run Solr (Solr Cloud Mode) on ports starting with 10001. I have been doing this since Solr 5x releases. In my experiment I have 1 shard with

RE: Indexing Korean

Hello, Although it is not mentioned in Solr's language analysis page in the manual, Lucene has had support for Korean for quite a while now. https://lucene.apache.org/core/8_5_0/analyzers-nori/index.html Regards, Markus -Original message- > From:Audrey Lorberfeld -

Re: Possible issue with Stemming and nouns ended with suffix 'ion'

The Porter/Snowball stemmer is an evolved version of a forty year old hack. It is neat that it works at all, but don’t expect too much. I think it is too aggressive for search use. What does KStem do with this? That is based on better linguistic models. wunder Walter Underwood

Re: Possible issue with Stemming and nouns ended with suffix 'ion'

This is how things get stemmed *now*, but I believe there is an open question as to whether that is how they *should* be stemmed. Specifically, the case appears to be -ify words not stemming to the same as -ification - this applies to much more than identify/identification. Also, justify, fortify,

RE: Possible issue with Stemming and nouns ended with suffix 'ion'

Unless I'm misunderstanding the bug in question, there is no bug. What you are observing is simply just how things get stemmed... Best, Audrey On 4/30/20, 6:37 PM, "Jhonny Lopez" wrote: Yes, sounds like worth it. Thanks guys! -Original Message- From: Mike

Indexing Korean

Hi All, My team would like to index Korean, but it looks like Solr OOTB does not have explicit support for Korean. If any of you have schema pipelines you could share for your Korean documents, I would love to see them! I'm assuming I would just use some combination of the OOTB CJK

Re: Possible issue with Stemming and nouns ended with suffix 'ion'

Jhonny, Are you planning on reporting the issue to snowball, or would you prefer one of us take care of it? If you do report it, please share the link to the issue or mail archive back here so that we know when it is resolved and can update our dependencies. Thanks, Mike On Thu, Apr 30, 2020 at

Re: SolrCloud degraded during backup and batch CSV update

If the errors happen with garbage collection then potentially, yes. You should never pause longer than your zk timeout (both sides). On Thu, Apr 30, 2020 at 11:03 PM Ganesh Sethuraman wrote: > > Any other JVM settings change possible? > > On Tue, Apr 28, 2020, 10:15 PM Sethuraman, Ganesh >

Re: off-heap OOM

I don't know exactly, but couldn't it hit host-wide threads limit limitation? On Fri, May 1, 2020 at 11:02 AM Raji N wrote: > Thanks for your reply . Sure will take a look at the docker host log. But > even when we got "unable to create new native thread" error , the heap dump > taken within

Re: Use TopicStream as percolator

Great! I ran Flax, where we created Luwak, up to last year when we merged with OSC, so this is great to see. Did you know we donated Luwak to Lucene recently? https://issues.apache.org/jira/browse/LUCENE-8766 It would be great to work this up into a Solr contrib module Charlie .. Berlin

Re: Use TopicStream as percolator

Hi everyone, I wrote SOLR Update Processor that wraps Luwak library and implements Saved Searches a la ElasticSearch Percolator. https://github.com/SOLR4189/solcolator for anyone who wants to use. -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html

How to use percentage in collection specific policy

Hello, I was trying to use a collection specific policy with sysprop and percentage for replica { "set-policy": { "generalpolicy": [ { "replica": "33%", "shard": "#EACH", "sysprop.key": "general" } ]

Re: off-heap OOM

Thanks for your reply . Sure will take a look at the docker host log. But even when we got "unable to create new native thread" error , the heap dump taken within hour before (we have hourly heap generation) the OOM did not have more than 150 to 160 threads. So it doesn't look like it happens

Re: off-heap OOM

> java.lang.OutOfMemoryError: unable to create new native thread Usually mean code flaw, but there is a workaround to trigger heap GC. It happens when app creates threads instead of proper pooling, and no GC occurs, so java Thread objects hangs in heap in stopped state, but every of them holds a