Hey everyone, I have the initial PR up in the `polaris-tools` repo.
It has multiple commits for easy review.
https://github.com/apache/polaris-tools/pull/1
Once we have Apache polaris release/nightly build, I will add Apache
polaris integration tests and update the README with polaris examples.
I renamed the repo to https://github.com/apache/polaris-tools
Regards
JB
Le mer. 26 févr. 2025 à 15:22, Dmitri Bourlatchkov a
écrit :
> "polaris-tools" SGTM.
>
> Cheers,
> Dmitri.
>
> On Wed, Feb 26, 2025 at 5:15 AM Jean-Baptiste Onofré
> wrote:
>
> > Yes, we have to keep polaris in the repo n
"polaris-tools" SGTM.
Cheers,
Dmitri.
On Wed, Feb 26, 2025 at 5:15 AM Jean-Baptiste Onofré
wrote:
> Yes, we have to keep polaris in the repo name to clearly state it
> belongs to Polaris (remember we are directly in the apache org
> https://github.com/apache).
>
> polaris-tools is fine for me.
Yes, we have to keep polaris in the repo name to clearly state it
belongs to Polaris (remember we are directly in the apache org
https://github.com/apache).
polaris-tools is fine for me. I honestly think it won't stay there
super long, and these "tools" will probably be used in federated
catalogs
"polaris-tools" sounds good to me. I assume it's not only used by
developers.
Yufei
On Tue, Feb 25, 2025 at 10:56 PM Ajantha Bhat wrote:
> JB mentioned that it has to have `polaris` in the repo name.
>
> How about calling it as `apache/*polaris-dev-tools*`? It can have an
> iceberg catalog mig
JB mentioned that it has to have `polaris` in the repo name.
How about calling it as `apache/*polaris-dev-tools*`? It can have an
iceberg catalog migrator CLI, Delta lake catalog migrator CLI, or something
else in the future as part of this repo.
I don't want the repo to be called just `apache/po
Good point! catalog-migrator sounds good to me.
On Tue, Feb 25, 2025 at 6:08 PM Yufei Gu wrote:
> I'm not sure if we want to limit it to Iceberg only as Polaris starts to
> support generic tables. I guess "catalog-migrator" is short and expressive.
> "polaris-catalog-migrator" is also fine to me
I'm not sure if we want to limit it to Iceberg only as Polaris starts to
support generic tables. I guess "catalog-migrator" is short and expressive.
"polaris-catalog-migrator" is also fine to me, given that the package name
already implies its association with Polaris.
Yufei
On Tue, Feb 25, 2025
iceberg-catalog-migrator sounds good to me!
On Tue, Feb 25, 2025 at 5:23 PM Ajantha Bhat wrote:
> >
> > The Nessie migrator was `iceberg-catalog-migrator`, and "catalogs" does
> > not seem grammatical to me. If I'm grading papers, I'm not a papers
> grader,
> > I'm a paper grader.
>
>
> The orig
>
> The Nessie migrator was `iceberg-catalog-migrator`, and "catalogs" does
> not seem grammatical to me. If I'm grading papers, I'm not a papers grader,
> I'm a paper grader.
The original name, *iceberg-catalog-migrator*, suggests that it supports
migrations between any Iceberg catalogs. Since w
Good point re: grammar, and I'll defer to native speakers on that :)
On Tue, Feb 25, 2025 at 2:45 PM Eric Maynard
wrote:
> The Nessie migrator was `iceberg-catalog-migrator`, and "catalogs" does
> not seem grammatical to me. If I'm grading papers, I'm not a papers grader,
> I'm a paper grader.
>
The Nessie migrator was `iceberg-catalog-migrator`, and "catalogs" does
not seem grammatical to me. If I'm grading papers, I'm not a papers grader,
I'm a paper grader.
The fact that it works with different catalog implementations doesn't
change that, but if we think polaris-catalog-migrator sounds
> Small question, why catalog*s*?
>
>
The tool can migrate any Iceberg catalog to any other Iceberg catalog.
Small question, why catalog*s*?
On Tue, Feb 25, 2025 at 5:51 AM Jean-Baptiste Onofré
wrote:
> Hi folks,
>
> I created the https://github.com/apache/polaris-catalogs-migrator
> repository.
>
> I will work with Ajantha to populate it.
>
> Regards
> JB
>
> On Thu, Feb 20, 2025 at 12:33 PM Jean-Bapt
Hi folks,
I created the https://github.com/apache/polaris-catalogs-migrator repository.
I will work with Ajantha to populate it.
Regards
JB
On Thu, Feb 20, 2025 at 12:33 PM Jean-Baptiste Onofré wrote:
>
> OK, let's move forward then
>
> I will prepare https://github.com/apache/polaris-catalogs
Thanks, everyone, for your interest in the catalog migrator tool!
I'm excited to collaborate with the Apache Polaris community on
contributing to it.
- Ajantha
On Thu, Feb 20, 2025 at 6:04 PM Jean-Baptiste Onofré
wrote:
> OK, let's move forward then
>
> I will prepare https://github.com/apache/
OK, let's move forward then
I will prepare https://github.com/apache/polaris-catalogs-migrator
repository as a transition phase.
> I also support inviting Ajantha as a committer.
That will be a separate discussion with PPMC.
> Still really prefer a separate repository, at least for now. We can a
Hi,
I also support inviting Ajantha as a committer.
Still really prefer a separate repository, at least for now. We can always merge later.
It also makes the "migration to ASF" easier.
The "Nessie Iceberg-catalog-migrator tool" has been built to support migrations from any catalog to
any othe
Hi Dmitri
About "evolution plan", I see the catalog migrator tool evolving as a
set of beans/providers that will be used in both CLI, and some server
features (like federated catalogs or "foreign catalogs").
We should not focus too much on catalog migrator as it is today but
more how it will be to
+1 to accept the catalog migrator tool.
I support inviting Ajantha as a committer.
As to the source location, I tend to think that a separate repo makes sense
with the current state of the code, but I also agree that the overhead of
that may be too much, given that the codebase is small. I'm fine
Thanks JB for driving this!
The tool serves a very specific purpose and is not directly tied to any
specific catalog. CI for it is different. It makes a lot of sense to have it in
a separate GitHub repository - that also eases the migration to the ASF. If
more functionality is added to the migr
Thanks, JB, for coordinating this effort. After briefly reviewing the code
base, I believe it makes sense to put this as a new module within the
existing repo. The module's code size is manageable, and consolidating it
into one repo helps us avoid the extra overhead associated with maintaining
mult
This is great to hear, thanks for helping arrange this!
+1 to having this tool in Polaris and +1 inviting one of the original main
contributors of the code.
I don't feel too strongly about separate repo vs additional module, since I
could see pros/cons of either approach. Would be a bit cleaner t
23 matches
Mail list logo
