imbajin commented on issue #319: URL: https://github.com/apache/hugegraph-ai/issues/319#issuecomment-4221141575
> Hi [@imbajin](https://github.com/imbajin), > > I’m interested in working on this task. > > From my understanding, this involves upgrading the HugeGraph server in the CI workflow to version 1.7.x and updating the integration tests to match the newer server behavior, including removing temporary compatibility workarounds. > > Before I start, I’d like to confirm: > > * Should I fully remove all compatibility gates related to the 1.3.0 behavior once tests pass on 1.7? > * Is there any preferred version within 1.7.x to target? > > I’d be happy to take this on. Please let me know if that works. > > Thanks! Hi @Muawiya-contact , after further consideration, let's refine the strategy to handle the breaking changes more cleanly: 1. **Target Version**: Use **1.7.0** as the primary stable version for this update. 2. **Compatibility Strategy**: * **Focus on 1.7**: We will treat version 1.7 as the standard for current API and data structure adaptations (including the storage format changes). * **Clean up Legacy Code**: You can **remove** old compatibility "tricks" and workarounds that were kept for much older versions. We want to keep the codebase clean. * **Version Guard**: Since there are breaking changes (storage/tables) between 1.3 and 1.5/1.7, we should implement a version check. If the detected HugeGraph Server version is **< 1.5**, the client should prompt the user to either **upgrade their server** or use an **older version of py-client (v1.3.x)**. 3. **Key Implementation Details**: * **Breaking Changes**: Note that in post-1.3 versions, the edge structure has changed (e.g., an additional part in the composition). Integration tests need to be adjusted to match these 1.7+ behaviors. * **References**: You can refer to the **Java-Client** repository for how it handled these adaptations, and check **DeepWiki** for specific data structure changes. This approach ensures the best support for the latest server while giving a clear path for legacy users. Let me know if you have any questions! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
