Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • I Indexer
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 23
    • Issues 23
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 21
    • Merge requests 21
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe SoftwareOpen Subsurface Data Universe Software
  • Platform
  • System
  • Indexer
  • Merge requests
  • !164

address indexing issue where data block becomes unsearchable

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged neelesh thakur requested to merge data-mapping into master Jul 01, 2021
  • Overview 1
  • Commits 2
  • Pipelines 4
  • Changes 3

Issue: 49

In Elastic v7, if we have any property with following mapping

"data": {
       "properties": {}
}

It gets mapped to object type in Elastic. This makes all attributes inside data block un-searchable by Search Service API.

MR addresses the issue, so we don't get into this scenario.

Edited Jul 01, 2021 by neelesh thakur
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: data-mapping