Thanks for starting this Artur. Thankful that 'apache-polaris' is available for the distribution! For the tool name - I have a slight preference for just 'polaris' but don't have strong opinions one way or the other.
-Travis On Wed, Oct 8, 2025 at 1:10 PM Michael Collado <[email protected]> wrote: > +1 on apache-polaris. Very easy to remember and straightforward. I > personally dislike the "py" prefix on everything - like the J... convention > on things in Java that was common for a while. I know what language I'm > using. You don't need to remind me 😂. But I understand it's a common > convention, so it doesn't bother me too much. > > Mike > > On Wed, Oct 8, 2025 at 10:53 AM artur rakhmatulin < > [email protected]> wrote: > > > Hello everyone, > > Thank you all for attending this discussion. > > > > The “apache-polaris” distribution name is available, so we can use it. I > > also like how it’s structured in the Apache Flink project — a great > > example, thank you for sharing it. > > > > Regarding the shorter name for the tool, I agree that we can keep it the > > same, but I’m a bit concerned about potential naming collisions with > > existing tools. In any case, both “polaris” and “pypolaris” are > acceptable > > options. Personally, I prefer “pypolaris”, as it follows the same naming > > convention used in the Apache Flink project. > > > > @Honah — The project name and the executable tool name can differ; it’s > not > > mandatory for them to match the distribution name. > > So, I don’t think this should be a problem. > > > > > > > > ср, 8 окт. 2025 г. в 17:47, Honah J. <[email protected]>: > > > > > Unfortunately, `pypolaris` is also taken by another project: > > > https://pypi.org/project/pypolaris/#description > > > > > > On Tue, Oct 7, 2025 at 2:15 PM Yufei Gu <[email protected]> wrote: > > > > > > > Thanks for bringing this up! "apache-polaris" as a Pypi repo name > > sounds > > > > good to me. Flink uses the same naming schema: > > > > https://pypi.org/project/apache-flink/. > > > > > > > > Are we still able to use a shorter package name like "pypolaris"? For > > > > example, Flink's package name is pyflink[1]. > > > > > > > > from pyflink.common import Row > > > > > > > > > > > > [1] > > > > > > > > > > > > > > https://nightlies.apache.org/flink/flink-docs-stable/docs/dev/python/table_api_tutorial/ > > > > > > > > Yufei > > > > > > > > > > > > On Tue, Oct 7, 2025 at 10:34 AM Dmitri Bourlatchkov < > [email protected]> > > > > wrote: > > > > > > > > > Hi Anna and All, > > > > > > > > > > > - polaris-catalog - taken > > https://pypi.org/project/polaris-catalog/ > > > > > > > > > > Apparently it is taken by Anna [1] who is a Polaris committer. > > > > > > > > > > Does anyone know previous plans for that project? > > > > > > > > > > [1] https://home.apache.org/phonebook.html?uid=annafil > > > > > > > > > > Cheers, > > > > > Dmitri. > > > > > > > > > > On Tue, Oct 7, 2025 at 6:29 AM artur rakhmatulin < > > > > > [email protected]> wrote: > > > > > > > > > > > Hello everyone! > > > > > > As part of the "Package Python CLI tool in the binary > distribution > > > > #2419" > > > > > > initiative [1], we need to agree on the package name for Apache > > > Polaris > > > > > > Catalog that will be used for publishing to PyPI. > > > > > > The current name "polaris" cannot be used as it's already taken > by > > > > > another > > > > > > package unrelated to Apache Polaris. > > > > > > I've created a separate Github Issue [2] to discuss this matter. > > > > > > > > > > > > Proposed options: > > > > > > - apache-polaris - available > > > > > > - polaris-catalog - taken > > https://pypi.org/project/polaris-catalog/ > > > > > > ... > > > > > > > > > > > > TLDR; > > > > > > ??? Is this a CLI or SDK? > > > > > > The current implementation is not just a CLI tool, but also a > > > library. > > > > > > After the package is delivered to PyPI, users will be able to use > > the > > > > CLI > > > > > > tool as well as import the library into their projects. > > > > > > The CLI tool name is defined through the [project.scripts] > > > > configuration > > > > > in > > > > > > the pyproject.toml file [3] > > > > > > > > > > > > Example: > > > > > > ``` > > > > > > [project.scripts] > > > > > > polaris-catalog-cli = "cli.polaris_cli:main" > > > > > > ``` > > > > > > > > > > > > When installing the package via "pipx install apache-polaris", > the > > > bin > > > > > file > > > > > > will be available in ~/.local/bin/ > > > > > > > polaris-catalog-cli --help > > > > > > > > > > > > This means that to use the CLI, there's no need to clone the > entire > > > > > > project. > > > > > > > > > > > > ??? How does it work now? > > > > > > Currently, to use the CLI you need to clone the entire project > and > > > use > > > > > > ./polaris from the project root directory. When calling > ./polaris, > > > > > > automatic initialization of the Python environment occurs. > > > > > > > > > > > > +-------------------------------------------------------------+ > > > > > > | cd polaris && ./polaris | > > > > > > +-------------------------------------------------------------+ > > > > > > +-------------------------------------------------------------+ > > > > > > | python environment inside ./polaris project dir | > > > > > > | +-------------------------------------------------------+ | > > > > > > | | 1 - check ./polaris-venv | | > > > > > > | +-------------------------------------------------------+ | > > > > > > | v | > > > > > > | +------------------------------------------+ | > > > > > > | | 1.1 - initialize ./polaris-venv through | | > > > > > > | | python3 -m venv | | > > > > > > | +------------------------------------------+ | > > > > > > | +-------------------------------------------------------+ | > > > > > > | | 2 - activate python env ./polaris-venv/bin/activate | | > > > > > > | +-------------------------------------------------------+ | > > > > > > | v | > > > > > > | +------------------------------------------+ | > > > > > > | | 2.1 - install dependencies | | > > > > > > | | ./regtests/requirements.txt | | > > > > > > | +------------------------------------------+ | > > > > > > | v | > > > > > > | +------------------------------------------+ | > > > > > > | | 2.2 - ./poetry install ./client/python | | > > > > > > | +------------------------------------------+ | > > > > > > | +-------------------------------------------------------+ | > > > > > > | | 3 - calling ./polaris -> ./polaris-venv/bin/polaris | | > > > > > > | +-------------------------------------------------------+ | > > > > > > +-------------------------------------------------------------+ > > > > > > > > > > > > > > > > > > [1]: https://github.com/apache/polaris/issues/2419 > > > > > > [2]: https://github.com/apache/polaris/issues/2699 > > > > > > [3]: > > > > > > > > > > > > > > > > > > > > > > > > > > > https://github.com/apache/polaris/blob/main/client/python/pyproject.toml#L45 > > > > > > > > > > > > > > > > > > -- > > > > > > Best regards, Artur Rakhmatulin > > > > > > e-mail: [email protected], > > > > > > telegram: https://t.me/binarycat0 > > > > > > > > > > > > > > > > > > > > > > > > -- > > Best regards, Artur Rakhmatulin > > e-mail: [email protected], > > telegram: https://t.me/binarycat0 > > >
