solo source build in local error

solr-repo/lucene-solr/build.xml:21: The following error occurred while executing this line:/solr-repo/lucene-solr/lucene/common-build.xml:623: java.lang.NullPointerException at java.util.Arrays.stream(Arrays.java:5004) at java.util.stream.Stream.of(Stream.java:1000) at

solr 7.5.0 custom search component.

We are migrating solr5 to solr7.5. we have custom search component. the prepare() method called multiple times ( single node(one box) two shard) in solr 7.5. we assume that each shard it called one time. Due to that response builder are changed in prepare method so causing issue. But the same was

SOLR 7.5.0 (Migrate from 5.3.1 to 7.5.0)

We are migrating solr 5.3 to solr 7.5 after done, 2/12/2019, 11:22:37 AM WARN false x:test_shard20_replica_n38 SolrCore [test_shard20_replica_n38] PERFORMANCE WARNING: Overlapping onDeckSearchers=4 2/12/2019, 11:22:37 AM WARN false x:test_shard20_replica_n38 SolrCore [test_shard20_replica_n38]

Migrate from sol 5.3.1 to 7.5.0

We are migrating SOLR version, We used 3 ZK hosts that configured to SOLR as ZK connection string: zookeeper.solrtest.net:2181/test-config Ensemble size: 1 Ensemble mode: ensemble zookeeper.solrtest.net:2181 ok true clientPort 2181 zk_server_state follower zk_version 3.4.5

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

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: Migrate from sol 5.3.1 to 7.5.0

Hi Eric, Found the reason and all shard request to go /select flow solves the problem. Regarding In SOLR 7 when relevancy added for the search it is not working (not expected results) for the above fieldtype but same works fine for /select because it uses Lucene Parser but our flow uses

Re: Migrate from sol 5.3.1 to 7.5.0

Do we need to reindex if we change synonymQueryStyle values for a fieldType ? I hope not. -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

COLLECTION CREATE and CLUSTERSTATUS changes in SOLR 7.5.0

SOLR 7.5.0 Created collection as below: /admin/collections?action=CREATE=test_collection=1=1=replica:<2,node:*=test_collection_config Created Successfully. After that when I try to see CLUSTERSTATUS, it is giving "replicas": {} empty. But IN SOLR 5.3.1 it was giving the response but SOLR

Re: COLLECTION CREATE and CLUSTERSTATUS changes in SOLR 7.5.0

I found the reason, =true when I create a collection with this parameter I could find that replicas data in CLUSTERSTATUS api request,. is there anything wrong if I use this in SOLR 7.5.0 when create a collection ? Please advice. -- Sent from:

Re: COLLECTION CREATE and CLUSTERSTATUS changes in SOLR 7.5.0

Thanks a lot Erick, Shawn and Walter. As Shawn mentioned I should not use core admin API when in solrcloud, Just reloading collection solved the problem. -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: COLLECTION CREATE and CLUSTERSTATUS changes in SOLR 7.5.0

Thanks Eric, After we create a collection and copy the index from one place new place, we are doing UNLOAD core and CREATE core as below, is it wrong and we have alternative to do that ? r = requests.get('{}/admin/cores'.format(base_url), params={ 'action': 'UNLOAD', 'core':

Re: COLLECTION CREATE and CLUSTERSTATUS changes in SOLR 7.5.0

What is legacyCloud properties does. Is there a document I could refer. Why it impacts collection creation with rule based and index copy from one to another. Replicas not registered how to fix without legacyCloud=true settings. -- Sent from:

Re: Suggestion or recommendation for NRT

Even though same document indexed over and over again due to incremental update. Index size is being increased. Do I miss any configuration to make optimization occur by internally ? -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Suggestion or recommendation for NRT

Hi Team, Any suggestion or recommendation for the above approach which we are doing to have better search performance. -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Suggestion or recommendation for NRT

Thanks a lot for your time to respond for my clarifications. We are having two environment, ENV A and ENV B ( Both same capacity of RAM ( r5.2xlarge and same number of shards and replicas type (NRT) for the collection) ENV A - it is having a collection which is optimized ( segment count 1 and

Re: Suggestion or recommendation for NRT

Thanks Erick for the details and reference to understand better about merging segment stuff. When I compare performance of uninterrupted/optimized ( segment count 1) collection for search request vs (indexing + search) in parallel going on collection performance is 3 times higher, for example

Suggestion or recommendation for NRT

Hi, We are using SOLR 7.5.0 version, We are testing one collection for both Search and Index. Our collection created with below indexerconfig, We are using indexing process KAFKA connect plugin with every 5 min commit (cloud SOLRJ) as below https://github.com/jcustenborder/kafka-connect-solr