However, in future versions of Mesos (beyond 0.28.2) tasks on the UI are identifiable using their framework name, instead of having to have that information embedded into the task ID. Since this code, that utilizes the frameworkName would then be redundant, we should make it an option on whether or not to include it in the task ID. Namely, the task ID should be a bit more customizable -- adding the ability to toggle on/off inclusion of the framework name in the task ID.
Right now, the Task IDs for a task are determined by the following code.
However, in future versions of Mesos (beyond 0.28.2) tasks on the UI are identifiable using their framework name, instead of having to have that information embedded into the task ID. Since this code, that utilizes the
frameworkNamewould then be redundant, we should make it an option on whether or not to include it in the task ID. Namely, the task ID should be a bit more customizable -- adding the ability to toggle on/off inclusion of the framework name in the task ID.This was realized in discussion of #223