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 custom support we wanted aside from what is supported with the default dropwizard metrics support.
https://github.com/collado-mike/polaris/blob/14865a97ad8f790a9992432d79975c05ff5c36fa/polaris-service-quarkus/README.md I think it would be great if others could add to the table with features that would be impacted by the migration and to call out the level of effort in both dropwizard and quarkus. Another possible consideration would be upgrading our Dropwizard dependency to the latest development version. It may be the case that doing so would address some of the targeted features with less effort in migrating. Mike On Tue, Oct 29, 2024 at 5:50 AM Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > Hi folks, > > Following the last community sync meeting, we create a branch > demonstrating use of Quarkus to powered Apache Polaris: > > https://github.com/jbonofre/polaris/tree/QUARKUS > > We still have work to do, but you can already take a look and > experiment (in the polaris-service-quarkus module). > > We added a README.md file to: > 1. Highlight the main differences (in terms of code) between > Dropwizard and Quarkus > 2. To build and run Polaris powered by Quarkus > 3. The list of TODO items > > > https://github.com/jbonofre/polaris/blob/QUARKUS/polaris-service-quarkus/README.md > > If anyone wants to contribute on the branch before creating the PR, > please let me know, I will add you as contributor on the branch. > > Any comments or questions are welcome ! > > Thanks, > Regards > JB >
