-
Notifications
You must be signed in to change notification settings - Fork 242
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[FEA] create AWS EMR 3.0.1 shim #905
Comments
It's great to know spark-rapids is going to support EMR, is there an ETA of 0.3.0? |
We are working to see if we can get the 0.2.0 plugin on EMR 6.2.0, which should be available in November / December. |
Cloudera Spark 3 release also runs on 3.0.1 so currently I run into:
|
thanks for reporting this, we actually have a separate issue to make the version parsing better - #409 We did add a config that lets the user override the shim if you know it will work. Its marked as an internal config because the user should know what they are doing because if the shim they specify doesn't work things will likely fail. It depends on if each vendor made internal Spark changes. |
cheers that got it to boot but as you said there will be no guarantees that something won't break somewhere. How can I validate? |
You can run the integration tests in your environment (instructions here: https://github.com/NVIDIA/spark-rapids/tree/branch-0.3/integration_tests ). We are going to work with Cloudera to ensure we are compatible in their environment. |
Okies I'm with Cloudera if you need any help finding people |
I confirmed with our Cloudera contact that CDS 3.0 is basically running Spark 3.0.1, so our plugin will work fine. The workaround mentioned above will work for now. Longer term we will build a shim layer for Cloudera so the workaround is not required. |
filed #951 to track that |
…IDIA#905) Signed-off-by: spark-rapids automation <70000568+nvauto@users.noreply.github.com>
Is your feature request related to a problem? Please describe.
Add a shim layer for aws EMR being based on spark 3.0.1
The text was updated successfully, but these errors were encountered: