Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support to configure multiple partitioner and encode sequentially #197

Open
daehokimm opened this issue May 31, 2021 · 1 comment
Open

Comments

@daehokimm
Copy link

Hi All :)

TL;DR

When the s3 partition is blunt, athena's query take long time.


In my environment, the s3 sink connector encode partition by FieldPartitioner.
As a result, one of s3 partition has so many objects.
and it cause long time query when using athena.
if s3 sink connector can configure more than one partitioner(like FieldPartitioner + DailyPartitioner), the s3 objects are encoded in detail.

So more than one partitioning is needed. plz support this 🙏

@daehokimm daehokimm mentioned this issue May 31, 2021
6 tasks
@raphaelauv
Copy link

You can write your own partitionner and use it with the confluent connector

Look to the current partitionners present in the repo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants