ableegoldman commented on code in PR #16265:
URL: https://github.com/apache/kafka/pull/16265#discussion_r1637729519
##########
docs/streams/developer-guide/config-streams.html:
##########
@@ -1017,6 +1022,20 @@ <h4><a class="toc-backref" href="#id14">state.dir</a><a
class="headerlink" href=
this path must be unique for each such instance.</div>
</blockquote>
</div>
+ <div class="section" id="task-assignor-class">
+ <h4><a class="toc-backref" href="#id39">task.assignor.class</a><a
class="headerlink" href="#task-assignor-class" title="Permalink to this
headline"></a></h4>
+ <blockquote>
+ <div>A task assignor class or class name implementing the
+
<code>org.apache.kafka.streams.processor.assignment.TaskAssignor</code>
interface. Defaults to the
+ high-availability task assignor. One possible alternative
implementation provided in Apache Kafka is
+
<code>org.apache.kafka.streams.processor.assignment.StickyTaskAssignor</code>,
which was the default task
+ assignor before KIP-441 and prioritizes stickiness over task
availability. Alternative implementations of
+ the task assignment algorithm can be provided in the classpath of
the Kafka Streams application. This
+ configuration will then be set to the fully qualified class name of
the desired
+ <code>TaskAssignor</code> implementation.
Review Comment:
nit: maybe this is just me, but the wording here feels a bit confusing.
Here's one suggestion for clearing this up but feel free to word it differently:
```suggestion
the task assignment algorithm can be plugged into the application
by implementing a custom <code>TaskAssignor</code> and setting this config to
the name of the custom task assignor class.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
