DanielLeens commented on issue #12434: URL: https://github.com/apache/seatunnel/issues/12434#issuecomment-6059629877
Classification: E / Core REST configuration parsing. Thanks for the HOCON reproduction. I traced the additional path on current dev: `JobInfoService` parses the HOCON body with `ConfigFactory.parseString`, then unconditionally calls `ConfigShadeUtils.decryptConfig`; its `processConfig` map-to-`parseMap` round trip is where a quoted `$systemId` key is reinterpreted as a HOCON path. That makes this a real 3.0 REST regression, not a JSON-only report. #12443 already changes the relevant `ConfigShadeUtils` conversion, so please keep the work in that PR rather than opening a parallel fix. Before it can be considered, add a REST `format=hocon` regression that submits a minimal job containing a quoted `$systemId` FieldMapper key, passes through decryption, and proves the literal key survives. Keep the existing JSON single/batch coverage too. Please also keep the PR scoped to the REST map conversion and the common shade round trip required by this reproduction. `ReadonlyConfig.toConfig` and config-adapter paths are shared API behavior outside this REST call chain; retain either only with direct regression evidence or move them to a separately justified change. #12443 currently has a failing Build and blocked merge state, so this is not fixed or suitable to promise for a specific release yet. -- 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]
