Skip to content

NimTechnology

Trình bày các công nghệ CLOUD một cách dễ hiểu.

  • Kubernetes & Container
    • Docker
    • Kubernetes
      • Ingress
      • Pod
    • Helm Chart
    • OAuth2 Proxy
    • Isito-EnvoyFilter
    • Apache Kafka
      • Kafka
      • Kafka Connect
      • Lenses
    • Vault
    • Longhorn – Storage
    • VictoriaMetrics
    • MetalLB
    • Kong Gateway
  • CI/CD
    • ArgoCD
    • ArgoWorkflows
    • Argo Events
    • Spinnaker
    • Jenkins
    • Harbor
    • TeamCity
    • Git
      • Bitbucket
  • Coding
    • DevSecOps
    • Terraform
      • GCP – Google Cloud
      • AWS – Amazon Web Service
      • Azure Cloud
    • Golang
    • Laravel
    • Python
    • Jquery & JavaScript
    • Selenium
  • Log, Monitor & Tracing
    • DataDog
    • Prometheus
    • Grafana
    • ELK
      • Kibana
      • Logstash
  • BareMetal
    • NextCloud
  • Toggle search form

[Golang] Define mapping when creating an index on Elasticsearch by Golang.

Posted on October 15, 2023October 15, 2023 By nim No Comments on [Golang] Define mapping when creating an index on Elasticsearch by Golang.

Mình có sử dụng Golang để create index trên elasticsearch.

mapping := map[string]interface{}{
    "mappings": map[string]interface{}{
        "properties": map[string]interface{}{
            "TimeStamp": map[string]interface{}{
                "type": "date",
            },
            "City": map[string]interface{}{
                "type": "text",
                "fields": map[string]interface{}{
                    "keyword": map[string]interface{}{
                        "type": "keyword",
                    },
                },
            },
            "District": map[string]interface{}{
                "type": "text",
                "fields": map[string]interface{}{
                    "keyword": map[string]interface{}{
                        "type": "keyword",
                    },
                },
            },
            "Ward": map[string]interface{}{
                "type": "text",
                "fields": map[string]interface{}{
                    "keyword": map[string]interface{}{
                        "type": "keyword",
                    },
                },
            },
            "PostTitle": map[string]interface{}{
                "type": "text",
                "fields": map[string]interface{}{
                    "keyword": map[string]interface{}{
                        "type": "keyword",
                    },
                },
            },
            "LandArea": map[string]interface{}{
                "type": "float",
            },
            "Price": map[string]interface{}{
                "type": "float",
            },
            "PostOwner": map[string]interface{}{
                "type": "text",
                "fields": map[string]interface{}{
                    "keyword": map[string]interface{}{
                        "type": "keyword",
                    },
                },
            },
            "Priority": map[string]interface{}{
                "type": "keyword",
            },
            "NumberOfBedroom": map[string]interface{}{
                "type": "integer",
            },
        },
    },
}

Giờ chúng ta mổ sẻ từng bổ phần nhỏ

“mappings”:

  • This is the root field for the mapping definition.
  • It contains the properties that define how the fields in the document will be mapped.

“properties”:

  • This field defines the fields that will be present in the documents that are indexed.
  • Each property/field is defined with a name and its type, along with additional properties.
            "time-stamp": map[string]interface{}{
                "type": "date",
            },

"type": "date": Specifies that the field will store date values.

            "City": map[string]interface{}{
                "type": "text",
                "fields": map[string]interface{}{
                    "keyword": map[string]interface{}{
                        "type": "keyword",
                    },
                },
            }

“City”: This is the name of the field in Elasticsearch.
map[string]interface{}: This is a Go map, where the key is a string and the value can be any type (interface{}). This map represents the configuration or settings of the “City” field in Elasticsearch.

“type”: “text”: The “City” field is of type “text” in Elasticsearch. This means that this field will store textual data and will be analyzed during indexing. Analyzed fields can be searched for partial matches. For example, if you have a city named “San Francisco”, you can search for just “San” and still get a match.

“fields”: Multi-fields allow you to index a single piece of text in multiple ways, typically once as a full text text field and once as a keyword field. This is useful for fields where you want to perform full-text search as well as sorting or aggregation.

“type”: “keyword”: This specifies that the “keyword” multi-field is of type “keyword” in Elasticsearch. A keyword is an unanalyzed field, meaning it is taken as-is without any analysis. This is useful for filtering, sorting, and aggregations. When you search against a keyword field, you have to provide the exact term.

Metaphor:

Imagine a library where books are categorized by their titles. The “City” is like the title of a book. You can search for a book by typing only part of its title, say just “Harry” for “Harry Potter”. This is similar to the text type in Elasticsearch.

Now, imagine you also want to sort the books alphabetically by their exact titles. For this, you need the exact title, like “Harry Potter”, without any variations. This is similar to the keyword type in Elasticsearch.

ELK, Golang

Post navigation

Previous Post: [Docker] Pulling unlimited public docker images
Next Post: [Golang] How is Singleton in Golang.

More Related Articles

[Golang] Note mấy thứ hay ho về golang Coding
[Golang] Looking filepath.Walk to return any file and children folder in the folder Golang
[Golang / EKS] Accessing AWS EKS with Go: A Comprehensive Guide to Interacting with Kubernetes APIs AWS - Amazon Web Service
[Golang] Using Repository Pattern to integrate the Database (Postgres) Golang
[Golang/Container] Build docker/container Golang Coding
[Golang] Create multiple CRON functions by looping through a list Golang

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Tham Gia Group DevOps nhé!
Để Nim có nhiều động lực ra nhiều bài viết.
Để nhận được những thông báo mới nhất.

Recent Posts

  • [Azure] The subscription is not registered to use namespace ‘Microsoft.ContainerService’ May 8, 2025
  • [Azure] Insufficient regional vcpu quota left May 8, 2025
  • [WordPress] How to add a Dynamic watermark on WordPress. May 6, 2025
  • [vnet/Azure] VNet provisioning via Terraform. April 28, 2025
  • [tracetcp] How to perform a tracert command using a specific port. April 3, 2025

Archives

  • May 2025
  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021

Categories

  • BareMetal
    • NextCloud
  • CI/CD
    • Argo Events
    • ArgoCD
    • ArgoWorkflows
    • Git
      • Bitbucket
    • Harbor
    • Jenkins
    • Spinnaker
    • TeamCity
  • Coding
    • DevSecOps
    • Golang
    • Jquery & JavaScript
    • Laravel
    • NextJS 14 & ReactJS & Type Script
    • Python
    • Selenium
    • Terraform
      • AWS – Amazon Web Service
      • Azure Cloud
      • GCP – Google Cloud
  • Kubernetes & Container
    • Apache Kafka
      • Kafka
      • Kafka Connect
      • Lenses
    • Docker
    • Helm Chart
    • Isito-EnvoyFilter
    • Kong Gateway
    • Kubernetes
      • Ingress
      • Pod
    • Longhorn – Storage
    • MetalLB
    • OAuth2 Proxy
    • Vault
    • VictoriaMetrics
  • Log, Monitor & Tracing
    • DataDog
    • ELK
      • Kibana
      • Logstash
    • Fluent
    • Grafana
    • Prometheus
  • Uncategorized
  • Admin

Copyright © 2025 NimTechnology.