Hello team, Happy new year! We have been experimenting with using Apache SIS within Apache AsterixDB to support EPSG CRS definitions. Currently, each AsterixDB worker node runs an embedded Apache Derby instance within its JVM to service queries requiring CRS information.
Given the recent retirement of the Apache Derby project <https://db.apache.org/derby/#Derby+Retired>, we are evaluating our migration options and have two primary questions: 1. Migration to H2/HSQL: Are there official plans for Apache SIS to migrate its default EPSG metadata provider from Derby to another engine like H2 or HSQL? Specifically, can we use H2 directly with the current version of Apache SIS for EPSG lookups, and has this combination been tested or verified for compatibility? 2. Programmatic Shutdown: Since we run these as embedded instances across many worker nodes, we are looking for a reliable way to programmatically shut down the database instance to free up resources. We noted that H2 offers straightforward ways to trigger a shutdown via code; does Apache SIS provide a standardized hook to manage the lifecycle (specifically the closure) of the underlying EPSG database? We would appreciate any guidance or roadmaps you can share regarding these embedded database transition. Best Regards, Suryaa Charan
