[Doris On ES][Bug-fix] Solve the problem of time format processing #3941
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#3936
Doris On ES can obtain field value from
_sourceordocvalues:_source, get the origin value as you put, ES process indexing、docvalues fordatefield is converted to milliseconddocvalues, before( 6.4 you getmillisecond timestampvalue, after(include) 6.4 you get the formatteddatevalue :2020-06-18T12:10:30.000Z, but ES (>=6.4) provideformatparameter fordocvaluefield request, this would coming soon for Doris On ESAfter this PR was merged into Doris, Doris On ES would only correctly support to process
millisecondtimestamp and string format date, if you provided asecondstimestamp, Doris On ES would process wrongly which (divided by 1000 internally)ES mapping:
ES documents:
Doris Table:
enable_docvalue_scan = false
For ES 5.5:
For ES 6.5 or above:
enable_docvalue_scan = true
For ES 5.5:
For ES 6.5 or above: