Remove Apache Solr assumption

Thanks, Nick. So if Search API implemented a numeric_range query type it could use this module? Or are there any other gotchas you can think of?

Good stuff. Postponing pending conversations with Thomas since Search API needs to do some work in order for this task to proceed / be verified that it will work.

No, I don't see that project as being a replacement. The goal of Facet API is to create a framework where contributions are module-agnostic, so whether you are using Search API, Apache Solr Search Integration, core Search, Bob-X Search, whatever, the code should be able to be re-used. Therefore having modules that specifically depend on one project is against the overall goals and benefit of Facet API. For ranges and sliders, looks like we have some work to do to figure out how to meaningfully consolidate code and effort.

Thanks,
Chris

Consider putting this paragraph as a Goal section on the Facet API modules page, so that everyone will get it.

Great suggestion. I will make sure to refresh the project page more clearly stating this goal. It is kind of buried in the section that it explains how it integrates with all of the various modules, so based on your suggestion I will provide a "Goals" header that clearly defines this.

Even some other Acquians are building an Apache Solr specific Geo search at http://drupal.org/sandbox/pwolanin/1497066 instead of working on a generic module like http://drupal.org/project/search_api_location

True, but understand that at this time for D7 (pulling from the May 13, 2012 statistics), approximately twice as many people are using Apache Solr Search Integration as Search API Solr (3,664 / 1,830). In addition, Apache Solr Search Integration does provide an API compatible backport of the D7 version for D6, so the geo module could provide that functionality for the numerous people who are unable to leverage Search API based on the version of Drupal they are using. I'm not arguing for or against either project, I am just saying that forcing people to switch to Search API for geolocation would be telling thousands of people to drastically change their site's architecture.

Also note that I am an Acquian who got Acquia time to write the Facet API module, so we are very interested in providing generic solutions and consolidating the search community. I am also getting time to work on Search API Solr so that it can work with Acquia Search, which in turn will further align the efforts of the two communities. So just to be clear, we are very Search API friendly :-).

Thanks,
Chris

Search API Ranges says, so it may be a viable solution:

Excellent! Didn't know there was parallel effort going on here. To be honest I could care less which project is deprecated, I just want something that implements Facet API and is backend agnostic :-)