KC: Connector type `unknown` is not supported

[yeikel]

Issue submitter TODO list

• I've looked up my issue in FAQ
• I've searched for an already existing issues here
• I've tried running main-labeled docker image and the issue still persists there
• I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

The UI fails to process the Kafka Connect response and the Kafka connect UI page does not load

Expected behavior

No response

Your installation details

d40fc30

Steps to reproduce

Try to parse the following Kafka Connect response

    "TestConnector": {
        "status": {
            "name": "TestConnector",
            "connector": {
                "state": "FAILED",
                "worker_id": "redacted",
                "trace": "org.apache.kafka.connect.errors.ConnectException: Failed to find any class that implements Connector and which name matches \n"
            },
            "tasks": [
                {
                    "id": 0,
                    "state": "FAILED",
                    "worker_id": "redacted",
                    "trace": "....."
                }
            ],
            "type": "unknown"
        }
    },

Notice the "type": "unknown"

Screenshots

No response

Logs

at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1357)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:440)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:868)
at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:799)
at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:501)
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:399)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:1583)
Caused by: com.fasterxml.jackson.databind.exc.ValueInstantiationException: Cannot construct instance of `io.kafbat.ui.connect.model.Connector$TypeEnum`, problem: Unexpected value 'unknown'
at [Source: REDACTED (`StreamReadFeature.INCLUDE_SOURCE_IN_LOCATION` disabled); line: 1, column: 4287] (through reference chain: io.kafbat.ui.connect.model.Connector["type"])
at com.fasterxml.jackson.databind.exc.ValueInstantiationException.from(ValueInstantiationException.java:47)
at com.fasterxml.jackson.databind.DeserializationContext.instantiationException(DeserializationContext.java:2015)

Additional context

No response

[Haarolean]

How can it even be unknown? AFAIK it's either sink or source

[yeikel]

How can it even be unknown? AFAIK it's either sink or source

I think that it can be unknown if the connector jar is deleted

1. Create a connector
2. Uninstall the connector from the deployment, but don't delete it in Connect yet
3. Redeploy

[Haarolean]

How can it even be unknown? AFAIK it's either sink or source

I think that it can be unknown if the connector jar is deleted

1. Create a connector
2. Uninstall the connector from the deployment, but don't delete it in Connect yet
3. Redeploy

I guess we could just update the enum in this case