- Le plus récent
- Le plus de votes
- La plupart des commentaires
Hello,
Could you verify and make sure that your scenario comply with the considerations mentioned in this document - https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-lf-limitations.html
We also may get this error Unable to get table: java.lang.IllegalArgumentException: No enum constant org.apache.hadoop.hive.metastore.TableType.
when EMR cluster missing table filtering permissions from the source lake formation account. If "External data filtering" missing, then it will deny accessing to the S3 locations that are registered with Lake Formation. This is consistent with the error message and my interpretation of it, that EMR possibly has no access to the location in which the table resides. - https://docs.aws.amazon.com/lake-formation/latest/dg/getting-started-setup.html#emr-switch
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a un an
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
I enabled the "external data filtering" option in the Lake Formation application integration settings of the producer account. I provided the session tag value "Amazon EMR" and added the consuming AWS account ID. Unfortunately, still no success. Is EMR serverless actually adding any session tag values when assuming the job runtime role? Or is this feature only working for EMR clusters?
Support for EMR Serverless with Lake formation was introduced from EMR 6.15 but still in preview as mentioned in the document.
Just make sure that you are configuring your EMR Serverless application appropriately.