Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • Search Search
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 35
    • Issues 35
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 10
    • Merge requests 10
  • 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
  • SearchSearch
  • Issues
  • #34
Closed
Open
Issue created Mar 29, 2021 by Gary Murphy@gtmurphyDeveloper

Index field not being returned in "returnedFields" option in Search query -- cannot get statusCode nor trace msg

Summary
Information about the status of indexing on a record is being created and kept in the Elastic index, but currently the value of that information is not directly accessible since it is not being returned in the "returnedFields" block when requested.
Details A standard query to return the "index" block is: { "kind": ":::", "limit": 100, "query": "index.statusCode:[399 TO 599]", "returnedFields": ["index", "id", "kind"] }

This should return a response with only "id", "kind", and "index" for those records with a response code in the given range. In the current implementation on Azure at least (may be common code...not checked), the query is honored in that only records that match the index assertion are returned, but the index block is not.
Example
Expected type of response to the above query:
{ "results": [ { "kind": "common:anp:block:1.0.0", "index": { "trace": [ "schema not found" ], "statusCode": 404, "lastUpdateTime": "2020-07-06T10:27:20.655Z" }, "id": "common:anp_block:3071854054914639" }

Whereas the current impl on Azure returns:
{ "results": [ { "kind": "common:anp:block:1.0.0", "index": { "trace": [ "schema not found" ], "statusCode": 404, "lastUpdateTime": "2020-07-06T10:27:20.655Z" }, "id": "common:anp_block:3071854054914639" }

Key info in the "index" block is therefore not available.

Assignee
Assign to
Time tracking