-
Notifications
You must be signed in to change notification settings - Fork 2
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
Enable block gzip compression example #85
base: master
Are you sure you want to change the base?
Conversation
@@ -0,0 +1,3 @@ | |||
#!/bin/bash -xe | |||
|
|||
sudo aws s3 cp s3://dig-data-registry/hail.jar /usr/lib/spark/jars/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I built the hail.jar from the hail source (it needs to compiled using java 8 since that's what our EMR clusters use) and then uploaded it to S3. We probably need a better location in s3, but I used this one now since it's not in production use. This solution also relies on EMR continuing to put /usr/lib/spark/jars on the classpath.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So for things like this we tend to use s3://dig-aggregator-data/bin/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Magical. For the generation of the hail.jar either we'll want instructions, or probably we'll want something to be put into dig-analysis-data/scripts
which is where I put things that have a specific generation sequence to help in case someone needs to generate or update the file itself.
@@ -0,0 +1,3 @@ | |||
#!/bin/bash -xe | |||
|
|||
sudo aws s3 cp s3://dig-data-registry/hail.jar /usr/lib/spark/jars/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So for things like this we tend to use s3://dig-aggregator-data/bin/
Making this work comes down to specifying the codec when writing from pyspark and also having that codec on the Spark classpath.