-
Notifications
You must be signed in to change notification settings - Fork 35
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
CSV support #175
Comments
Thanks for submitting the issue! We'll probably prioritise a quick spike soon to quantify the efforts, I'll update this thread as we make progress. |
hi @matteofigus Any updates about CSV support? Thanks! |
Hi, This is on our backlog, we plan to start working on it soon. |
Awesome 😃 |
Hello team we are also waiting for CSV support. can you provide some time lines |
Hey guys, we are also interested in the csv topic. Are there any updates yet? |
Hi everyone and thanks for waiting. We are currently working on drafting a PR for that, it should be here next week. It will then take a couple of weeks, at least, for reviewing and testing. I'll provide more details once we have the PR draft. |
Hi @matteofigus, are there any good news ? Thanks ! |
Hi @matteofigus, thank you so much for this project. Are there updates on CSV support? Thank you! |
Hi everyone. Unfortunately I cannot offer timelines for this feature yet. It is on our backlog, but unfortunately it's not a high priority item. If anyone is keen to collaborate, we would be keen to offer mentoring and support to work on a Pull Request. |
Hey @matteofigus, nice meeting you today.
As discussed in the meeting, we currently use CSV rather than Parquet for our data lake objects.
In an ideal world we probably migrate to parquet which would enable us to use this project, but that's currently a project with a lot of unknowns on our side - if s3-find-and-forget supported CSV it would enable us to test out the project on our existing data sets.
We understand that this could result in increased costs and reduced performance vs. parquet - but it would still be helpful at this point.
Thanks!
CC @mmontreuil @nduthoit @dawilliams-wave @aerum15
The text was updated successfully, but these errors were encountered: