I have updated the apache2 version form apache2.2.14 to apache2.4.7 and also apache-solr package form 1.4.x to 4.x.
Before upgradation, I have indexed all the content.
After upgradation, in apache configuration it showing 0% indexed.
is there any way to use old indexing?
Solr / Lucene only upgrades older index formats in smaller increments, so you'll have to at least stop by a 3.x release on the way to be able to use the 1.4 index formats.
I'd also recommend going from 4 to 5 as well, since you're already doing the upgrade now, and will be stuck in the past again if you don't do the 5.x upgrade as well (6.0 was just released).
My suggestion is to optimize for easy reindexing, and do that. You'll run into the same issue later, or after doing any major changes to your schema.
The index format is backward compatible between two consecutive major
Solr versions. So a Solr 3.x index is compatible with a Solr 4.x
index. However if you have a Solr 1.x index and want to upgrade to
Solr 4.x then you would need to first upgrade to Solr 3.x first.
upgrade between major Solr Versions
So you'll have to go via 3.x (as Mats says below) or reindex or use the IndexUpgrader tool on your index.
http://lucene.apache.org/core/4_0_0/core/org/apache/lucene/index/IndexUpgrader.html
Related
I have hazelcast version 3.8.3. I want to enable rest api.
I wrote in the config:
The rest-api section was added in 3.12, you're using 3.8.
An upgrade should sort it.
The latest Hazelcast 3 series is 3.12.9, but it's still old.
Current Hazelcast is Hazelcast 5. If you can upgrade, going to 5.1.1 would be better, the very latest (as of time of writing) -- even faster, more features, etc.
I want to migrate a shopware with shopware 3.5.4 version to shopware 5 version, but I cannot update it. I'm also trying to transfer its contents and theme to shopware 5, which I just installed. Is there a short way I can do this
There isn't any short way.
You must update to some intermediate version.
If you made it to version 4.2 you can update in these steps:
4.2
5.1.6
5.6.10
5.7.6
See also the shopware 5 changelog
In the shopware github repository, you can find all versions since 4.0.1 as tags.
As most old versions of shopware (at least the ones I got to know) are pretty "tinkered", the easy way moving to recent shopware is:
Copy database and local files to a supporting host (keep in mind that you will need older versions of PHP)
Disable (better uninstall) every plugin and theme, switch to default theme
Upgrade to SW4, then upgrade to recent version of shopware 5 by following this guide strictly https://docs.shopware.com/de/shopware-5-de/update-guides
Use import/export tool to export all product and order data
You might as well succeed by skipping step 3, applying all db-migrations, and using the db with your fresh installation, but I guess you will run into trouble with your media files (images etc. might not be usable anymore).
Another way might be writing a small script to export all data to csv and import it with the native tool.
There is no way (that I know of) to make your old theme working in recent versions of SW5. Before creating a new one, keep in mind SW5 will quite soon be EOL, and SW6 is much faster and way ahead in usability. You could use SW6's import functions to move from SW5 to the recent release.
I am just starting a student project for a lesson based on apache lucene and the data that i am going to process with this tool is critics about restaurants from yelp.
What version do you recommend as the most stable for this purpose?
I think that if you are starting from scratch there's no reason to use an old version. Use the latest version (8.0). Lucene releases are always very stable in my experience.
Based on this question I have managed to successfully integrate Nutch and Elasticsearch, albeit by downgrading my Elasticsearch version. How can I modify the Nutch source code to accommodate the latest version of Elasticsearch (0.90.2+)? I have tried modifying the Ivy dependency to this version of Elasticsearch and also modified Nutch's Elasticsearch compatibility code so it would build properly, but I end up with an error as Nutch times out waiting for a response from Elasticsearch; the two are unable to communicate.
I think I found the solution. You need to modify all references to the version number, both in ivy/ivy.xml and pom.xml (which is the file I forgot to change). Changing both 0.19.4s to 0.90.2s should do the trick. Also, you need to change item.failed() in src/java/org/apache/nutch/indexer/elastic/ElasticWriter.java to item.isFailed() to match the newer Elasticsearch refactoring.
My runtime environment is still on JDK1.4 but I like the Solr features related to how documents are ingested and indexed. Would I be able to index my documents using Solr offline on a recent version of the JDK, copy the index over and use it in my runtime environment with an older version of the JDK?
Version wise, Solr 1.4.0 uses Apache Lucene 2.9.1 which is JDK1.4 compatible. (but Solr itself requires JDK5).
Assuming what I'm trying to do is even possible, what features would I lose if I search Solr indices only with the Lucene API?
Yes, the Solr index is a standard Lucene index which you can open with "raw" Lucene, however you would lose all the features that Solr does for you, like faceting, caching, highlighting, etc.