binarycat0 commented on issue #2419: URL: https://github.com/apache/polaris/issues/2419#issuecomment-3338559696
Hello coleagues, if you'll allow me, I'd like to add my two cents. First of all, it's really great that such a big amount of work has been done and this is a huge achievement 🫶 I recently worked on an issue (#2620) and also noticed this improvement opportunity - to use polaris CLI **without the need** to clone the entire project and install all dependencies. I proposed the same idea to my colleagues and they shared that work is already in progress, which I'm very happy about. ---- I also see this opportunity as a way to deliver **polaris-catalog** CLI and enable using this **SDK** for the Python engineers. To currently use the polaris module as an SDK, you need to do many steps. As a python dev, I would like to have the ability to make this process simpler and more convenient through `pip/pipx`. I mean that after installing the current project, it becomes possible to use the polaris module in Python code. But the current structure is not quite convenient and obvious, I would also suggest slightly changing the directory structure for greater convenience. ``` # now from polaris import catalog from polaris import management # proposed version # from polaris_catalog.sdk import management # from polaris_catalog.sdk import catalog ``` ---- Just to highlight, the short names already booked for other projects not related to Apache Polaris Catalog, like polaris/polaris-cli/polaris-sdk, so it's also required to change the `name` in the `client/python/pyproject.toml` file. Maybe the [polaris-catalog package](https://pypi.org/project/polaris-catalog/) is already prebooked for the Apache Polaris Catalog project ---- If I can help you with any part to make this work completed faster, please let me know. -- 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]
