SEZ9 opened a new pull request, #12071:
URL: https://github.com/apache/seatunnel/pull/12071
Close #12067
### Purpose of this pull request
`POST /update-tags` replaces the tag set Zeta uses to decide where a job may
be scheduled, and leaves no trace of having done so. Because `updateAttribute`
replaces the whole map instead of merging into it, a request that omits a tag
silently drops it, and afterwards there is no record anywhere of what the tags
used to be — so "why did this job stop being scheduled onto that node" has no
answer in the logs.
This logs the node address, the previous tag set and the new tag set at
INFO. Every other mutating Zeta operation (job submit, job stop, log level
change) already logs what it did.
### Does this PR introduce _any_ user-facing change?
No. One new INFO log line on the node that handled the request:
```
Node tags updated: node=[localhost]:5801, {group=platform} ->
{group=platform, team=team1}
```
The response body and status are unchanged.
### How was this patch tested?
No new test. The change is a single log statement around the existing
`updateAttribute` call, with no branch and no change to the returned value, so
the existing `RestApiIT` coverage of `/update-tags` exercises it as-is.
To read it yourself on a running cluster, `POST /update-tags` with
`{"group":"platform"}` and then with `{"team":"team1"}`; the second call now
logs the drop of `group` explicitly:
```
Node tags updated: node=[localhost]:5801, {group=platform} -> {team=team1}
```
### Check list
* [x] If any new Jar binary package adding in your PR, please add License
Notice according
[New License
Guide](https://github.com/apache/seatunnel/blob/dev/docs/en/developer/new-license.md)
* [x] If necessary, please update the documentation to describe the new
feature. https://github.com/apache/seatunnel/tree/dev/docs
* [x] If necessary, please update `incompatible-changes.md` to describe the
incompatibility caused by this PR.
--
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]
