Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Missing custumFields in Elastic search

See original GitHub issue

customfields are not listed in Elastic.

After adding customfields in in venture-config.

  customFields: {
    Product: [
      { name: "lat", type: "string" },
      { name: "long", type: "string" },
    ],
    ProductVariant: [
      { name: "lat", type: "string" },
      { name: "long", type: "string" },
    ],
  },

executing the API request to create a product and ProductVariant works. The API schema is correct, though the custom field records do not propagate to Elastic.

All fields are:

        {
            "_index": "vendure-products",
            "_type": "product-index-item",
            "_id": "1__98",
            "_score": 1.0,
            "_source": {
                "channelId": 1,
                "sku": "dk",
                "slug": "cool-name-2",
                "productId": 98,
                "productName": "cool name",
                "productAssetId": null,
                "productPreview": "",
                "productPreviewFocalPoint": null,
                "productVariantId": 100,
                "productVariantName": "cool name",
                "productVariantAssetId": null,
                "productVariantPreview": "",
                "productVariantPreviewFocalPoint": null,
                "priceMin": 1200,
                "priceMax": 1200,
                "priceWithTaxMin": 1200,
                "priceWithTaxMax": 1200,
                "currencyCode": "USD",
                "description": "<p>test</p>",
                "facetIds": [],
                "facetValueIds": [],
                "collectionIds": [],
                "channelIds": [
                    1
                ],
                "enabled": true
            }
        }

Issue Analytics

State:
Created 3 years ago
Comments:8 (4 by maintainers)

Top GitHub Comments

1reaction

grinonocommented, Jul 30, 2020

thanks, missed that extra elastic indeces. It’s showing up as expected.

0reactions

michaelbromleycommented, Jul 30, 2020

Thanks for including such detailed info, that’s helpful.

The reason that the elastic index does not show the custom mappings is that you are looking at the vendure-products index, whereas you only defined custom mapping for the ProductVariants, which would live in the vendure-variants index.

Top Results From Across the Web

Custom fields are empty - Beats - Discuss the Elastic Stack

The fields shouldn't be empty, but they might be missing from the Kibana index pattern. If you go to the Discover page and...

Missing meta field in mapping of index - how to solve ... - Opster

How to troubleshoot Elasticsearch/OpenSearch log "Missing meta field in mapping of index" a detailed guide including background on ES concepts: index, ...

Elasticsearch/Kibana: 3 ways to add missing fields during ...

Elasticsearch /Kibana: 3 ways to add missing fields during runtime · Solution 1: Create runtime_mappings · Solution 2: add a lens formula ·...

Fields missing on an Index of Elasticsearch from one moment ...

By some reason since today, some fields went missing, one of them is the very important field message . Looking the logs of...

Missing vs. Empty Fields - The Elasticsearch Handbook

The topic of empty-ish fields comes up often because: input fields weren't required and were skipped (e.g. optional input fields in signup forms)...