hutiefang76 opened a new issue, #4413:
URL: https://github.com/apache/amoro/issues/4413

   ### What happened?
   
   A reachable bracketed IPv6 endpoint fails before connection validation 
because splitting on colons loses its host and port. CommonUtil.telnetOrPing 
throws IllegalArgumentException; the existing KafkaClusterSimpleInfo.validate 
bean uses that helper and also fails.
   
   Expected: reachable bracketed IPv6 endpoints pass, while IPv4, optional 
chroot, fallback and malformed-port rejection remain supported.
   
   ### Affects Versions
   
   master at 061eb724e93592fe87cf44b61af34c1d799f5db6
   
   ### What table formats are you seeing the problem on?
   
   _No response_
   
   ### What engines are you seeing the problem on?
   
   _No response_
   
   ### How to reproduce
   
   1. Open a loopback ServerSocket on ::1 with an ephemeral port p.
   2. Call CommonUtil.telnetOrPing("[::1]:" + p). The current split attempts to 
parse an empty token as the port and throws before connecting.
   3. Set the same endpoint as brokerList on KafkaClusterSimpleInfo and call 
validate; it also fails.
   4. Repeat with /service appended to the endpoint to exercise the optional 
chroot.
   
   ### Relevant log output
   
   ```shell
   
   ```
   
   ### Anything else
   
   Tests exercise real IPv4/IPv6 ServerSockets and the production helper/bean. 
Four of six initial cases fail on the base. Seven final cases pass, including 
the review-discovered empty-port regression; all 15 reactor modules compile and 
Spotless/Checkstyle pass. No deployed Kafka registration flow was exercised. A 
tested fix is ready in hutiefang76/amoro branch 
fix/kafka-ipv6-address-validation.
   
   ### Are you willing to submit a PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's Code of Conduct


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to