kafka

This happens occasionally when shutting down the server:

Exception in thread "http-worker-15" java.lang.NullPointerException: null value in entry: exception=null
        at com.google.common.collect.CollectPreconditions.checkEntryNotNull(CollectPreconditions.java:32)
        at com.google.common.collect.ImmutableMap.entryOf(ImmutableMap.java:176)
        at com.google.common.collect.I

Bug description

When saving retention metrics it looks like the process is allocating space for saving the data serially when OK is clicked on the dialog as it blocks for a noticeable period and you feel the application is unresponsive.

Expected behavior

Instead the space creation for data should happen asynchronously and the dialog should return immediately, or at least show a spi

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

Describe the bug
If you try to create a KAFKA formatted source with a BYTES column, the command will return

CREATE STREAM TEST (ID BYTES KEY, b BYTES) WITH (kafka_topic='test', format='DELIMITED');
The 'KAFKA' format does not support type 'BYTES'

This is because the BYTES type is missing [here](https://github.com/confluentinc/ksql/blob/a27e5e7501891e644196f8d164d078672e0feecd

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.

I have this implemented in a custom marshaler now but wondering if it makes sense to push back upstream - when we are integrating with legacy services we find it useful to use the correlation ID as the message ID when first brought into watermill - from there they get sent on headers to subsequent services and work normally.

Its a simple change if it would make sense for other users.

Version & Environment

Redpanda version: (use rpk version):

v21.11.2 (rev f58e69b)

What went wrong?

Accessing the admin API at hostname:9644/v1 fails. On the browser, the request hangs for several minutes (dev tools shows it as a in-progress, waiting for more bytes), before eventually failing (timing out).

wget shows some kind of read error 6.5K into the response:

~~