[Discover]view surrounding documents on date_nanos field, the result incorrect

[chgxtony]

Kibana version:
v7.3.2
Elasticsearch version:
v7.3.2
Server OS version:
ubuntu 16.04
Browser version:
chrome 77
Browser OS version:
mac 10.14
Original install method (e.g. download page, yum, from source, etc.):
source
Describe the bug:
View surrounding documents on date_nanos field, the surrounding documents is incorrect, diff 8 hours.

[elasticmachine]

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

[timroes]

@kertal is this currently one of the known limitations of Date Nanos? Or something we’re not yet aware of?

[kertal]

@timroes this should work
@chgxtony I'd be interested in the RAW JSON value of event_time of these 3 hits, when you expand a document, what's the value in JSON of event_time? thx!

[chgxtony]

@kertal

view surrounding documents :

[kertal]

Sorry for the long delay. it seems you using a custom date format, that's why it doesn't work
Standard format in Date datatype in Elasticsearch is strict_date_optional_time||epoch_millis
https://www.elastic.co/guide/en/elasticsearch/reference/current/date.html
Which date format are you using? thx!

[chgxtony]

I specify the format :
"event_time" : { "type" : "date_nanos", "format" : "yyyy-MM-dd HH:mm:ss.SSSSSS" }, it not work

when I use the format:
"event_time" : { "type" : "date", "format" : "yyyy-MM-dd HH:mm:ss.SSSSSS" }, it works

[kertal]

thx, will try that format. I'm pretty sure it would work if you'd use the standard datatype.

[kertal]

We found the cause of this behavior, it's due to the custom format you're using, there is no timezone information in it (Like a Z for UTC). We use a workarounds for date_nanos format to generate the search_aftervalue, since the browsers don't 64bit numbers natively. The browser takes your local timezone in this case. We will provide a fix.