-
Notifications
You must be signed in to change notification settings - Fork 323
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
Ability to connect and read from S3 #5777
Comments
@radeusgd - can you separate the Redshift and AWS credentials from Database to their own project please (and leave as a branch). |
Radosław Waśko reports a new STANDUP for yesterday (2023-05-02): Progress: Added the missing check and got the pending PR in. Started work on splitting of Redshift to separate AWS project. Created the project, updated build.sbt with build settings for new project; moved Redshift related modules to it. Got stuck on a weird module loading bug. Started legal review; had issues with the sbt-license-report not resolving correctly - updated to the new version and resolver. It should be finished by 2023-05-05. Next Day: Next day I will be working on the same task. Finish the legal review update. Check out the fix for the bug. Add SPI for detection of supported DB backends and a widget setup for |
Radosław Waśko reports a new STANDUP for today (2023-05-04): Progress: Fixing remaining issues on AWS project - finished Legal Review update; fixed the structure; fixed empty schema resulting in wrong URL not detected by JDBC. Added SPI based widget and tested it in the GUI. Tested that we can attempt a Redshift connection (did not test actual connection as I have no redshift instance accessible). Did a small PR ensuring redundant columns are dropped only in Inner join (they are not actually redundant in other modes). Did 1 bookclub (2 missing ones to go). It should be finished by 2023-05-05. Next Day: Next day I will be working on the #6437 task. Improve Non_Unique_Primary_Key error. Work on widgets. Make up missing bookclubs. |
Radosław Waśko reports a new STANDUP for the provided date (2023-05-05): Progress: Updated error handling on Table.join, updated column renaming to add Next Day: Next day I will be working on the #6437 task. Improve Non_Unique_Primary_Key error. Work on widgets. Make up missing bookclubs. |
Want the ability to connect to an S3 bucket and list items within it as if a folder on the local drive.
Should be able to read files from it.
Needs to support AWS Profile and Access Key/Secret Key authentication.
This is a pre-cursor to reading from
enso://
This should be the start of
Standard.AWS
library. Eventually, Redshift should move into here but this is not part of this ticket.This will eventually be followed by
Standard.Azure
etc.The text was updated successfully, but these errors were encountered: