Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KC: Connector type unknown is not supported #756

Open
4 tasks done
yeikel opened this issue Jan 7, 2025 · 5 comments
Open
4 tasks done

KC: Connector type unknown is not supported #756

yeikel opened this issue Jan 7, 2025 · 5 comments
Assignees
Labels
area/connect Kafka Connect, its connectors good first issue Up for grabs scope/backend Related to backend changes status/triage/completed Automatic triage completed type/bug Something isn't working

Comments

@yeikel
Copy link
Collaborator

yeikel commented Jan 7, 2025

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

@yeikel yeikel added status/triage Issues pending maintainers triage type/bug Something isn't working labels Jan 7, 2025
@kapybro kapybro bot added status/triage/manual Manual triage in progress status/triage/completed Automatic triage completed and removed status/triage Issues pending maintainers triage labels Jan 7, 2025
@yeikel yeikel changed the title Value 'unknown' for the connector type fails Value unknown for the connector type fails Jan 7, 2025
@yeikel yeikel changed the title Value unknown for the connector type fails Task type unknown is not supported Jan 7, 2025
@yeikel yeikel changed the title Task type unknown is not supported Connector type unknown is not supported Jan 7, 2025
@Haarolean
Copy link
Member

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

@yeikel
Copy link
Collaborator Author

yeikel commented Jan 16, 2025

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
Copy link
Member

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

@Haarolean Haarolean added scope/backend Related to backend changes area/connect Kafka Connect, its connectors good first issue Up for grabs and removed status/triage/manual Manual triage in progress labels Jan 16, 2025
@Haarolean Haarolean moved this to Todo in Up for grabs Jan 16, 2025
@Haarolean Haarolean changed the title Connector type unknown is not supported KC: Connector type unknown is not supported Jan 16, 2025
@yeikel
Copy link
Collaborator Author

yeikel commented Jan 16, 2025

Where is that defined in the source? I can take it

@Haarolean
Copy link
Member

Where is that defined in the source? I can take it

most likely in contract/connect-api.yaml which Is used to build models later via openapi

@Haarolean Haarolean moved this from Todo to In Development in Up for grabs Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/connect Kafka Connect, its connectors good first issue Up for grabs scope/backend Related to backend changes status/triage/completed Automatic triage completed type/bug Something isn't working
Projects
Status: In Development
Development

No branches or pull requests

2 participants