Skip to content

add schema parse error in record trace field

Neelesh Thakur requested to merge schema-errors into master

Address issue: 27

Add schema parse errors in record trace field on indexed records. Users can later use Search service to query records and check errors themselves.

As an example, in case of schema parsing failure, a generic message get's indexed on the record instead of actual error message:

 "results": [
    {
        "index": {
            "trace": [
                "schema not found"
            ],
            "statusCode": 404,
            "lastUpdateTime": "2021-06-24T14:23:50.596Z"
        },
        "id": "opendes:indexer-test:01ae8501-1534-4c6b-93e7-8ea2ed26d752.xml"
    }
]

This MR addresses this and indexes specific error messages (highlighted in bold), enabling ingestor to take corrective actions:

 "results": [
    {
        "index": {
            "trace": [
                "Errors occurred during parsing the schema, kind: opendes:indexer-test:sample-schema-2:2.0.0 | errors: kind cannot be null or empty for path 'WB_NAME'"
            ],
            "statusCode": 400,
            "lastUpdateTime": "2021-06-24T14:23:50.596Z"
        },
        "id": "opendes:indexer-test:01ae8501-1534-4c6b-93e7-8ea2ed26d752.xml"
    }
]

Instruction to search trace field can be found here.

Edited by Neelesh Thakur

Merge request reports