Skip to content
This repository has been archived by the owner on Jul 20, 2023. It is now read-only.

Support trinodb 351 #59

Closed
shawnzhu opened this issue Jan 18, 2021 · 0 comments · Fixed by #67
Closed

Support trinodb 351 #59

shawnzhu opened this issue Jan 18, 2021 · 0 comments · Fixed by #67
Assignees
@shawnzhu
Labels
enhancement New feature or request

Comments

@shawnzhu
Copy link
Contributor

it will need to support trinodb when upgrading to 351 or higher revision
@shawnzhu shawnzhu added the enhancement New feature or request label Jan 18, 2021
@shawnzhu shawnzhu changed the title Supports trinodb 351 Support trinodb 351 Jan 18, 2021
@shawnzhu shawnzhu self-assigned this Feb 14, 2021
@shawnzhu shawnzhu pinned this issue Mar 14, 2021
@shawnzhu shawnzhu mentioned this issue Mar 30, 2021
Merged
@shawnzhu shawnzhu unpinned this issue Mar 31, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@shawnzhu shawnzhu

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use Trino 354 IBM/trino-db2
1 participant
@shawnzhu