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

Support Trino AVRO format access via S3 gateway #2429

Closed
arielshaqed opened this issue Sep 1, 2021 · 3 comments · Fixed by #2557
Closed

Support Trino AVRO format access via S3 gateway #2429

arielshaqed opened this issue Sep 1, 2021 · 3 comments · Fixed by #2557
Assignees
Labels
area/gateway Changes to the gateway bug Something isn't working
Projects

Comments

@arielshaqed
Copy link
Contributor

Currently #2296 causes this to fail -- it expects a particular Content-Type to be returned when detecting an AVRO subtree.

@itaiad200 itaiad200 added this to Backlog in lakeFS via automation Sep 1, 2021
@ozkatz ozkatz added bug Something isn't working contributor area/gateway Changes to the gateway and removed contributor labels Sep 19, 2021
@itaiad200
Copy link
Contributor

@nopcoder make sure to test this one as well.

@itaiad200 itaiad200 moved this from Backlog to Planned in lakeFS Sep 30, 2021
@ozkatz ozkatz moved this from Planned to In progress in lakeFS Sep 30, 2021
lakeFS automation moved this from In progress to Done Oct 17, 2021
@nopcoder nopcoder moved this from Done to In progress in lakeFS Oct 17, 2021
@nopcoder
Copy link
Contributor

move back to in-progress until we verify this one is fix and there are not followup issues we need to open.

@nopcoder nopcoder reopened this Oct 17, 2021
@nopcoder
Copy link
Contributor

table creation, insert and select using AVRO format using Trino works.

lakeFS automation moved this from In progress to Done Oct 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/gateway Changes to the gateway bug Something isn't working
Projects
No open projects
lakeFS
  
Done
Development

Successfully merging a pull request may close this issue.

4 participants