Re: Help for importing large data (approx. 8GB) from old solr version to new solr version

2019-12-24 Thread Ken Walker
Hello Erick, Thanks for your reply! You mean that, we should follow below steps right? Here is the data directory path : solr/solr-8.2.0/server/solr/product/item_core/data STEPS :- 1. Stop old solr-8.2.0 server 2. Copy data directory (from old solr version to new solr version) copy solr/solr-8.2

Re: does copyFields increase indexe size ?

2019-12-24 Thread Shawn Heisey
On 12/24/2019 5:11 PM, Nicolas Paris wrote: Do you mean "copy fields" is only an action of changing the schema ? I was thinking it was adding a new field and eventually a new index to the collection The copy that copyField does happens at index time. Reindexing is required after changing the

Re: does copyFields increase indexe size ?

2019-12-24 Thread Nicolas Paris
> The action of changing the schema makes zero changes in the index. It > merely changes how Solr interacts with the index. Do you mean "copy fields" is only an action of changing the schema ? I was thinking it was adding a new field and eventually a new index to the collection On Tue, Dec 24, 2

Cache fails to warm after Replication Recovery in solr cloud

2019-12-24 Thread Cao, Li
Hi! I have some custom cache set up in solrconfig XML for a solr cloud cluster in Kubernetes. Each node has Kubernetes persistence set up. After I execute a “delete pod” command to restart a node it goes into Replication Recovery successfully but my custom cache’s warm() method never gets calle

Re: does copyFields increase indexe size ?

2019-12-24 Thread Shawn Heisey
On 12/24/2019 10:45 AM, Nicolas Paris wrote: From my understanding, copy fields creates an new indexes from the copied fields. From my tests, I copied 1k textual fields into _text_ with copyFields. As a result there is no increase in the size of the collection. All the source fields are indexed

does copyFields increase indexe size ?

2019-12-24 Thread Nicolas Paris
Hi >From my understanding, copy fields creates an new indexes from the copied fields. >From my tests, I copied 1k textual fields into _text_ with copyFields. As a result there is no increase in the size of the collection. All the source fields are indexed and stored. The _text_ field is indexed bu

Re: Help for importing large data (approx. 8GB) from old solr version to new solr version

2019-12-24 Thread Erick Erickson
Here’s the very simplest way: 1> shut down your 8.2 Solr instance 2> install your 8.3.1 instance on the same machine 3> when you start your 8.3.1 instance, specify the environment variable SOLR_HOME to point to the same one you used in 8.2 If you don’t know what SOLR_HOME used to point to, bring

Re: Help for importing large data (approx. 8GB) from old solr version to new solr version

2019-12-24 Thread Ken Walker
Hello Jörn, Thanks for your reply! As per Shawn "Why not just copy the index and use it directly rather than importing it? Solr 8.x can directly use indexes built by versions back to 7.0.0." in previous mail comment. Is it possible and how we can do that ? Thanks in advance - Ken On Tue, Dec

Re: Help for importing large data (approx. 8GB) from old solr version to new solr version

2019-12-24 Thread Jörn Franke
It seems that you got this handed over with little documentation. You have to explore what the import handler does. This is a custom configuration that you need to check how it works. Then as already said. You can simply install another version of Solr if you are within a Solr major version 8.x

can you help me?

2019-12-24 Thread Jie ant
Highlight, display when the query ID is available Change to title. The return value of highlighting is only the ID information, and the content is empty

Re: Help for importing large data (approx. 8GB) from old solr version to new solr version

2019-12-24 Thread Ken Walker
Hello Shawn, Thanks for your reply! Actually we don't know how its works ( just copy the index ) so could you please give us some reference urls or any steps for it? Thanks in advance - Ken On Tue, Dec 24, 2019 at 11:56 AM Shawn Heisey wrote: > > On 12/23/2019 9:58 PM, Ken Walker wrote: > > We