Configuring ElasticSearch as Full Text

Support
1

I have…

I’m submitting a…

  • [X] Bug report

Current behavior

Trying to configure Elastic Search as the FullText store.

When starting squidex image, the following error appears in the logs and squidex image stops:

Unhandled exception. System.InvalidOperationException: Failed with ${“error”:{“root_cause”:[{“type”:“index_not_found_exception”,“reason”:“no such index [squidex]”,“resource.type”:“index_or_alias”,“resource.id”:“squidex”,“index_uuid”:“na”,“index”:“squidex”}],“type”:“index_not_found_exception”,“reason”:“no such index [squidex]”,“resource.type”:“index_or_alias”,“resource.id”:“squidex”,“index_uuid”:“na”,“index”:“squidex”},“status”:404}
—> Elasticsearch.Net.ElasticsearchClientException: Request failed to execute. Call: Status code 404 from: PUT /squidex/_mapping. ServerError: Type: index_not_found_exception Reason: “no such index [squidex]”
— End of inner exception stack trace —
at Squidex.Extensions.Text.ElasticSearch.ElasticSearchIndexDefinition.ApplyAsync(IElasticLowLevelClient elastic, String indexName, CancellationToken ct) in /src/extensions/Squidex.Extensions/Text/ElasticSearch/ElasticSearchIndexDefinition.cs:line 126
at Squidex.Hosting.InitializerHost.StartAsync(CancellationToken cancellationToken)
at Microsoft.Extensions.Hosting.Internal.Host.StartAsync(CancellationToken cancellationToken)
at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token)
at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token)
at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.Run(IHost host)
at Squidex.Program.Main(String[] args) in /src/src/Squidex/Program.cs:line 18

Expected behavior

ElasticSearch is correctly used, and index created.

Minimal reproduction of the problem

docker-compose.xml

services:
  mymongodb:
    image: mongo:5.0.5
    container_name: mymongodb
    networks:
      my-net:
        ipv4_address: 172.21.0.10

  mysquidex:
    image: "squidex/squidex:6.6.0"
    container_name: mysquidex
    environment:
      - URLS__BASEURL=https://${SQUIDEX_DOMAIN}
      - EVENTSTORE__TYPE=MongoDB
      - EVENTSTORE__MONGODB__CONFIGURATION=mongodb://mymongodb
      - STORE__MONGODB__CONFIGURATION=mongodb://mymongodb
      - IDENTITY__ADMINEMAIL=${SQUIDEX_ADMINEMAIL}
      - IDENTITY__ADMINPASSWORD=${SQUIDEX_ADMINPASSWORD}
      - IDENTITY__GOOGLECLIENT=${SQUIDEX_GOOGLECLIENT}
      - IDENTITY__GOOGLESECRET=${SQUIDEX_GOOGLESECRET}
      - IDENTITY__GITHUBCLIENT=${SQUIDEX_GITHUBCLIENT}
      - IDENTITY__GITHUBSECRET=${SQUIDEX_GITHUBSECRET}
      - IDENTITY__MICROSOFTCLIENT=${SQUIDEX_MICROSOFTCLIENT}
      - IDENTITY__MICROSOFTSECRET=${SQUIDEX_MICROSOFTSECRET}
      - ASPNETCORE_URLS=http://+:5000
      - FULLTEXT__TYPE=elastic
      - FULLTEXT__ELASTIC__CONFIGURATION=http://elastic:password@172.21.0.12:9200
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:5000/healthz"]
      start_period: 60s
    depends_on:
      - mymongodb
      - myelasticsearch
    networks:
      my-net:
        ipv4_address: 172.21.0.11

  myelasticsearch:
    image: docker.elastic.co/elasticsearch/elasticsearch:7.6.1
    container_name: myelasticsearch
    restart: always
    environment:
      - "discovery.type=single-node"
      - ELASTIC_PASSWORD=password
      - cluster.name=elastic-cluster
    ports:
      - 9200:9200
    networks:
      my-net:
        ipv4_address: 172.21.0.12

Environment

App Name: None

  • [X] Self hosted with docker

Version: 6.6.0

Browser:

  • Not Applicable
2

You have to create the index, e.g. “squidex” as mentioned in the logs.

3

I though Squidex would create it automatically, like logstash or kibana do.

So the solution is to create the index as a separate logic?
Like adding it to a startup script in squidex or elasticseach images?

4

You can create a feature request for that ofc.

1 Like
5

Btw: I don’t see that kibana needs to configure the indexes somehow because it is read only. Not sure about logstash. But if I remember correctly the main reason, why I do not create the index is that there are a few settings that need to be customized.

6

Howdy :slight_smile:

I have one question, after successful configuration between squidex and elasticsearch can i use squidex search api todo my querys or i need to expose an elasticsearch api url for my query’s?

Thanks in advance.

7

Yes, you can, these are the needed values: https://github.com/Squidex/squidex/blob/master/backend/src/Squidex/appsettings.json#L36

So it is basically

FULLTEXT__TYPED=Elastic
FULLTEXT__ELASTIC__CONFIGURATION=[CONNECTION_STRING]
8

Howdy again :slight_smile:

After having evidences that squidex integration with elasticsearch instance is working, i’m trying testing the API https://localhost/api/apps/{app}/search to return contents by quering some key words.

But it seems that the returned results are only related to schemas names, like the following test:

image
image1490×728 46.5 KB

Has i said before when i query any text from content in squidex index nothing is returned.

Here’s a sample of my elasticsearch instance:

image
image778×950 28.6 KB

There’s something missing in my search test?

9

Could be a bug, but the yellow part is actually the interesting stuff :wink: … Especially the “texts” fields.

10

The yellow status only indicates there isn’t a cluster for elastic search, beacause we only configured one node.

11

Status? I mean the removed information from the screenshot with the yellow color.

1 Like