[Discover] Fix context view for date_nanos format with custom timestamps

[kertal]

Summary

Discover's context view currently doesn't work when you're using a custom formatted date_nanos timestamp like this: { "type" : "date_nanos", "format" : "yyyy-MM-dd HH:mm:ss.SSSSSS" }.

We're currently using the timestamp stored in _source to provide the context functionality with date_nanos timestamps, which is due to the limited support of BigInt support of Browsers. If the _source value is formatted in a non standard way, the conversion to a Date Object may fail. This fix switches from the value stored in _source to the value provided by fields of the search result.

This contains a strict_date_time formatted string, so there are no more problems with custom timestamp formats

Fixes #48064

Testing

You can use the following data to test the fix:

PUT date_nanos_test-ms
{
  "mappings": {
    "properties": {
      "timestamp": {
        "type": "date_nanos",
        "format" : "yyyy-MM-dd HH:mm:ss.SSSSSS"
      }
    }
  }
}

PUT date_nanos_test-ms/_doc/1
{
  "timestamp": "2019-10-12 00:30:04.828740",
  "test": "1"
}

PUT date_nanos_test-ms/_doc/2
{
  "timestamp": "2019-10-21 08:30:04.828733",
  "test": "1"
}


PUT date_nanos_test-ms/_doc/3
{
  "timestamp": "2019-10-21 00:30:04.828723",
  "test": "1"
}

Before the fix:

After the fix:

Checklist

Use strikethroughs to remove checklist items you don't feel are applicable to this PR.

- [ ] This was checked for cross-browser compatibility, including a check against IE11
- [ ] Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
- [ ] Documentation was added for features that require explanation or tutorials

• Unit or functional tests were updated or added to match the most common scenarios
  - [ ] This was checked for keyboard-only and screenreader accessibility

For maintainers

- [ ] This was checked for breaking API changes and was labeled appropriately
- [ ] This includes a feature addition or change that requires a release note and was labeled appropriately

[kertal]

@elasticmachine merge upstream

[kertal]

@elasticmachine merge upstream

[kertal]

@elasticmachine merge upstream

[Bargs]

Code change looks good to me and I tested the functionality in Chrome. Had one question about the tests that were changed.

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 904bb88

History

• 💔 Build #19826 failed 3e56acb
• 💔 Build #19513 failed 1fc53c7
• 💔 Build #19365 failed 31ff2af
• 💔 Build #19330 failed a944014
• 💚 Build #18301 succeeded fc0f2f2

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[elasticmachine]

Pinging @elastic/kibana-app (Team:KibanaApp)