[Bug] No mysql-sync-table action in paimon-action-1.3.1.jar
- Dominant language
- Java
- Stars
- 3.4k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 396
Description
### Search before asking
- [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar.
### Paimon version
Hello:
I'm trying to follow the demo for run first application, but I got an error like:
```txt
/app/flink-2.2.0# ./bin/flink run \
./app/paimon-flink-action-1.3.1.jar \
mysql_sync_table \
--warehouse hdfs:///app/paimon/warehouse \
--database ods_db \
--table ods_foo \
--partition_keys pt \
--primary_keys pt,uid \
--computed_column '_month=month(created_at)' \
--mysql_conf hostname=10.0.171.137 \
--mysql_conf username=root \
--mysql_conf password=test01 \
--mysql_conf database-name='mysql_cdc_test' \
--mysql_conf table-name='foo' \
--table_conf bucket=4 \
--table_conf changelog-producer=input \
--table_conf sink.parallelism=4
Usage: [OPTIONS]
Available actions:
copy_files
compact
compact_database
drop_partition
delete
merge_into
rollback_to
rollback_to_timestamp
create_tag
create_tag_from_timestamp
create_tag_from_watermark
delete_tag
expire_tags
replace_tag
reset_consumer
migrate_table
migrate_database
remove_orphan_files
query_service
expire_partitions
mark_partition_done
create_branch
delete_branch
fast_forward
rename_tag
repair
rewrite_file_index
expire_snapshots
expire_changelogs
remove_unexisting_files
clear_consumers
rescale
clone
For detailed options of each action, run --help
------------------------------------------------------------
The program finished with the following exception:
org.apache.flink.client.program.ProgramInvocationException: The main method caused an error: Unknown action "mysql_sync_table".
at org.apache.flink.client.program.PackagedProgram.callMainMethod(PackagedProgram.java:360)
at org.apache.flink.client.program.PackagedProgram.invokeInteractiveModeForExecution(PackagedProgram.java:223)
at org.apache.flink.client.ClientUtils.executeProgram(ClientUtils.java:105)
at org.apache.flink.client.cli.CliFrontend.executeProgram(CliFrontend.java:1017)
at org.apache.flink.client.cli.CliFrontend.run(CliFrontend.java:230)
at org.apache.flink.client.cli.CliFrontend.parseAndRun(CliFrontend.java:1261)
at org.apache.flink.client.cli.CliFrontend.lambda$mainInternal$11(CliFrontend.java:1355)
at org.apache.flink.runtime.security.contexts.NoOpSecurityContext.runSecured(NoOpSecurityContext.java:28)
at org.apache.flink.client.cli.CliFrontend.mainInternal(CliFrontend.java:1355)
at org.apache.flink.client.cli.CliFrontend.main(CliFrontend.java:1323)
Caused by: java.lang.UnsupportedOperationException: Unknown action "mysql_sync_table".
at org.apache.paimon.flink.action.ActionFactory.createAction(ActionFactory.java:76)
at org.apache.paimon.flink.action.FlinkActions.main(FlinkActions.java:38)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:569)
at org.apache.flink.client.program.PackagedProgram.callMainMethod(PackagedProgram.java:343)
... 9 more
```
It seems like not mysql-sync-table action in that jar.
So, am I use wrong version?
thanks.
### Compute Engine
Flink: 2.2.0
### Minimal reproduce step
follow the first step about paimon mysql cdc here: https://paimon.apache.org/docs/1.3/cdc-ingestion/mysql-cdc/
### What doesn't meet your expectations?
Can not be running.
### Anything else?
_No response_
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the MySQL CDC documentation at the linked Paimon 1.3 page and compare its command with the actions listed by paimon-flink-action-1.3.1.jar. Inspect FlinkActions.main and ActionFactory.createAction, then verify whether the documentation or released JAR is inconsistent. Done means the documented first-step command runs with the stated version, or the version requirement and correct command are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100