1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
If it's just the table name, just a job argument and then use the argument in the code.
For something more sophisticated you probably need some parameters and code logic, or just build a SparkSQL query dynamically.
It's not common practice to combine Glue and Athena for the same task (e.g. mapping and saving the data), in this case it sounds like Glue is more suited for that ETL.
Contenus pertinents
- demandé il y a 2 mois
- demandé il y a 7 mois
- demandé il y a 2 mois
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
Glue natively stores the source meta data in glue catalog. Is there a way to customize the crawlers to record target meta data in the same table? If so, what are the steps to do so?
You could use a crawler and then add some of your own metadata, but if you run the table again it can be overriden