By using AWS re:Post, you agree to the Terms of Use
/Are partitions advantageous for groupby operations in Glue jobs?/

Are partitions advantageous for groupby operations in Glue jobs?


I have a table with columns A, B, C, D, ..., where A is a partition key. In a Glue job I want to group records of this table by column A. Is there a way to make the glue workers aware of the partitions in A, such that workers do not have to process dataframes created from different partitions in order to speed up the processing time?

1 Answers
answered 4 months ago
  • In my case, the table has maybe in the order of 1e9 lines which can be grouped into around 1e6 groups. Do I understand it right, that I should then start 1e6 Glue jobs for each partition/group in parallel and perform the selection push_down_predicate? This does not sound practical to me, as I assume that it would be better to effieciently use Glue's internal parallelisation.

  • Yeah sorry, I haven't run tests on the scaling of the number of partitions so high with low data, but my assumption is that it scales and using partitions is better since the query you would be making to s3 is using presto to optimize the data grabbed and how it is grabbed with the partitions organization.

    This might help.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions