Ma77Ball opened a new issue, #5328: URL: https://github.com/apache/texera/issues/5328
Part of #4070. ### Goal Add human-readable lifecycle/error logging across the amber engine control plane. ### Problem The engine control plane (controller, worker lifecycle, scheduling, recovery/replay, client, network setup) emitted little to no log output, making it hard to follow a workflow's execution or diagnose failures. ### Scope - INFO/DEBUG/WARN/ERROR logging at control-plane boundaries via the `AmberLogging` trait. - No per-tuple/per-message logging on the data hot path. - Non-functional; no behavior change. Branch: `chore/logging-amber-engine` -- 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]
