Skip to content

Fix wrong field path in Elasticsearch ROW type#12286

Merged
ebyhr merged 1 commit intotrinodb:masterfrom
ebyhr:ebi/elasticsearch-nested-timestamp
May 9, 2022
Merged

Fix wrong field path in Elasticsearch ROW type#12286
ebyhr merged 1 commit intotrinodb:masterfrom
ebyhr:ebi/elasticsearch-nested-timestamp

Conversation

@ebyhr
Copy link
Copy Markdown
Member

@ebyhr ebyhr commented May 9, 2022

Description

Fixes #12250

Documentation

(x) No documentation is needed.

Release notes

( ) No release notes entries required.
(x) Release notes entries required with the following suggested text:

# Elasticsearch
* Fix failure when reading not ISO 8601 formatted timestamp values in `row` type. ({issue}`12250`)

@cla-bot cla-bot bot added the cla-signed label May 9, 2022
@ebyhr ebyhr requested review from Praveen2112, martint and phd3 May 9, 2022 03:36
@ebyhr ebyhr merged commit f353101 into trinodb:master May 9, 2022
@ebyhr ebyhr deleted the ebi/elasticsearch-nested-timestamp branch May 9, 2022 07:47
@ebyhr ebyhr mentioned this pull request May 9, 2022
@github-actions github-actions bot added this to the 381 milestone May 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

Trino is not supporting Date type in ElasticDB nested fields

2 participants