Closed (works as designed)
Project:
Apache Solr Autocomplete
Version:
7.x-1.2
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
16 Feb 2012 at 22:51 UTC
Updated:
12 Mar 2012 at 17:25 UTC
Hi folks,
There is a new module out there called "Sarnia" which allows a Drupal site to connect to any external Solr instance. With the Sarnia module users can use Views 3 to create search pages that provide full access to external Solr instances. It would be great if the autocomplete module would support Sarnia as an additional option. Thoughts?
Regards,
Mitch
Comments
Comment #1
janusman commentedApachesolr_autocomplete is tied to Apachesolr.module. Hence the apachesolr_ prefix.
Perhaps in a different project called sarnia_autocomplete? =)
Comment #2
christowm commentedJanusman,
Funny you should say that. I already started on that. I am using your code as the basis to build a Sarnia version. I would have preferred not to split this out as a separate project. But for the time being I will go ahead and build it that way. Maybe once I have it running and see how different the code base is, there may be a possibility to merge the changes back into this project. In any event. I am going ahead with a fork called sarnia_autocomplete. :)
Regards,
Mitch
Comment #3
janusman commentedSounds great! =)
Just am a bit concerned about the "developer experience" (confusing them). Probably might not be confusing... others might have the same idea you did... sort of "For all things Solr + Autocomplete, use Apache Solr Autocomplete" (hey, that even sounds like a jingle!) =)
Comment #4
lampson commentedJust use the Search API autocomplete module. It works fine with Sarnia.