[
https://issues.apache.org/jira/browse/HDDS-15775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18097721#comment-18097721
]
Huang Kuan Hao commented on HDDS-15775:
---------------------------------------
[~smeng] hi I'm trying this. For o3fs, the ticket lists BasicOzoneFileSystem
too, but I don't think a bracketed IPv6 literal can actually reach that code:
java.net.URI rejects o3fs://bucket.volume.[::1]:9862 at the syntax level, so an
o3fs IPv6 OM has to come from config (ozone.om.address), which is already
covered by HDDS-15773. So I'm planning to leave o3fs untouched. Does that sound
right, or is there an o3fs path I'm missing?
> Support IPv6 literal authorities in OzoneFS URI parsing
> -------------------------------------------------------
>
> Key: HDDS-15775
> URL: https://issues.apache.org/jira/browse/HDDS-15775
> Project: Apache Ozone
> Issue Type: Task
> Reporter: Siyao Meng
> Assignee: Huang Kuan Hao
> Priority: Major
>
> ofs://[::1]:9862/path and o3fs://[::1]:9862/... fail because the authority is
> split on every colon.
> - BasicRootedOzoneFileSystem.java:164-175: authority.split(":") yields more
> than two parts for a bracketed IPv6 literal and throws
> IllegalArgumentException (URI_EXCEPTION_TEXT).
> - BasicOzoneFileSystem.java:167-176: same pattern.
> Proposed: parse the authority with an IPv6-aware helper (Guava HostAndPort /
> Hadoop NetUtils) that understands bracketed literals. Add filesystem tests
> that construct and resolve IPv6 authorities.
> Parent epic: HDDS-15763.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
