-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Cannot list splits for table 'table_name' reading topic 'topic_name' #24783
Comments
Do you face this issue with all topics or a specific topic? Can you test with a small topic? |
Thank you for your response. I will test with a smaller topic and let you know the results. |
I tested with a smaller topic using the following configuration: Table Description: {
"tableName": "small_topic",
"schemaName": "default",
"topicName": "small_topic",
"key": {
"dataFormat": "raw",
"fields": [
{
"name": "kafka_key",
"type": "VARCHAR",
"hidden": "false"
}
]
},
"message": {
"dataFormat": "json",
"fields": [
{
"name": "row_number",
"mapping": "rowNumber",
"type": "BIGINT"
}
]
}
} Topic Data:
{
"rowNumber": 1
} Despite testing with a smaller dataset, the same error persists. Reported Error:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
I am using a Trino Cluster running in Docker to connect Apache Kafka to Oracle Cloud Infrastructure. While attempting to query a Kafka topic (customer), the query fails with the following error:
Error Details
Query ID: 20250123_002229_00000_7d8d6
Error Type: KAFKA_SPLIT_ERROR
Elapsed Time: 79,439 ms
Configuration Details
Kafka Connector Configuration
Kafka Resources Configuration (kafka-configuration.properties)
Kafka Table Description
Kafka Topic Data
Steps to Reproduce
Expected Behavior
Trino should successfully list splits and execute the query against the customer topic.
Actual Behavior
The query fails with a TimeoutException while fetching topic metadata.
Environment Details
Additional Notes
I have verified the following:
Any insights or assistance on resolving this issue would be greatly appreciated!
The text was updated successfully, but these errors were encountered: