Skip to content
#

kafka

Here are 6,730 public repositories matching this topic...

Language: All
Filter by language
All 6,730 Java 2,323 Python 730 Go 621 Scala 515 JavaScript 380 Shell 336 C# 166 TypeScript 165 Kotlin 147 Jupyter Notebook 128
Sort: Best match
Sort options
Best match Most stars Fewest stars Most forks Fewest forks Recently updated Least recently updated
flink-learning

zhisheng17 / flink-learning

flink learning blog. http://www.54tianzhisheng.cn/ 含 Flink 入门、概念、原理、实战、性能调优、源码解析等内容。涉及 Flink Connector、Metrics、Library、DataStream API、Table API & SQL 等内容的学习案例，还有 Flink 落地应用的大型项目案例（PVUV、日志存储、百亿数据实时去重、监控告警）分享。欢迎大家支持我的专栏《大数据实时计算引擎 Flink 实战与性能优化》

mysql redis elasticsearch streaming kafka spark influxdb rabbitmq clickhouse hbase stream-processing opentsdb loki flink rocketmq
  • Updated Oct 8, 2021
  • Java
signoz

SigNoz / signoz

Open

For new alert channel page, webhook URL field should be made mandatory is slack is chosen as the alert channel

4
pranay01
pranay01 commented Nov 22, 2021

For slack to work as a notification channel, a webhook URL is necessary. Users should not be able to save the alert channel without providing webhook URL.

Users should be prompted to enter webhook URL if they try to save a new alert channel without providing webhook URL
![Image 22-11-2021 at 12 27](https://user-images.githubusercontent.com/504541/142817412-c43cc792-13b9-44d2-a144-070e699329d8.

Read more
good first issue frontend alerts
Find more good first issues

confluentinc / ksql

Find more good first issues
watermill

ThreeDotsLabs / watermill

Open

A comment for the `Message.UUID` lies

1
xorcare
xorcare commented Nov 22, 2021

This comment says that the message ID is optional,
but for SQL transport it is a mandatory attribute,
in turn it causes misunderstanding?

Is it possible to fix it or did I get something wrong?

https://github.com/ThreeDotsLabs/watermill/blob/b9928e750ba673cf93d442db88efc04706f67388/message/message.go#L20
https://github.com/ThreeDotsLabs/watermill/blob/b9928e750ba673cf93d442db88efc04706f6

Read more
help wanted good first issue S
Find more good first issues

fanliang11 / surging

Surging is a micro-service engine that provides a lightweight, high-performance, modular RPC request pipeline. The service engine supports http, TCP, WS,Grpc, Thrift,Mqtt, UDP, and DNS protocols. It uses ZooKeeper and Consul as a registry, and integrates it. Hash, random, polling, Fair Polling as a load balancing algorithm, built-in service governance to ensure reliable RPC communication, the engine contains Diagnostic, link tracking for protocol and middleware calls, and integration SkyWalking Distributed APM

redis microservices kafka apollo rabbitmq consul json-serialization swagger grpc apigateway zookeeper messagepack nlog log4net dns-server kestrel skywalking memorycache protobuffer surging
  • Updated Jun 7, 2021
  • C#

souyunku / DevBooks

2021面试题，Java面试题、JVM面试题、多线程面试题、并发编程、设计模式面试题、SpringBoot面试题、SpringCloud面试题、MyBatis面试题、ZooKeepe面试题r、Dubbo面试题、Elasticsearch面试题、Memcached面试题、MongoDB面试题、Redis面试题、MySQL面试题、RabbitMQ面试题、Kafka面试题、Linux面试题、Netty面试题、Tomcat面试题、Python面试题

mysql python java linux kafka spring rabbitmq jvm netty tomcat zookeeper springboot dubbo springcloud
  • Updated Nov 15, 2021

Improve this page

Add a description, image, and links to the kafka topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the kafka topic, visit your repo's landing page and select "manage topics."

Learn more