Why client code in the conductor only provide poll one task at once?

[zheyiyi]

Why client code in the conductor only provide poll one task at once?
Conductor server provide batch poll api but In TaskPollexecutor class, we only procide taskClient.pollTask.

    public Task pollTask(String taskType, String workerId, String domain) {
        Validate.notBlank(taskType, "Task type cannot be blank");
        Validate.notBlank(workerId, "Worker id cannot be blank");

        Object[] params = new Object[] {"workerid", workerId, "domain", domain};
        Task task =
                ObjectUtils.defaultIfNull(
                        getForEntity("tasks/poll/{taskType}", params, Task.class, taskType),
                        new Task());
        populateTaskPayloads(task);
        return task;
    }

Can I ask why conductor doesn't provide batch poll client?

[zheyiyi]

tasks/poll/{taskType}

[apanicker-nflx]

The batch poll semantic is on our roadmap and will be implemented in an upcoming version of the client.