Re: [I] [Improve][Connector-V2][Starrocks-Source]When obtaining data from Starrock, an exception prompt 'Unknown HostException' appears [seatunnel]

[via GitHub]

zhangshenghang commented on issue #10123:
URL: https://github.com/apache/seatunnel/issues/10123#issuecomment-3682012845

   > > [@LiJie20190102](https://github.com/LiJie20190102) Can you add a 
specific implementation plan? Then we can discuss it.
   > 
   > Currently, when obtaining data from starrocks, the query plan is first 
obtained from the FE node, and then the obtained query plan is used as 
parameters, mainly `be_cost` and `be_port`, and distributed to the BE node. 
Finally, the data returned by the BE node is obtained.The main process is as 
follows:
   > 
   > <img alt="Image" width="522" height="335" 
src="https://private-user-images.githubusercontent.com/53458004/528869279-27c3144e-651f-4a2c-9618-230af8995905.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjY0MDg1MTEsIm5iZiI6MTc2NjQwODIxMSwicGF0aCI6Ii81MzQ1ODAwNC81Mjg4NjkyNzktMjdjMzE0NGUtNjUxZi00YTJjLTk2MTgtMjMwYWY4OTk1OTA1LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTEyMjIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUxMjIyVDEyNTY1MVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTVkNzM5MTg4Zjg1NTNhOTNjNTY1MWZiZWFjZGFhMzJkM2E3YzQ4YjZiZGYwZmRlZjA4N2MyYTM2YTEwYzhhM2MmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.ySJmsze1yGzft0I1Obz771TtP-nct76TFBZjBRbo9VU";>
   > However, there may be issues at this point, such as when starrocks is 
deployed in the k8s scenario, if the computing cluster and starrocks cluster 
are not the same cluster, meaning that the computing cluster cannot access 
starrocks' be domain name and `be_port`, an 'Unknown HostException' will be 
thrown。 To make up for the above scenario, my idea is to add a 
`beHostPortMapping` configuration, which is an optional configuration. When the 
computing cluster is able to fully access `be_ host` and `be_ port`, this 
configuration can be ignored; If the computing cluster cannot recognize `be_ip` 
and `be_port`, this configuration can be used to obtain the accessible `be_ip` 
and `be_port`, The improved flowchart is as follows:
   > 
   > <img alt="Image" width="571" height="381" 
src="https://private-user-images.githubusercontent.com/53458004/528870028-fed3c38c-4a9b-4366-99c9-d625cbcd3da2.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjY0MDg1MTEsIm5iZiI6MTc2NjQwODIxMSwicGF0aCI6Ii81MzQ1ODAwNC81Mjg4NzAwMjgtZmVkM2MzOGMtNGE5Yi00MzY2LTk5YzktZDYyNWNiY2QzZGEyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTEyMjIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUxMjIyVDEyNTY1MVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTFhYTY5MzgzMjhiYzk5OGFlZDUwM2E4ZTAzYWE5YTFkMThiNjYxNTY3MTVkYTM2MGJlOTQyZjExNzcwZjdmNGImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.Qdc9tcdy3QRtHZZLQZrhmQQAR0L-K0D5T93Bhi-taDk";>
   
   thanks @LiJie20190102  
   How about handling it like this: when a value is manually specified, we 
directly use the manually specified value, because when you manually specify 
it, the user clearly understands their own usage scenario. There is no need to 
detect again.
   When it is not configured, the previous logic will continue to be used.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@seatunnel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org