FANNG1 commented on PR #11060: URL: https://github.com/apache/gravitino/pull/11060#issuecomment-4485567694
Current issues after upgrading Lance Namespace to 0.7.x: 1. CreateTable does not handle the new 0.7.x REST parameters. In 0.7.x, properties and storage_options are passed as JSON-encoded query parameters, but the current server side still only follows the old behavior, so values sent by new clients will be ignored. 2. DescribeTable does not handle check_declared. In 0.7.x, check_declared is passed as a query parameter, and the response should populate is_only_declared when requested. Currently this is not parsed/returned. 3. DeclareTable should preserve/use request.properties and return the new response fields consistently if supported, especially properties and managed_versioning. From the client compatibility side, additive response fields should be safe. I checked the Lance generated clients: Java disables FAIL_ON_UNKNOWN_PROPERTIES, Rust serde models do not use deny_unknown_fields, and Python generated models only extract known keys in from_dict. So older clients should ignore these new response fields instead of failing. The main compatibility gap is server-side request handling: after this dependency upgrade, the REST server should accept and process the new 0.7.x request parameters rather than silently dropping them. -- 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]
