You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
EMRFS was implemented internal to EMR's filesystem after s3mper was released with many of the same concepts and features. Overall, the EMRFS implementation is more complete in that it covers all operations whereas s3mper only covers create, delete, and list. The underlying implementation appears to be different at least in how the metadata is stored.
For s3a filesystem, you need to update the aop.xml file to point to the s3a classes (any implementation of the FileSystem interface can be used).
There is currently no property for region, but could be added easily to DynamoDBMetastore.java when creating the client.
I've had multiple people ask about integration, but don't know if they are actively using it. It will work out of the box for spark, but presto uses a new list method not currently covered by s3mper.
Overall, if you have access to EMRFS, I would recommend you use that in lieu of s3mper as it should be more complete and will address consistency issues that s3mper was never intended to resolve.
Is EMRFS a fork a s3mper?
I tried s3mper with hadoop 2.7.1 :
Thx!
The text was updated successfully, but these errors were encountered: