Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix wrong field path in Elasticsearch ROW type #12286

Merged
merged 1 commit into from
May 9, 2022

Conversation

ebyhr
Copy link
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 martint, Praveen2112 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