A question unrelated to this, but if the subtasks that exist in the jobgraph all appear to be one, why is that?
In order to do source scaling, the outputRecords value needs to be non-zero, but since the downstream after the kafka source stream is not separated on the jobgraph, the outputRecords is getting zero, so we explicitly added a keyBy operation to the kafka source stream so that we can intentionally separate them and then calculate the outputRecords value.
(I don’t think this is very good for performance) Is there any other way to ensure that the streams are separated into two at the desired location in the jobgraph?