This is a maintenance release for version 0.9 containing the following improvements:
Enhancements
UI Improvements:
- Enhanced readability of query implementation code displayed in the UI by removing package names.
- Streamlined adapter deployment dialog.
- Added suggestions for adapter names, simplifying data store deployment.
- Improved parsing of comments in SQL queries submitted through the Polypheny-UI.
Adapter and Container Management:
- Each Polypheny instance is now assigned a UUID, used in container names to avoid name collisions when multiple Polypheny instances use the same Docker host.
- Automated port selection and password assignment for containers deployment via Docker.
- All traffic is now tunneled through an encrypted connection.
Bug Fixes
- Resolved remote connection issues with PostgreSQL and MonetDB.
- Fixed a bug with MongoDB adapters during system restart.
- Resolved an issue that prevented interface and adapter changes from saving under certain conditions.
- Fixed a problem related to creating graph namespaces.
Migration Notes
The docker integration is now using three new ports. By default, these are 7001, 7002, and 7003. Make sure to adjust firewall rules if necessary. The old Polypheny Docker Connector container is no longer required and can be deleted.
Due to various internal changes, this version is incompatible with previous versions of Polypheny. For a seamless transition to the new release, we recommend following these steps: If you encounter any issues when starting the new version, rest assured that a straightforward solution is available. Simply delete the .polypheny folder in your user's home directory.
However, since this results in loosing all data and schema, resetting might not be an ideal scenario for everyone. To cater to your enterprise needs, we offer migration support in our paid versions of Polypheny. This feature allows you to smoothly transfer your valuable data and schema to the latest version without any data loss. Moreover, we are constantly striving to improve user experience, and we are happy to share that automatic migration capabilities will be introduced in an upcoming version. This addition will further simplify the migration process, eliminating the need for manual intervention.
Thanks to @gartens for implementing all Docker related changes as well as some of the additional improvements.
Full Changelog: releases/0.9.0...releases/0.9.1
