apache / apache/rocketmq-flink
why 'nameServerAddress' option unsupported?
- Dominant language
- Java
- Stars
- 174
- Forks
- 104
- PR merge metrics
- No merged PRs in 30d
Description
I'm new to flink and rocketmq, I follow the README steps to execute following sql to create table :
```sql
CREATE TABLE rocketmq_source (
`message` STRING
) WITH (
'connector' = 'rocketmq',
'topic' = 'TestTopic',
'consumerGroup' = 'test',
'nameServerAddress' = '127.0.0.1:18081'
);
```
and then execute following sql :
```sql
select * from rocketmq_source;
```
but I got an error below:
```
[ERROR] Could not execute SQL statement. Reason:
org.apache.flink.table.api.ValidationException: Unsupported options found for 'rocketmq'.
Unsupported options:
nameServerAddress
Supported options:
connector
property-version
rocketmq.client.accessKey
rocketmq.client.message.encoding
rocketmq.client.message.field.delimiter
rocketmq.client.message.length.check
rocketmq.client.message.line.delimiter
rocketmq.client.secretKey
rocketmq.client.timeZone
rocketmq.source.column.error.debug
rocketmq.source.filter.sql
rocketmq.source.filter.tag
rocketmq.source.group
rocketmq.source.pull.rpc.timeout
rocketmq.source.startup.offset.specific
rocketmq.source.startup.offset.timestamp
rocketmq.source.startup.scan.mode
rocketmq.source.stop.offset.timestamp
rocketmq.source.topic
```
so my question is : Why I got this error, I suppose 'nameServerAddress' option already supported as README shows.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the README section that documents the RocketMQ connector options and compare its nameServerAddress entry with the supported-options validation shown in the report. Trace the connector option definitions or entry point responsible for that validation, then verify that the documented SQL either accepts the option or that the README accurately reflects the supported configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- stream-processing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100