Closed (fixed)
Project:
Search API
Version:
7.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
9 Feb 2012 at 23:36 UTC
Updated:
1 Mar 2012 at 17:50 UTC
Im not sure if it would be a good idea, but im curious about using search api to replace most of my nodes using views. Currently Im using standard views, however with Search API solr, and views integration, I have soo much more flexibility with creating related content, by using 'fulltext' as an argument.
Would this would be more efficient? I'm running the solr on a separate server, and if so, I could also cut a few modules off such as recommender api.
Comments
Comment #1
marcoka commentedDepends on speed and data. With too much stuff i guess you need solr to be fast and that requires a root.
I dont use search api to generally replace core search.
If you have solr always avaliable, i would say search api is the better search experience. As you said..flexibility :)
Comment #2
ivan zugec commentedViews and Search API work great together when you use them to create blocks like, related content or recommended content. However if you're dependant on Solr for a lot of blocks, make sure it's on a stable server.
Comment #3
bigsyke commentedGood to know, thanks!