kafka

PHP looks like a less mature OpenTelemetry implementation, but it exists: https://github.com/open-telemetry/opentelemetry-php#installation

If possible, additional instrumentation tutorial for these popular frameworks would be helpful:

1. Zend Framework 3
2. WordPress
3. Silverstripe
4. [Symfony]

https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/servicebus/Azure.Messaging.ServiceBus/MigrationGuide.md

Describe the bug
There are a few functions (AS_MAP, ARRAY_SORT and URL_ENCODE_PARAM for example) that don't do null checks on inputs. We should do null checks because these errors are left uncaught and end up crashing queries. An example of one that has been fixed recently is confluentinc/ksql#8400

Under the hood, Benthos csv input uses the standard encoding/csv packages's csv.Reader struct.

The current implementation of csv input doesn't allow setting the LazyQuotes field.

We have a use case where we need to set the LazyQuotes field in order to make things work correctly.

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

This was seen while attempting to solve an issue last month: we seeked group offsets, but the seek "errored" because the kadm library was expecting all topics and all partitions in the response to be in the same order as the request. Either the order was different, or the response was missing some data.

IIRC, essentially all Kafka responses always are in the order requested and are always compl