kafka
Here are 7,458 public repositories matching this topic...
-
Updated
May 3, 2022 - Java
-
Updated
May 8, 2022 - Java
-
Updated
May 14, 2022 - Java
-
Updated
Apr 29, 2022 - Scala
-
Updated
May 15, 2022 - Java
-
Updated
Apr 23, 2022 - Python
Is your feature request related to a problem? Please describe.
A user in the community Slack wanted to filter out/select items from a JSON array of objects. Given records in the following format:
'[{"type": "AAA", "timestamp": "2021-09-27"}, {"type": "BBB", "timestamp": "2021-09-27"}, {"type": "AAA", "t-
Updated
May 13, 2022 - Go
-
Updated
May 14, 2022 - JavaScript
-
Updated
Apr 28, 2022 - Java
-
Updated
May 12, 2022 - Go
-
Updated
Apr 24, 2020 - Jsonnet
Por Sentry Kafka client (arroyo) tests to Redpanda ducktape tests suite.
-
Updated
May 15, 2022 - Rust
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
-
Updated
Mar 17, 2022 - Java
-
Updated
Apr 15, 2022 - Java
-
Updated
May 15, 2022 - Go
-
Updated
May 15, 2022 - Java
Improve this page
Add a description, image, and links to the kafka topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the kafka topic, visit your repo's landing page and select "manage topics."
I have noticed when ingesting backlog(older timestamped data) that the "Messages per minute" line graph and "sources" data do not line up.
The Messages per minute appear to be correct for the ingest rate, but the sources breakdown below it only show messages for each type from within the time window via timestamp. This means in the last hour if you've ingested logs from 2 days ago, the data is