augment and streamline export functionality #347
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #338
Explanation
exportsfolder within Airflow (and updating.gitignoreand anddocker_compose.ymlaccordingly) so that data marts are exported locally, in addition to on S3 (if destination bucket URI is specified).s3fslibrary torequirements.txtto allow for more streamlined writing of files to S3 (described below)pandas(whens3fsis installed) to write files (CSV, Parquet, etc.) directly from a DataFrame to an S3 bucket (no need to write to local file then copy to bucket).export_martsDAG writes to.parquetformat by default (but I left commented-out lines for writing to CSV for easy editing, if desired).pandasdefault use of environment variables for AWS authentication (no need to explicitly pull the keys from the environment then pass them to boto/pandas/etc).docker_compose.ymlfile to remove unnecessary references to AWS environment variables. Simply naming them appropriately in the .env file (example below) is all that's required.Tests
Successfully ran
export_martsDAG in Airflow, noting the files were written properly to both the local exports directory, as well as an S3 bucket.