Server index status count never updates

Created on 10 April 2021, over 3 years ago
Updated 17 April 2024, 7 months ago

Problem/Motivation

The "Server index status" on an index's "View" tab never changes from 0.

It is possible that this is a result of a method not having been implemented on the Typesense backend class.

Steps to reproduce

  1. Create a Typesense server and index
  2. Index content
  3. Compare "Server index status" count with "Datasource" count or with count from drush sapi-ts 'index_name' '*' 'field_name'

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Fixed

Version

1.0

Component

Code

Created by

🇫🇷France bedlam Lyon

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇮🇹Italy robertoperuzzo 🇮🇹 Tezze sul Brenta, VI
  • 🇮🇹Italy robertoperuzzo 🇮🇹 Tezze sul Brenta, VI

    The drush command drush sapi-ts does not exist anymore, but I can't test the index status because the indexing process is stuck at the initialization.

    I'm using the demo_umami profile and these configs:

    search_api.index.articles.yml

    uuid: 399ff165-efed-4f19-8fa6-92996fcb4bc8
    langcode: en
    status: true
    dependencies:
      config:
        - search_api.server.typesense_test
      module:
        - node
        - search_api_typesense
        - search_api
    id: articles
    name: Articles
    description: ''
    read_only: false
    field_settings:
      title:
        label: Title
        datasource_id: 'entity:node'
        property_path: title
        type: typesense_string
        dependencies:
          module:
            - node
    datasource_settings:
      'entity:node':
        bundles:
          default: false
          selected:
            - article
        languages:
          default: true
          selected: {  }
    processor_settings:
      add_url: {  }
      aggregated_field: {  }
      custom_value: {  }
      entity_type: {  }
      language_with_fallback: {  }
      rendered_item: {  }
      typesense_schema:
        all_fields: false
    tracker_settings:
      default:
        indexing_order: fifo
    options:
      cron_limit: 50
      index_directly: true
      track_changes_in_references: true
    server: typesense_test
    

    search_api.server.typesense_test.yml

    uuid: b2c1e11d-a383-4c9d-acf8-87ac86d553a9
    langcode: en
    status: true
    dependencies:
      module:
        - search_api_typesense
    id: typesense_test
    name: 'Typesense test'
    description: ''
    backend: search_api_typesense
    backend_config:
      admin_api_key: ddev
      nodes:
        -
          host: typesense
          port: '8108'
          protocol: http
      retry_interval_seconds: '2'
    
  • 🇮🇹Italy robertoperuzzo 🇮🇹 Tezze sul Brenta, VI

    It was my fault, I didn't save the processors' index (/admin/config/search/search-api/index/articles/processors) before running the indexing.
    The "Server index status" is correct.

  • Issue was unassigned.
  • Status changed to Fixed 8 months ago
  • 🇮🇹Italy robertoperuzzo 🇮🇹 Tezze sul Brenta, VI

    This issue has been fixed with the current version 1.0.x-dev.

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024