Can you hook an existing Elasticsearch index to Elastic App search

Elastic Search
1

I want to integrate App Search in my project. App search runs fine out of the box. But I have an application that is running on Elasticsearch, I was wondering if I could use this existing index as a backend for App search? If No, is it because documents are indexed differently for App Search engine compared to Elasticsearch? Also, why can't I access App search documents from my elasticsearch cluster (localhost:9200)?

1 Like
2

You need to reindex using AppSearch.

3

Where do the Appsearch documents reside? I can see that they are not an index on elasticsearch. I can't find it on localhost:9200. I wanted to know if I can browse app-search index and documents like indices and documents on elasticsearch.

I did not find any information related to it on Elastic and Swift type documentation.

4

I don't know. And actually it should not be exposed or used by anything else than AppSearch.

Basically you send documents to AppSearch. You send queries to AppSearch.
You should not really be aware that the back end is actually elasticsearch :slight_smile:

That being said, I just started an AppSearch instance on cloud.elastic.co and ran from Kibana:

GET /_cat/indices/.app-search*/?v&h=index

And I can see:

index
.app-search-actastic-clusters
.app-search-actastic-loco_moco_accounts_v2-key-unique-constraint
.app-search-actastic-users-email-unique-constraint
.app-search-actastic-user_external_identities_v1
.app-search-actastic-loco_moco_document_position_queries
.app-search-actastic-document_types
.app-search-actastic-elasticsearch_indices
.app-search-actastic-loco_moco_accounts_v3-key-unique-constraint
.app-search-actastic-loco_moco_role_engines
.app-search-esqueues-me_queue_v1_index_adder
.app-search-esqueues-me_queue_v1_analytics_events
.app-search-actastic-synonyms
.app-search-actastic-loco_moco_document_positions
.app-search-actastic-loco_moco_api_tokens
.app-search-actastic-index_pointers
.app-search-actastic-loco_togo_role_mappings_v1
.app-search-actastic-loco_moco_invitations
.app-search-actastic-reindex_jobs
.app-search-actastic-user_external_identities_v1-external_id-service_type-unique-constraint
.app-search-actastic-engines_v5-account_id-loco_moco_account_id-slug-unique-constraint
.app-search-esqueues-me_queue_v1_reindexer
.app-search-esqueues-me_queue_v1_schema_updater
.app-search-actastic-engines_v3-account_id-loco_moco_account_id-slug-unique-constraint
.app-search-actastic-loco_moco_accounts-key-unique-constraint
.app-search-actastic-engines_v7-key-unique-constraint
.app-search-actastic-index_pointers_v2
.app-search-actastic-engines-key-unique-constraint
.app-search-actastic-document_types-engine_id-slug-unique-constraint
.app-search-esqueues-me_queue_v1_refresh_document_counts
.app-search-esqueues-me_queue_v1_mailer
.app-search-actastic-loco_togo_role_mapping_engines_v1-engine_oid-loco_togo_role_mapping_id-unique-constraint
.app-search-actastic-engines_v4-account_id-loco_moco_account_id-slug-unique-constraint
.app-search-actastic-users_v2
.app-search-actastic-clusters-name-unique-constraint
.app-search-actastic-users_v2-email-unique-constraint
.app-search-actastic-engines_v6-key-unique-constraint
.app-search-actastic-engine_document_backends
.app-search-actastic-loco_moco_api_token_engines
.app-search-actastic-loco_moco_search_settings
.app-search-actastic-engines
.app-search-actastic-loco_togo_role_mapping_engines_v1
.app-search-actastic-loco_moco_roles
.app-search-actastic-loco_moco_api_tokens-authentication_token-unique-constraint
.app-search-actastic-engines-account_id-loco_moco_account_id-slug-unique-constraint
.app-search-actastic-engines_v5-key-unique-constraint
.app-search-actastic-engines_v6-account_id-loco_moco_account_id-slug-unique-constraint
.app-search-esqueues-me_queue_v1_indexed_doc_remover
.app-search-actastic-loco_togo_migrations_v1
.app-search-actastic-engines_v2-account_id-loco_moco_account_id-slug-unique-constraint
.app-search-actastic-loco_moco_role_engines_v2
.app-search-actastic-loco_moco_roles_v2
.app-search-actastic-loco_moco_accounts_v2
.app-search-actastic-loco_moco_document_position_queries_v3
.app-search-actastic-loco_moco_document_position_queries_v2
.app-search-actastic-loco_moco_accounts_v3
.app-search-actastic-loco_moco_invitations_v3
.app-search-actastic-loco_moco_invitations_v2
.app-search-actastic-engines_v4-key-unique-constraint
.app-search-esqueues-me_queue_v1_engine_destroyer
.app-search-actastic-engines_v3-key-unique-constraint
.app-search-actastic-users
.app-search-actastic-engines_v7
.app-search-actastic-engines_v7-account_id-loco_moco_account_id-slug-unique-constraint
.app-search-actastic-engines_v6
.app-search-actastic-engines_v5
.app-search-actastic-engines_v4
.app-search-actastic-engines_v3
.app-search-actastic-engines_v2
.app-search-esqueues-me_queue_v1_document_destroyer
.app-search-db-lock
.app-search-actastic-engines_v2-key-unique-constraint
.app-search-actastic-loco_moco_accounts

So I believe there should be something there...

5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.

6

Hey all - we've recently introduced new functionality on two fronts that will certainly help with the use case at hand:

  1. A way to use existing Elasticsearch indices with App Search. You can still create and managed indices (via engines) with App Search, but this gives you more flexibility on where and how the data is indexed. If some restaurants are bring your own wine, App Search is now bring your own Elasticsearch index :slight_smile:

  2. A way to use the Elasticsearch Query DSL for any App Search engine. This means even the most demanding of queries can be issued against App Search engines, with all the automatic goodness of Analytics capture, for example.

Hope this helps you all on this thread, and perhaps any other peer that stumbles upon this thread!

-- Jonas