Closed (fixed)
Project:
Search API Multi-Index Searches
Version:
7.x-1.0-rc1
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
31 Oct 2012 at 17:01 UTC
Updated:
28 Dec 2012 at 21:40 UTC
Jump to comment: Most recent file
Comments
Comment #1
eme commentedSame here using Apache SOLR, last version of Views and last version of search api and current + dev version of this module and search API.
Comment #2
arrubiu commentedI've tried the dev version, also this doesn't work.
My drupal logs say:
Notice: Trying to get property of non-object in SearchApiMultiViewsQuery->get_result_wrappers() (linea 99 di /home/sdurzu/mysite/sites/all/modules/contrib/search_api_multi/views/query.inc).And apache logs say:
[Tue Nov 13 09:14:20 2012] [error] [client 127.0.0.1] PHP Fatal error: Call to a member function datasource() on a non-object in /home/sdurzu/mysite/sites/all/modules/contrib/search_api_multi/views/query.inc on line 100Comment #3
minoroffense commentedWhen use var_dump the following (from search_api_multi/views/query.inc:100)
I get
The solr search has two indexes: the defautl node one and one I added for the user entities. I create a single page view using the "Solr" base table.
Using the dev version of search api, search api solr and search api multi index. Every other module is using the latest stable.
Comment #4
minoroffense commentedThe results I get back from Solr are for an index that don't exist on this Drupal site. It is an old dev index. If we look at the results array from solr (in my case) I get:
from search_api_multi/views/query.inc:49
I wonder if the Solr configuration needs updating to limit the index results to only those for the given Drupal site. Or the case may be for multi index searches, the Solr server needs to exist for this site alone. Are the solr instances you're using shared as well or are they dedicated to only the Drupal site in question. I'm not an expert in deploying Solr so I can't answer that question.
Comment #5
minoroffense commentedIf in your Filter criteria in Views, you add an entry for "Search: Index" and limit to your own search indexes. the search results start working again. See the screenshot below.
Comment #6
eme commentedGood catch : same here. It misses some sort of "all server" parameter. If you expose the filter criteria, it does not work again (by default it is "all"), il works again if you require it..
Comment #7
minoroffense commentedAlright, in the end I got things working. There are definitely some sanity check bugs in the code which need to be added but for the most part it's an issue of documentation.
To get this to work, ensure you're:
I'll post some issues from my "adventure" with the module to help make it easier to use.
Thanks.
Comment #8
drunken monkeyWell, normally you of course shouldn't leave stale data on your Solr server, and using the same server for several sites also isn't supported as such.
However, since several of you seem to have problems, please try the attached patches for this module and the Solr module.
Either of those should fix the issue, so it would be great if you could first test one, then revert again and test the other one.
If both work, I'll commit both, of course.
Comment #9
drunken monkeyNo-one here to test these? I'd like to fix this issue before I create a stable release, but would like to do that soon.
Comment #10
minoroffense commentedI'll be doing more work on the search portion of a client project next week. I can test the patches then. Hopefully that works well for your schedule.
Comment #11
drunken monkeyWill you test/review soon or should I just commit this and hope for the best?
Comment #12
minoroffense commentedWorking on it now. Just getting Solr back up and running.
Comment #13
minoroffense commentedPatches seem to work. Not getting errors anymore.
Comment #14
drunken monkeyOK, thanks for testing.
Committed!