Hi!

Thanks all for the great work!

First of all: I'm not an expert (at all!)...
I try to use the elasticsearch connector module in order to speed up my search. I want to recall data that are on a server on a view (ok, I can do that) but I cannot recall an index (a type for the ES) that is on the server as use all the functionality of the search api "submodule" (autocomplete and spellcheck for example).

Maybe is better explained with a practical example. Steps that I follow now:
1. Add a new cluster for the elasticsearch connector (OK)
2. Add a new server in search API (OK)
3. add a new index in search API (not what I want to do)

when I open the Add index window, I can use the server that I've created before and also I can select one of the index that are on that specific server, but I want use is, not create a new one!

Hope I can explain my problem, sorry for my inexperience... (I've asked the same question in the Elasticsearch connector issues, but maybe here is more appropriate)

Thank you so much for the attention,

MC

Comments

drunken monkey’s picture

So, making sure I understand your question correctly: You want to use Elastic Search, but without letting the Search API index items. You want to use an index that's already in Elastic Search, and has some content in it (possibly not even from the same Drupal site)?
I don't think that's possible at the moment, the right place to ask for this would probably be the ES Connector module's issue queue, where you might propose either an addition to the module or a new module that adds support for this. But in general, the Search API is aimed at indexing and searching data from the same Drupal site. Searching through external data needs additional work to set up.

(Also, it would have been very helpful to link to your other issue in the ES Connector module.)

drunken monkey’s picture

Status: Active » Postponed (maintainer needs more info)
legolasbo’s picture

Status: Postponed (maintainer needs more info) » Closed (outdated)

This issue has not seen activity in over 2,5 years. I am therefore closing this issue to clean up the issue queue. Feel free to re-open and update this issue if you feel this issue is still relevant and of importance.