The OR operator returns no results for facets with colons in the value (such as entity reference facets)

Hi amanire.

Thanks for the post and the details on your environment. Facet API doesn't actually perform the facet calculations, so this is most likely an issue with Apache Solr Search Integration. Switching to that project unless it is determined the root cause is somewhere in Facet API.

Thanks,
Chris

Support for entity reference is a feature request.

Also please provide more information so we can reproduce

Exact same issue here.
Versions : drupal-7.14, apachesolr-7.x-1.0-rc5 with the following patches applied : #1679392: Move logic from apachesolr_default_node_facet_info() into a separate function so other modules can use it for non-node entities and #1273658: Add the ability to filter by profile fields, apachesolr_user-7.x-1.x-dev, facetapi-7.x-1.1 and entityreference-7.x-1.0-rc3.

Steps to reproduce
In our case, it's been encoutered when searching for users :

1. add an entityreference field on user profile (core module profile-7.14)
2. Setup the facet for this entityreference field with "OR" :
   
3. create/generate a bunch of users with entities referenced
4. index these users
5. search & check that facet fails when selecting several entities (no results instead of more results as expected with "OR")

Actually, should this be an issue for the Facet API module ? I'm looking at #1161434: Modify "query type" key in facet definition to accept an array and wondering if that's related (still searching).

Hi paul.michalet.

Probably not. Unless there is some specific piece of code you can point to or debugging that highlights Facet APi as being the problem, I would stick with debugging the Apache Solr Search Integration module. Facet API does not set the parameters on the backend, nor does it do the facet calculations. I am open a bug being in Facet API, however with issues like this is it usually an issue with the backend.

Thanks,
Chris

This seems to be because entity reference facets use values like "node:133" but the colon has a special meaning in Solr.

Based on discussion in #1154770: Must double quote filter query values if containing space or colon. it seems like code which adds the filter to the query should be responsible for fixing it (by quoting the value so Solr doesn't get confused). Conveniently there's already some very similar code there which we can reuse.

Many thanks David !
This patch http://drupal.org/files/apachesolr-or-filter-colons-entityreference-1803... solved our issue.

Committed to 7.x-1.x, thanks!