Details
-
Task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
As stated in the write-ups, documentation and discussed in various presentations and meetups, Flume (ng) uses the notion of "Agent" which is different from the previous implementation's use of the term "node". While this has been discussed informally in various forums, we have not been disciplined enough to make this clear in the code itself. Consequently, the code for Flume (ng) still references "node" in many places and is confusing to say the least.
To make the code aligned with the terminology used in design discussions in various forums, I am suggesting that we formally retire the term "node" in favor of the term "agent". This will require non-trivial code and documentation changes. However, not doing it now will increase the cost of fixing this later and add to the confusion of folks transitioning from the prior implementation to current implementation.