Search API Solr search is stable!

Mon, 2013-06-10 18:55 -- drunken monkey

TL; DR:

After being production-ready for a long while and having accumulated several thousand users, the Search API Solr Search project has now finally got a stable release. Included is the promise and hope that the configuration files and inner workings of the module are now insofar stable, as that future minor version upgrades won't require any re-indexing anymore.
If you are using an older version (especially pre-RC4), upgrade now and benefit from a range of new features and bug fixes!


It sometimes seems to me, that there are two different types of Drupal module maintainers: the ones who create a stable 1.0 release as soon as any code is working; and those who leave their modules "unstable" for years until they finally pluck up the courage to go 1.0. (I guess there also have to be some with the right middle approach, but those propably just don't catch one's eye as much.) There are actually projects in the top 10 of contrib module usage without a stable 7.x release (although there may of course be good reasons for that).
Anyways, in that pattern I'm definitely one of the latter group. I have only recently gotten to eventually creating stable releases for a number of modules (though some of them already had several thousand users) – Search API Database search (over 11k users) and Search API Pages (almost 3k users) are still waiting – and the 1.0 release of the Search API itself also took extremely long (by which time it also already had over 2000 reported* users).

In that context, it is kind of a milestone that there is now finally a 1.0 release of the Search API Solr Search module. (If you are not familiar with it, it's pretty self-explanatory: it allows you to use Apache Solr with the Search API.) As with the other modules, it had already been production-ready for quite some time, and currently has almost 5000 users.

In the case of the Solr Search module, though, there were several good reasons to wait with a stable release – foremost, the Apache Solr Common Configurations project, though definitely a good thing, changed the configuration files quite drastically when the module was otherwise stable. We also managed to add numerous feature (like location search support) and fix a lot of bugs, but those would have probably worked as well in subsequent minor releases. There were some other major refactorings, though, (foremost the effort to get rid of the external library dependency) whose inclusion in the 1.0 release is definitely beneficial.

Additionally, for the Solr Search module the 1.0 stable release is also kind of a promise: with it, I'm saying that I'm now confident that no major changes to the config files will be necessary anymore, so that there won't be the necessity for re-indexing the content for future new (minor) releases. Time will tell whether I'll be able to keep that promise but, as said, I'm quite confident.

So, if you shied away from giving the module a spin in the past, due to its missing stable release: it has been ready for quite some time now, but now it's official!
For all existing users: upgrade to the new stable release and see if there are features or bug fixes that help you out (or, hopefully not, any bugs you can report)! Recent additions include support for SSL, field collapsing, Solr 4.x and location-based searches.
(Also, check out the new documentation, if you haven't done so already!)

* By the way, is there any data or estimations out there on what percentage of users the Drupal.org usage statistics actually capture?

Image credit: Sergey Melkonov

Comments

Submitted by marcvangend (not verified) on

Congratulations on the release, and thanks for the hard work!

Submitted by John Ennew (not verified) on

"those who leave their modules "unstable" for years until they finally pluck up the courage to go 1.0" - My favourite there is Image Cache, 141,000 website using it, a mere 31 open bugs and good enough to make it into core in Drupal 7 - still only at release candidate 1.
https://drupal.org/project/ImageCache

Submitted by Phil (not verified) on

"Drupal, the CMS where you bleed the dev"

Grats on a stable release!

Submitted by SpiffBB (not verified) on

Thank you for all the hard work you put in this great set of modules!

Submitted by Andreas Licht (not verified) on

Hi thanks for these great modul, but now i want to get all documents with searching by '*', how can i realize that, when i build the request by url i am getting all documents.

Submitted by drunken monkey on

You probably want to use the parse mode "direct query", in Views' Advanced » Query settings.
However, better ask such questions in the issue queue.

Add new comment

To prevent spam, submitting full URLs in comments is not allowed. Please omit the "http[s]://" portion of the URL and I will restore the complete URL on review.

Filtered HTML

  • Lines and paragraphs break automatically.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <q> <cite> <blockquote> <code> <ul> <ol> <li> <dl> <dt> <dd> <sup> <sub> <p> <br>
  • To post pieces of code, surround them with <code>...</code> tags. For PHP code, you can use <?php ... ?>, which will also colour it based on syntax.

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.