RE: Solr Index Size after reindex

Hello Andrea, I'm really sorry for the delay of my answer but I beed more information before answer you. Yes 5.365.213 is the numDocs you got just after the sync and yes 4.537.651 is the numDocs you got in the staging server after the reindexing and the colleague who realized the rsync confirm

Re: Migrate from sol 5.3.1 to 7.5.0

Thanks Erick, I was waiting your Day time appears to get suggestion because you are very spontaneous for this great open source community. 1. Did you recompile and redistriburte your custom component? * Yes* 2. Did you take the solrconfig that came with 7.5 and modify it rather than copy you

Re: Migrate from sol 5.3.1 to 7.5.0

Thanks Jan, I am unaware how our Devops team decided this But this was working well without any issues with SOLR 5.3.1 for couple of years. Just wanted to make any changes in SOLR7 mandates . -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

RE: Multiplicative Boosts broken since 7.3 (LUCENE-8099)

I like to bump this issue up, since this is a showstopper for us to upgrade from Solr 6. In https://issues.apache.org/jira/browse/SOLR-13126 I described a couple of more use cases in which this bug appears. We see different scores in the EXPLAIN compared to the actual scores and our analysis is

Re: Incorrect shard placement during Collection creation in 7.6

I haven't verified, but this looks like a JIRA to me. Looks like some of the create logic may have issues, see: SOLR-12944 and maybe link to that JIRA? Best, Erick On Wed, Feb 13, 2019 at 4:15 AM Bram Van Dam wrote: > > > TL;DR; createNodeSet & shards combination is not being respected. > > Upda

Re: misteriuos nullpointerexception while adding documents

bq. I also tried with a plain solr installation (just unpack solr and copy the index folder), and in this way it works. Then it sounds like your production system was not installed properly if it mysteriously fails there but succeeds on a new install. If you upgraded your prod system, did you use

Re: SOLR 7.5.0 (Migrate from 5.3.1 to 7.5.0)

On 2/12/2019 9:25 PM, ramyogi wrote: [test_shard20_replica_n38] PERFORMANCE WARNING: Overlapping onDeckSearchers=6 2/12/2019, 1:45:39 PM WARN true x:test_shard20_replica_n38 DirectUpdateHandler2 Starting optimize... Reading and rewriting the entire index! Use with care. Eventhough index is optim

Re: Migrate from sol 5.3.1 to 7.5.0

1. Did you recompile and redistriburte your custom component? 2. Did you take the solrconfig that came with 7.5 and modify it rather than copy your 5.3 solrconfig? 3. Did you reindex from scratch with 7x? Lucene/Solr guarantees only one major version back-compat. Best, Erick On Wed, Feb 13, 2019

NYC Apache Lucene/Solr User Group: Call for Speakers

Hello, everyone! The New York Apache Lucene/Solr User Group is, for the first time, sending out a call for speakers for 2019/20. We have a great line up of speakers for this year, but we also want to hear more from the community. Now that we

Re: Get details about server-side errors

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jason, On 2/13/19 07:39, Jason Gerlowski wrote: > Hey Chris, > > Unfortunately I think you covered the main/only options above. > > HTTP status code isn't the most useful, but it's worth pointing > out that there are a few things you can do with i

Re: Migrate from sol 5.3.1 to 7.5.0

You need to list all zk hosts in zkHost, that’s part of the design for ZK, clients will open connections to all nodes and be able to fail over if trouble. Where did you get the CNAME advice? Jan Høydahl > 13. feb. 2019 kl. 05:56 skrev ramyogi : > > We are migrating SOLR version, We used 3 ZK h

Re: What's the deal with dataimporthandler overwriting indexes?

Thank you all for helping me with this. I have started implementing aliases and that seems like the proper way to go. Thanks again and all the best! Den tis 12 feb. 2019 kl 18:16 skrev Elizabeth Haubert < ehaub...@opensourceconnections.com>: > I've run into this also; it is a key difference bet

Re: Terms Query Parser: filtering on null and strings with whitespace.

Oh yeah, my pet peeve. This is the cure. (*:* AND -department_name:[* TO *]) OR {!tag=department_name terms f=department_name v='Kirurgisk avdeling'} no comments. On Wed, Feb 13, 2019 at 1:49 PM Andreas Lønes wrote: > I am experiencing some weird behaviour when using terms query parser where > I

Re: SOLR and AWS comprehend

I guess you have to find out which product fits better your needs. The use case can be somehow reflected in both solutions, but the description about the use case is very generic so difficult to say. > Am 13.02.2019 um 13:17 schrieb Gareth Baxendale : > > This is perhaps more or an architecture

Re: Get details about server-side errors

Hey Chris, Unfortunately I think you covered the main/only options above. HTTP status code isn't the most useful, but it's worth pointing out that there are a few things you can do with it. Some status codes are easy to identify and come up with a good message to display to your end user e.g. 40

SOLR and AWS comprehend

This is perhaps more or an architecture question than dev code but appreciate collective thoughts! We are using Solr to order records and to categorise them to allow users to search and find specific medical conditions. We have an opportunity to make use of Machine Learning to aid and improve the

Re: Incorrect shard placement during Collection creation in 7.6

> TL;DR; createNodeSet & shards combination is not being respected. Update: Upgraded to 7.7, no improvement sadly.

RE: Document Score seen in debug section and in main results section dont match

Hi Baloo, > Is there and solution/workaround available for this issue? > or going back to Solr 7.2.1 is the only solution - As per comments in above > issue (https://issues.apache.org/jira/browse/LUCENE-8099 these changes are > not there in 7.2.1) The only workaround, I know of, is building SOLR

RE: Document Score seen in debug section and in main results section dont match

Hi Erick, > You are saying that "X" doesn't work, in this case the scores are different > in the debug section. But this implies that there is a problem "Y" that > you're having. The issue is not that they don't match, the issue is that the calculated score is wrong. The debug score shows eve

Re: Delete by id

Hi Dwane, The error suggests that Solr is trying to add a document, rather than delete one, and is complaining that the DOC_ID is missing. I tried each of your examples (without the smart quotes), and they all worked as expected, both from curl and the admin UI. There's an error in your long

Re: misteriuos nullpointerexception while adding documents

I changed the schema, but I deleted all the documents and tried a reindex. I also tried deleting the core and re-adding it. The autocommit is disabled because hard commits are controlled in the client-side. I also tried with a plain solr installation (just unpack solr and copy the index fold

Terms Query Parser: filtering on null and strings with whitespace.

I am experiencing some weird behaviour when using terms query parser where I am filtering on documents that has no value for a given field(null) and strings with whitespaces. I can filter on documents not having a value OR having some specific values for the field as long as the value does not

Incorrect shard placement during Collection creation in 7.6

Hey folks, TL;DR; createNodeSet & shards combination is not being respected. I'm attempting to create a collection with multiple shards, but apparently the value of createNodeSet is not being respected and shards are being assigned to nodes seemingly at random. createNodeSet.shuffle is set to fa