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.

Sign up for GitHub

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

Jump to bottom

PoC _INFO files generation in S3 #37

Closed
dk1844 opened this issue Aug 19, 2020 · 0 comments · Fixed by #38
Closed

PoC _INFO files generation in S3 #37

dk1844 opened this issue Aug 19, 2020 · 0 comments · Fixed by #38
Assignees
@dk1844

Comments

@dk1844
Copy link
Collaborator

dk1844 commented Aug 19, 2020 •
edited
Loading

Enceladus expects to be able to generate _INFO files to be generated in the output directory alongside the spark output.

This feature is originally implemented using HDFS API, for AWS S3, we need to replicate the functionality for S3. Options are:

  • AWS SDK for S3 API (primary option)
  • using temp HDFS location and copying the _INFO file(s) over (fallback option)

The most prominent entry point should be:
AtumImplicits.SparkSessionWrapper(spark) and internally ControlFrameworkState.storeCurrentInfoFile
@dk1844 dk1844 self-assigned this Aug 19, 2020
@dk1844 dk1844 changed the title Info files generation in S3 PoC _INFO files generation in S3 Aug 19, 2020
@Zejnilovic Zejnilovic mentioned this issue Aug 25, 2020
Closed
@dk1844 dk1844 linked a pull request Aug 31, 2020 that will close this issue
AWS S3 support for Atum #38
Merged
@dk1844 dk1844 mentioned this issue Sep 8, 2020
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dk1844 dk1844

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

AWS S3 support for Atum AbsaOSS/atum
1 participant
@dk1844