Fix issue 2489

[penghuo]

Description

• Use OpenSearch DateFieldMapper.getDefaultDateTimeFormatter as default format if format is missing.
• Integrate with yamlRestTest to framework to test OpenSearch specific cases.
  • YamlRestTest execut along with ./gradlew integ-test:build.
  • YamlRestTest execut independenly. ./gradlew integ-test:yamlRestTest.
• Remove "2015-01-01 12:10:30" related UT, it is not valid OpenSearch default date format.

### Create Index
PUT {{baseUrl}}/idx00003
Content-Type: application/x-ndjson

{
  "mappings": {
    "properties": {
      "timestamp": {
        "type":   "date"
      }
    }
  }
}

### Index data failed
POST {{baseUrl}}/idx00003/_doc
Content-Type: application/x-ndjson

{"timestamp": "2015-01-01 12:10:30"}

### Index data failed
{
  "error": {
    "root_cause": [
      {
        "type": "mapper_parsing_exception",
        "reason": "failed to parse field [timestamp] of type [date] in document with id 'dyoyNpYBxdmNMfRxwqjc'. Preview of field's value: '2015-01-01 12:10:30'"
      }
    ],
    "type": "mapper_parsing_exception",
    "reason": "failed to parse field [timestamp] of type [date] in document with id 'dyoyNpYBxdmNMfRxwqjc'. Preview of field's value: '2015-01-01 12:10:30'",
    "caused_by": {
      "type": "illegal_argument_exception",
      "reason": "failed to parse date field [2015-01-01 12:10:30] with format [strict_date_optional_time||epoch_millis]",
      "caused_by": {
        "type": "date_time_parse_exception",
        "reason": "Failed to parse with all enclosed parsers"
      }
    }
  },
  "status": 400
}

Related Issues

#2489

Check List

• New functionality includes testing.
• New functionality has been documented.
• New functionality has javadoc added.
• New functionality has a user manual doc added.
• API changes companion pull request created.
• Commits are signed per the DCO using --signoff.
• Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[qianheng-aws]

Remove "2015-01-01 12:10:30" related UT, it is not valid OpenSearch default date format.

This should be a breaking change that replacing DATE_TIME_FORMATTER with DateFieldMapper.getDefaultDateTimeFormatter(), which means we no longer support parsing value with format "yyyy-MM-dd HH:mm:ss". Shall we add this change in this issue: #3248 or somewhere else for recording breaking change after 3.0 release?

And shall we keep the format align in the final results? After this change, the input value will require format with "yyyy-MM-ddTHH:mm:ss" or epoch_millis by default if no user-specified formats, while the PPL results will always show timestamp with format "yyyy-MM-dd HH:mm:ss"

[qianheng-aws]

Shall we remove DATE_TIME_FORMATTER from DateTimeFormatters since it's no longer used anywhere.

[penghuo]

done. 801ca25

[penghuo]

This should be a breaking change that replacing DATE_TIME_FORMATTER with DateFieldMapper.getDefaultDateTimeFormatter(), which means we no longer support parsing value with format "yyyy-MM-dd HH:mm:ss". Shall we add this change in this issue: #3248 or somewhere else for recording breaking change after 3.0 release?

It is not a breaking change. yyyy-MM-dd HH:mm:ss it is not valid OpenSearch default date format. I explained in PR description.

And shall we keep the format align in the final results? After this change, the input value will require format with "yyyy-MM-ddTHH:mm:ss" or epoch_millis by default if no user-specified formats, while the PPL results will always show timestamp with format "yyyy-MM-dd HH:mm:ss"

Not necessary, index mapping default format enforce on ingestion. PPL could have it own default format when present result.

[qianheng-aws]

It is not a breaking change. yyyy-MM-dd HH:mm:ss it is not valid OpenSearch default date format. I explained in PR description.

Got it, although we have such test cases before, it seems could never be happened in fact for customers because opensearch will throw error when putting such a value without customized format

[dai-chen]

Thanks for the changes!

Any guidance when should we add test to this new yaml test? Any bug fix?