Skip to content

KAFKA-10326 Both serializer and deserializer should be able to see th…#9102

Merged
guozhangwang merged 5 commits intoapache:trunkfrom
chia7712:KAFKA-10326
Oct 1, 2020
Merged

KAFKA-10326 Both serializer and deserializer should be able to see th…#9102
guozhangwang merged 5 commits intoapache:trunkfrom
chia7712:KAFKA-10326

Conversation

@chia7712
Copy link
Copy Markdown
Member

https://issues.apache.org/jira/browse/KAFKA-10326

Committer Checklist (excluded from commit message)

  • Verify design and implementation
  • Verify test coverage and CI build status
  • Verify documentation (including upgrade notes)

@chia7712
Copy link
Copy Markdown
Member Author

EosBetaUpgradeIntegrationTest is flaky... retest this please

Copy link
Copy Markdown

@abbccdda abbccdda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are there any serde use cases that require client id?

@chia7712
Copy link
Copy Markdown
Member Author

chia7712 commented Aug 1, 2020

Are there any serde use cases that require client id?

I observed this issue when we are removing custom client id config. It causes error as the metrics of our serde is encoded with client id.

Copy link
Copy Markdown

@abbccdda abbccdda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The change makes sense to me. Will also let @guozhangwang take a look. Btw, I don't think this is an improvement rather than a bug, as we don't have any guarantee to see client id in serdes before.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/originals/copyWithOverride?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will copy that

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have updated the method name.

@chia7712
Copy link
Copy Markdown
Member Author

chia7712 commented Aug 1, 2020

Btw, I don't think this is an improvement rather than a bug, as we don't have any guarantee to see client id in serdes before.

There is another reason. We do pass generated client id to metric reporter. It seems to me all plugins should see consistent props.

@guozhangwang
Copy link
Copy Markdown
Contributor

This change makes sense to me, thanks @chia7712

One (very) minor thing is that, enableAutoCommit may also be overridden when passing into the coordinator object, i.e. the value read from ConsumerConfig may be different from what's actually used. I'm not too worry that this would be leveraged by serde but just want to bring this up.

@chia7712
Copy link
Copy Markdown
Member Author

chia7712 commented Aug 3, 2020

@guozhangwang thanks for reviews

One (very) minor thing is that, may also be overridden when passing into the coordinator object, i.e. the value read from ConsumerConfig may be different from what's actually used. I'm not too worry that this would be leveraged by serde but just want to bring this up.

Let me address it to make consistent configs for all plugins.

@chia7712
Copy link
Copy Markdown
Member Author

chia7712 commented Aug 4, 2020

org.apache.kafka.clients.admin.KafkaAdminClientTest.testMetadataRetries is traced by #9091 and EosBetaUpgradeIntegrationTest.shouldUpgradeFromEosAlphaToEosBeta[true] is flaky. retest this please

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems beyond the scope of this PR. Why do we also need to let deserializer see whether given consumer instance is auto commit enabled?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This flag is included by reason of this comment #9102 (comment)

I’m ok to revert it if it is overkill

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for the delay, I suggest we revert this part to properly scope this PR.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@abbccdda thanks for suggestion. I have reverted it.

@chia7712
Copy link
Copy Markdown
Member Author

@guozhangwang @abbccdda More comments?

@chia7712
Copy link
Copy Markdown
Member Author

chia7712 commented Sep 2, 2020

@guozhangwang @abbccdda ping ~

@guozhangwang
Copy link
Copy Markdown
Contributor

I took a quick look and it lgtm. @abbccdda If your pass is good please feel free to merge.

@chia7712
Copy link
Copy Markdown
Member Author

@abbccdda ping~

@chia7712
Copy link
Copy Markdown
Member Author

rebase to trigger new QA

@guozhangwang guozhangwang merged commit b8090ad into apache:trunk Oct 1, 2020
@guozhangwang
Copy link
Copy Markdown
Contributor

I've merged it to trunk and marked fix version as 2.7, thanks a lot for your contribution @chia7712 !

@chia7712 chia7712 deleted the KAFKA-10326 branch March 25, 2024 15:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants