-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Issue with reading data from StarRocks (allin1) using Flink SQL on Linux running on Windows10 virtual box #27308
Comments
this is a known issue that the flink connector connects FE and FE returns a HTTP redirection with the internal address of the BE. you can make sure that |
您好,我是林恩伟,你发的邮件我已经收到。
|
I've received your email and will will reply to you as soon as possible after the vacation.————————————This is an auto reply email from QQ Mail.
|
您好,您的邮件已收到,我会尽快给你回复。
|
I tried verifying those ports already using telnet for 8030, 8040, and 8060, and they were all able to connect.
The reason why it said connected to a different name is because of the way I modified etc/hosts, the two names points to the name ip address:
|
can you have a try with our formal release. |
We have marked this issue as stale because it has been inactive for 6 months. If this issue is still relevant, removing the stale label or adding a comment will keep it active. Otherwise, we'll close it in 10 days to keep the issue queue tidy. Thank you for your contribution to StarRocks! |
This was based on the following instructions:
https://docs.starrocks.io/en-us/latest/unloading/Flink_connector
Instead of the StarRocks setup through VMs, I used the StarRocks allin1 on Docker instead, based on the following guide to set up and deploy StarRocks with Docker:
https://docs.starrocks.io/en-us/latest/quick_start/deploy_with_docker
Instead of behaving as the expected behavior in the Flink connector guide, it returned several different errors after multiple attempts using different ports. I have already made sure to change and modify my etc/hosts file to include the IP and DNS names used for StarRocks allin1 as well before hands.
First it failed by trying connection with port 8030 on scan_url, which gave the following error:
8040 connection failed as well:
8060 gives the following issue:
Steps to reproduce the behavior
Expected behavior
The expected behavior of this would be as depicted on the guide, where data is successfully read from StarRocks using Flink SQL.
Real behavior
Instead of behaving as the expected behavior in the guide, it returned several different errors after multiple attempts using different ports.
First it failed by trying connection with port 8030 on scan_url, which gave the following error:
8040 connection failed as well:
8060 gives the following issue:
StarRocks version
The StarRocks version used here is 3.1.0-rc01-64ca37e863
Below are the code used on the Windows Command Prompt:
The text was updated successfully, but these errors were encountered: