-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[Bug] [FLINK SQL] Could not load service provider for table factories. #3415
Comments
wangsan1988
added
Bug
Something isn't working
Waiting for reply
Waiting for reply
labels
Apr 19, 2024
d6b42e62-5693-4d93-8656-61aff01022ad.txt above is the full log file. |
Zzm0809
added
Wont Fix
This will not be worked on
FAQ
Frequently Asked Questions
and removed
Bug
Something isn't working
Waiting for reply
Waiting for reply
labels
Apr 21, 2024
Hello @wangsan1988, thank you for your feedback, but this issue will not be fixed. You can search for keywords in the Issue list to view it. Issues are marked `Wont Fix` 你好 @wangsan1988, 感谢你的反馈, 但是此问题不会被修复,你可以在 Issue 列表中搜索关键字来查看, Issues 标注为 `Wont Fix` 。 |
排查环境 |
算了,还是试试streampark了 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Search before asking
What happened
run the demo job by quick start of offical website .https://dinky.org.cn/docs/next/get_started/quick_experience
get a error : Could not load service provider for table factories. java.util.ServiceConfigurationError: org.apache.flink.table.factories.TableFactory: Provider org.apache.flink.table.planner.StreamPlannerFactory not a subtype.
job submit to yarn is successfully,then get a error : ava.lang.IndexOutOfBoundsException: Index: 0, Size: 0 , getYarnContainerLog
i think "Could not load service provider for table factories." it the root cause ,seem like jars or dependence problem ,but don't know how to fix it.
d6b42e62-5693-4d93-8656-61aff01022ad.txt
What you expected to happen
mate the demo job run
How to reproduce
Anything else
No response
Version
1.0.0
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: