In a previous version of Boto, there was a helper class called HiveStep , which made it easy to create a job flow step to complete a Hive job. However, in Boto3, the approach has changed, and classes are generated at runtime from the AWS REST API. As a result, such an auxiliary class does not exist. Looking at the source code of HiveStep , https://github.com/boto/boto/blob/2d7796a625f9596cbadb7d00c0198e5ed84631ed/boto/emr/step.py , you can see that this is a subclass of Step , which is a class with jar args and mainclass properties very similar to requirements in Boto3.
It turns out that all the steps of the workflow in EMR, including Hive, still have to be created from the JAR. Therefore, you can follow Hive steps through Boto3, but there is no helper class to simplify the construction of the definition.
Considering the approach used by HiveStep in a previous version of Boto, you can build the correct definition of the job stream.
Or you can revert to using the previous version of Boto.
source share