Aggregation Support for OpenSearch

[mhabib2003]

Is your idea related to a problem? Please describe.
The issue I'm facing is in awswrangler.opensearch._read.py. The conversion from response to dataframe assumes that all relevant information is returned under top_hits. However, for aggregations, this is not true, as there are additional fields in the returned json before arriving at potentially top_hits or other relevant fields (e.g. buckets).

Describe the solution you'd like
I'd like aggregations to be supported in the conversion from response to dataframe. Specifically, it would be nice to at least support top_hits within aggregations.

Thanks in advance!

P.S. Please do not attach files as it's considered a security risk. Add code snippets directly in the message body as much as possible.

[kukushking]

Thanks @mhabib2003 for opening this - we will add top hits within aggregations.

[kukushking]

Hi @mhabib2003 I've opened PR with top hits for aggregations. One thing I would like to get user input on, is in case of multiple aggregations within a single query. Currently I am considering to add a _aggregation_name column to the returned data frame to indicate which aggregation the hit belongs to.

[mhabib2003]

Hi @mhabib2003 I've opened PR with top hits for aggregations. One thing I would like to get user input on, is in case of multiple aggregations within a single query. Currently I am considering to add a _aggregation_name column to the returned data frame to indicate which aggregation the hit belongs to.

Hey, I'm so sorry I never answered this! I was planning on responding the next day, but you were too quick! Thanks so much, I really appreciate it. I think the way you solved this issue should work well. I'm excited to try it out in the next release.

[kukushking]

@mhabib2003 no probs! 3.11.0 was released so feel free to give it a try and give us feedback if there is anything to improve.