This JIRA issue and this wiki page imply that there is an up-and-coming component called org.apache.solr.spelling.suggest.Suggester for doing improved auto-complete with Solr. But I'm having trouble trying to find a release that actually has this code.
The wiki says that Solr 3.x and 4.x have include it; is that insider-speak for Solr 1.3 and 1.4 respectively? I'm using 1.4.1 (via Maven), and I see no such component.
Pulling the source from here, I find it in src/java/org/apache/solr/spelling/suggest/Suggester.java. But it fails to build with:
[javac] Compiling 8 source files to /Users/user/Downloads/apache-solr-4.0-2011-02-22_08-06-33/apache-solr-4.0-2011-02-22_08-06-33/contrib/analysis-extras/build/classes
BUILD FAILED
/Users/user/Downloads/apache-solr-4.0-2011-02-22_08-06-33/apache-solr-4.0-2011-02-22_08-06-33/common-build.xml:275: /Users/user/Downloads/apache-solr-4.0-2011-02-22_08-06-33/apache-solr-4.0-2011-02-22_08-06-33/contrib/analysis-extras/lib does not exist.
Is there a way to get a reasonably stable Solr artifact with the Suggester included, preferably via Maven?
Solr 3.x and 4.x are not 1.3 and 1.4.
1.3 and 1.4 are stable releases. 3.x and 4.x are yet unreleased. Versioning scheme changed due to Solr merging with Lucene.
If you need a 4.x build I recommend getting one from the build server.
Also note there are several ways to implement autocomplete with 1.4.1, see Simple Solr schema problem for autocomplete
Related
I am planning to use MapStruct in my project. Using JDK11, Spring boot 2.7.x has my current version but soon planning to upgrade it to JDK17 and Spring Boot 3.0. Based on documentation, latest library will support JDK8 onwards. Would like to know, whether library will support for above said specification. And also would like to know, how actively the project is going to support in near future?
i have a Zend Framework project and i need to know which framework and version they use. also is that mandatory to migrate the project from Zend to laminas. having no idea to what to do.
You can find the current version in Zend_Version::VERSION constant (there will be the same, but namespaced for ZF2 and ZF3 I believe).
Also migration to laminas is not "mandatory". It's just that Zend Framework 1/2/3 is no longer maintained.
You can find community maintained forks for older versions (like diablomedia/zendframework1)
You can find the version of the framework and plugins in composer.json file in the application folder
We are planning to migrate AEM version from 6.4 to 6.5. How do we ensure the current codebase(built on AEM 6.4) will be compatible with AEM 6.5?
Will pattern detector help here ? Do we have any other way to identify if AEM 6.4 code will be compatible with AEM 6.5
Is the 6.4 AEM codebase inherited from a previous version (6.3 or older)? If the current site was developed with 6.4, more likely your site should work, but the only way is to test.
You have to take into account if you want to preserve all the content versioning (at the AEM level) or if a single package with the pages, XF, tags, and assets is enough.
Other than that, upgrade the AEM UberJar version and make a clean install and review the AEM logs. Make sure all the Java bundles are active, etc.
It is also helpful to capture visual evidence of the current look and feel and compare against the same pages running in 6.5.
The pattern detector is the first step, yes. The only way to truly ensure that the codebase is compatible is testing.
The only way to be absolutely sure is to build your project using the AEM 6.5 archetype.
The pattern detector will help identify potential issues but it won't guarantee that the code will be compatible.
I am using GWT 2.4 with Hibernate 3.0. I wanted to know what changes I need to make in my application for integrating GWT 2.5 in my application ?
Nothing special.
Replace 2.4.0 dependencies with 2.5.0-rc1 ones (depending on how you manage dependencies, either download the SDK and drop the new JARs to replace the previous ones, or bump the version number in your POM –if using Maven– or similar build file).
If you're using Maven and the gwt-maven-plugin, make sure you re-define the plugin dependencies too (note gwt-maven-plugin 2.4.0 also needs gwt-servlet to be overridden); or you can test the gwt-maven-plugin 2.5.0-rc1.
Check the list of breaking changes though; chances are small that they affect you, but there's still a risk.
Has anybody heard of the Lucene version 2.3.1.3?
We're using it in a production project.
However the stable version of Lucene version 2.0.0.4.
Should I push to have the project's dependencies moved to version 2.0.0.4?
Are you talking about Lucene or Lucene.NET? These are different but related projects. Lucene.NET is a .NET port of the Lucene Java code.
2.0.0.4 is the stable version of Lucene.NET.
However, there is a version 2.3.1 of Lucene (for Java). The Lucene Website makes it seem like 2.4.1 is the most recent release suitable for production.
I'm running 2.3.1.3 over here in production at about 50 sites.
I wouldn't recommend downgrading the version as a lot of performance and memory leak issues are adressed in 2.3.1.