I added a table to the README with the differences that were called out. I
added some details that I think are worth understanding better. E.g., the
Json layout we added has specific custom functionality we wanted for
supporting key/value pairs and the micrometer annotation was added for some
custo
When I said "migrate", I specifically meant the feature to actually move
the tables to a new source catalog. Polaris as a _path_ to migration
definitely should be a core feature - it's the reason External catalogs are
supported at all. Adding full delegation, IMO, helps fulfill the purpose of
Exter
I think it's really important that we have the functionality to move folks
off of existing catalog solutions be they Hive, Hadoop or what not. I do
think, even with the dependency issues, this should be a core functionality
of Polaris. I think this would make it much easier for folks on non-REST
ca
Hi Yufei
Thanks for scheduling this !
I should be able to join.
For the community, will you be able to record ?
Regards
JB
On Mon, Nov 4, 2024 at 10:40 PM Yufei Gu wrote:
>
> Hi Folks,
>
> I've scheduled a community sync to discuss table maintenance in Polaris
> this Thursday at 9 AM PST. Sin
