adoroszlai commented on PR #9874: URL: https://github.com/apache/ozone/pull/9874#issuecomment-4012779942
> client components should be built using separate target and be published as a separate set of artifacts that can be used by different products They are separate artifacts, which other products can depend on. Client components can also be used from "edge" nodes, where only client-side artifacts are present. Parts of Ozone CLI (`ozone sh`, `ozone fs`, `ozone admin`, etc.) are also considered client components. > what is the intended Freon usage outside of Ozone deployment? Freon is used in tests for at least 3 reasons: - exercise code paths currently only available via Java API, not via regular CLI (this is the hsync scenario I ran into) - as a shortcut for multiple statements (create volume, create bucket, create key in one step) - exercise Freon itself -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
