Hi, In FDB world there wouldn't be erlang mesh as far as I can tell. In this situation the `node` field in the response from `/_scheduler/jobs` and `/_scheduler/docs` doesn't make sense.
We could either remove the field or set it to `None`. I propose complete removal. I also propose to establish a formal process to track API changes formally. Sooner or latter we would need to compile list of changes between versions. In case of a rewrite on top of FDB I suspect the archeology process wouldn't be easy. We could create a github issue template which would set necessary labels for example. Best regards, iilyak
