Can any one tell me liferay 6.1.2 ce ga3 on tomcat 7 and solr 4.6 on tomcat 7 are compatible?
Used the solr web portlet avaible from liferay market.
I am working on this from last 3 days and i am still getting version issues,executing query issues ,SolrCore 'collection1' is not available issues, CommonsHTTPSolrServer even after following lot of suggestion.
I tried all permutation regarding the jars.
slf4j-api-1.6.6
slf4j-log4j12-1.6.6
slf4j-simple-1.6.6
solr-common-1.3.0
solr-core-4.6.0
solr-solrj-4.6.0
httpclient-4.3.1
httpcore-4.3
httpmime-4.3.1
I also raised this issue on liferay support forum : https://issues.liferay.com/browse/LPS-42758
No they are not compatible (out of the box).
But it is doable, at least it is with Solr 4.4.0 and 4.5.1, so I would guess with Solr 4.6.0 also.
General steps to make it work:
solr-web
download latest solr-web plugin (source) for 6.1.x
modify dependacies (see below)
modify source files (resolve compilation errors)
modify solr-spring.xml (if needed)
modify schema.xml (look at both liferay's and solr version, and "merge" (what makes sense) them)
List of jars
commons-codec-1.6.jar
commons-io-2.1.jar
httpclient-4.2.3.jar
httpcore-4.2.2.jar
httpmime-4.2.3.jar
noggit-0.5.jar
portal-compat-shared.jar
slf4j-api-1.6.1.jar
solr-solrj-4.5.1.jar
wstx-asl-3.2.7.jar
zookeeper-3.4.5.jar (probably could be removed, I did not)
Additional (provided) jars not packaged in war
portal-service-6.1.1.jar
util-java-6.1.1.jar
servlet-api-2.5.jar
Specifically for CommonsHTTPSolrServer ClassNotFoundException
in BasicAuthSolrServer constructor you should use HttpSolrServer, instead of CommonsHTTPSolrServer
Related
I have a problem with an old TYPO3 installation (TYPO3 site 7 LTS [7.6.9]).
The site is using Apache Solr as the search engine, but it's not working. When a user tries to search, the system shows a message telling that the search engine is not available now.
In the administration panel, if I go to the Search option, I see this message:
Unable to contact your Apache Solr server.
Hosts missing:http://localhost:8080/solr/core_es/
http://localhost:8080/solr/core_eu/
http://localhost:8080/solr/core_en/
Of course, I have checked that Solr is running and listening on the port 8080. The Solr server is on the same machine than TYPO3.
I found this link about the Apache Solr configuration, but I cannot find these administration pages. I would like to test with the machine's public IP. In fact, I changed all the records regarding Solr in the cf_tx_solr_configuration table, and cleared all the cache tables manually, with no effect.
I have a couple of questions here:
Is it possible to change the configuration of the Solr server in TYPO3? If so, how can I do that?
Is TYPO3 shipped with an out-of-the-box search feature? If so, how can I disable Apache Solr and use the default search engine?
Thanks so much in advance!
please consume appropriate documentation Version of installed Extension.
So I assume(see Version Matix) you are using EXT:Solr version 6.5, therefore you must use the documentation for EXT:Solr v. 6.5.
--
QA
Is it possible to change the configuration of the Solr server in TYPO3? If so, how can I do that?
Yes, it is. You can set it via TypoScript path "plugin.tx_solr.solr.scheme|host|port|..."
Is TYPO3 shipped with an out-of-the-box search feature? If so, how can I disable Apache Solr and use the default search engine?
Yes, TYPO3 has build in search feature. Its name is indexed_search.
PS: You know, there are much more modern versions of TYPO3 available? Please upgrade at least to the newer major release.
Is it necessary to use tomcat for configuring Solr with asp.net.
by this link [link]https://www.codeproject.com/Tips/480091/Using-Solr-for-Search-with-NET-Csharp
i configured and it works!! but it uses solr 1.4 version and i want to update my solr version.
And [link]https://cwiki.apache.org/confluence/display/solr/Running+Solr+on+Tomcat
it says that you cannot configure the tomcat with version 5 or latest from it.
so how to configure asp.net with solr latest version ?
Latest Solr runs as standalone black box. Do not look at ancient tutorials for Tomcat information, they are not useful anymore. And it is a separate issue from connecting to it via .NET client.
For the client part, the source-code version of SolrNet is more up to date. And it should work with latest Solr, with the main issue being that the URL for Solr now must include collection name, so http://localhost:8983/solr/collectionname . Check for parameters to set core or collection or similar.
There is also Solr Express you may want to have a look at.
As you may already know that Sitecore, configured to work with SolrCloud, does not support index switch on rebuild. Is there a way to achieve this with version 4.10.3 of Solr and Sitecore 8.0?
We found a link - https://github.com/SitecoreSupport/Sitecore.Support.449298 - but this has only been tested from version 5.2.1 to 5.5.1. Does anyone have any experience implementing this for version 4.10.3? Any issues that we may need to be aware of?
Thanks
This patch was created as the old SwitchOnRebuild used the Solr Core switching API which is now deprecated in version 5.* and above. It was not recommended when running in SolrCloud mode due to an issue with Zookeeper.
This code uses the Solr 'collections' API (/solr/admin/collections?action=LIST) instead , you would need to check if this API is available for Solr 4.10 (I think it is but I'm not 100% sure)
You would then just need to ignore the parts about the schemaFactory as that is Solr 5.* specific.
Note that this patch relies on the 405677 patch to be applied too.
We are looking to upgrade from SolrCloud 4.10.3 to SolrCloud 6.1. The documentation for Solr 6.1 is not very clear on backward compatibility.
I came across this post on the LucidWorks site.
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.
It was written before Solr 6.x was out, and the wording of "between two consecutive major Solr versions" is unclear. The example skips the exact scenario that I'm interested in (skipping exactly 1 major version).
Do I have to first upgrade to Solr 5.x and then go to Solr 6.1?
Since I face same situation on upgrading SOLR from 4.x to 6.x I have been lucky and found on git hub next script, that is making the upgrade:
https://github.com/cominvent/solr-tools.git/
All the credits goes to "cominvent" for this script.
Since the folder cores vers 4.x structure is not same with version 6.x I have made a script that is creating the right tree configuration, then is applying upgradeindex.sh.
The script (buildsorltree.sh) can be found on https://github.com/cradules/bash_scripts and the repo dose have upgradeindex.sh too. Since I have linked this too scripts, I put them on same repo. Good luck!
I was able to find this on the Apache website.
Solr 6 has no support for reading Lucene/Solr 4.x and earlier indexes.
Be sure to run the Lucene IndexUpgrader included with Solr 5.5 if you
might still have old 4x formatted segments in your index.
Alternatively: fully optimize your index with Solr 5.5 to make sure it
consists only of one up-to-date index segment.
So this means that you can upgrade directly, but only if you run the IndexUpgrader from Solr 5.5 first.
In reference to my other SO question (Using solr 4.2 how do I use/enable fuzzy phrase searching)
I was told I can get fuzzy phrases working by installing the plugin mentioned there (https://issues.apache.org/jira/browse/SOLR-1604). However, with every attempt I've made I cannot get it to work. When I download the latest dated file, there is not readme or install directions. Also, I'm not entirely sure that there is a version for Solr 4.2 yet.
Can someone provide me with instructions on how to install that plugin with Solr 4.2?
I was just looking at this myself. According to another SO question (https://stackoverflow.com/a/28463319/1222019) that parser was added in Solr 4.8, though it may be possible to add it to the solr war file in earlier versions and recompile.