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

[Improve][Connector-V2-kafka] Support read message metadata(key、timestamp、headers) #2960

Closed
3 tasks done
Carl-Zhou-CN opened this issue Sep 30, 2022 · 6 comments
Closed
3 tasks done
Labels

Comments

@Carl-Zhou-CN
Copy link
Member

Search before asking

  • I had searched in the feature and found no similar feature requirement.

Description

subtask of #2755

Usage Scenario

No response

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@ashulin
Copy link
Member

ashulin commented Sep 30, 2022

There is currently no particularly good way to support metadata columns. If metadata columns are required, you may only add one option for each metadata column;

solution proposal for metadata columns: #2490

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

@github-actions github-actions bot added the stale label Oct 31, 2022
@Carl-Zhou-CN
Copy link
Member Author

underway

@stale stale bot removed the stale label Nov 1, 2022
@Carl-Zhou-CN
Copy link
Member Author

Carl-Zhou-CN commented Nov 11, 2022

@ashulin @EricJoy2048
7983ff29b69a13127260c30ae5f446d
This is the schema that we currently support for kafka. I would like to add metadata columns to it. I want to get some support

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

@github-actions github-actions bot added the stale label Dec 17, 2022
@github-actions
Copy link

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.

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