You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@inlong.apache.org by GitBox <gi...@apache.org> on 2021/07/28 11:59:28 UTC
[GitHub] [incubator-inlong] dockerzhang opened a new issue #1309: [INLONG-720] Support Kafka
dockerzhang opened a new issue #1309:
URL: https://github.com/apache/incubator-inlong/issues/1309
<p>InLong only supports TubeMQ now, we can support using Kafka to extend its usage scenario.</p>
<i>JIRA link - <a href="https://issues.apache.org/jira/browse/INLONG-720">[INLONG-720]</a> created by dockerzhang</i>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@inlong.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [incubator-inlong] walkhan commented on issue #1309: [INLONG-720] Dataproxy Support Kafka
Posted by GitBox <gi...@apache.org>.
walkhan commented on issue #1309:
URL: https://github.com/apache/incubator-inlong/issues/1309#issuecomment-1072074526
@dockerzhang 你好！针对Dataproxy 对Kafka的支持，我觉着是有必要的。kafka因为是绝大公司在生产使用的。另外manager端界面上也是需要支持，毕竟界面配置更符合现在的技术融合了。
另外，我们这边场景涉及到binlong,埋点日志及上游提供的http数据。
通过一段时间大概调研了下inlong，这种消息队列的同步也进一步减少了各种组件的维护。不愿意使用Pulsar的原因，是因为公司层面还觉着Pulsar当前不是特别稳定，不愿意冒哪个风险，毕竟kafka已经相当成熟了。
所以建议社区，能将kafka尽快支持Dataproxy 和manager。这样对社区产品的使用上也会有更多的用户参与进来。
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@inlong.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [incubator-inlong] walkhan commented on issue #1309: [INLONG-720] Dataproxy Support Kafka
Posted by GitBox <gi...@apache.org>.
walkhan commented on issue #1309:
URL: https://github.com/apache/incubator-inlong/issues/1309#issuecomment-1072074526
@dockerzhang 你好！针对Dataproxy 对Kafka的支持，我觉着是有必要的。kafka因为是绝大公司在生产使用的。另外manager端界面上也是需要支持，毕竟界面配置更符合现在的技术融合了。
另外，我们这边场景涉及到binlong,埋点日志及上游提供的http数据。
通过一段时间大概调研了下inlong，这种消息队列的同步也进一步减少了各种组件的维护。不愿意使用Pulsar的原因，是因为公司层面还觉着Pulsar当前不是特别稳定，不愿意冒哪个风险，毕竟kafka已经相当成熟了。
所以建议社区，能将kafka尽快支持Dataproxy 和manager。这样对社区产品的使用上也会有更多的用户参与进来。
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@inlong.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org