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

protobuf命名冲突警告 #58

Closed
ouqiang opened this issue Jul 29, 2020 · 11 comments
Closed

protobuf命名冲突警告 #58

ouqiang opened this issue Jul 29, 2020 · 11 comments

Comments

@ouqiang
Copy link

ouqiang commented Jul 29, 2020

你好,运行时会提示命名冲突

WARNING: proto: file "EntryProtocol.proto" has a name conflict over com.alibaba.otter.canal.protocol.HEARTBEAT
A future release will panic on registration conflicts. See:
https://developers.google.com/protocol-buffers/docs/reference/go/faq#namespace-conflict

@nanjingfm
Copy link

@ouqiang 我也遇到相同的问题,应该是EntryProtocol.proto中有个枚举值也叫HEARTBEAT

@ouqiang
Copy link
Author

ouqiang commented Jul 30, 2020

HEARTBEAT = 4;

换个名称就可以了

@withlin
Copy link
Owner

withlin commented Aug 3, 2020

这个应该是java那边的主仓库更改过proto文件吧,我这边没更新。

@ouqiang
Copy link
Author

ouqiang commented Aug 7, 2020

java那边的仓库修改proto文件后会同步到这边吗? 会不会跟使用的protoc版本有关。

@withlin
Copy link
Owner

withlin commented Aug 7, 2020

不会,你可以提个pr过来。 proto文件在这里都在这里protocol,java那边没有一个公共的库呢。

@cityiron
Copy link

一样,我也看到这个告警

@kdpujie
Copy link
Contributor

kdpujie commented Apr 14, 2021

请问,这个是还没修复是嘛

@youwen21
Copy link

不算问题,只是警告可正常使用。
要去掉警告自已在本地换个名称是可以的

@kdpujie
Copy link
Contributor

kdpujie commented Apr 15, 2021

不会,你可以提个pr过来。 proto文件在这里都在这里protocol,java那边没有一个公共的库呢。
提了一个pr,你看看呢。主要是把proto文件做了分包处理。如果修改字段会对其他客户端造成影响。
#70

@kdpujie
Copy link
Contributor

kdpujie commented Apr 15, 2021

不算问题,只是警告可正常使用。
要去掉警告自已在本地换个名称是可以的

有些protobuf版本是警告,有些版本就是panic了。详细参考:https://developers.google.cn/protocol-buffers/docs/reference/go/faq

@withlin
Copy link
Owner

withlin commented Apr 16, 2021

/close

@withlin withlin closed this as completed Apr 16, 2021
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

No branches or pull requests

6 participants