Download search_api-7.x-1.0-beta3.tar.gztar.gz 121.36 KB
MD5: b324c2c807cca2b6599c3ceb1f1e4014
SHA-1: e73480256a3bb7abcc8a1fbfa9e6980d3f15a125
SHA-256: 3f617be467905bb42a7b13128d15dd4abf273543b00b2ad336829ca413020fca
Download search_api-7.x-1.0-beta3.zipzip 153.19 KB
MD5: 0db0c227dfc2a34c95151409e82c9d6f
SHA-1: d1ce629ea139ad1f6162b18a1a1f9a35814ca892
SHA-256: d647c28ef4600603a4baf06e968027abcd8057064d3f1939d0124b4ea57b36ec

Release info

Created by: drunken monkey
Created on: 30 Sep 2010 at 18:27 UTC
Last updated: 30 Sep 2010 at 18:43 UTC
Core compatibility: 7.x
Release type: New features, Bug fixes

Release notes

Added new modules:
- search_api_solr
- search_api_views
- search_api_facets

Several API changes:

- Query::execute() doesn't need to load the entities anymore, just IDs and score are returned.
- Some new query methods for dealing with options.
- Some new service class methods: configurationFormValidate(), configurationFormSubmit(), supportsFeature(), view() – but all with sensible defaults in AbstractService.
- Added Index::getFulltextFields() for convenience.
- Added search_api_current_search() as a static query cache (necessary e.g. for facetting). Along with this, added the concept of search IDs, so searches can be uniquely identified – at least within one page request.

A ton of bug fixes and other improvements.

Things that don't work yet (I admit it, there are a few):
- Facets on dates, or other ranges, at least in Solr.
- There is some other facet anomaly I have to investigate (sharp eyes will spy it in the screencast).
- Sorting by related entities' properties (e.g., author's name) in views – not my fault, though, it gets double-urlencoded by Views.
- Indexing taxonomy terms associated with a node, and even for two reasons:
-- Properties that are lists of entities can't be indexed.
-- Fields only present on a bundle, and not on all entities of that type, currently can't be indexed. This is simply a UI restriction I have to work around.
- Removing deleted entities from the index (see #709892: Complete entity CRUD hook invocations – it's not my fault).
- The tests are heavily out of sync with the module, this should be fixed before a 1.0 release. Also, the new modules are yet untested.


The selected release is the release that will be used for automated testing. Optional projects are only used for testing.



No optional projects