cameronlee314 commented on a change in pull request #1008: SAMZA-2174: Throw a
record too large exception for oversized records in changelog
URL: https://github.com/apache/samza/pull/1008#discussion_r289099618
##########
File path: docs/learn/documentation/versioned/jobs/configuration-table.html
##########
@@ -1687,6 +1687,50 @@ <h1>Samza Configuration Reference</h1>
</td>
</tr>
+ <tr>
+ <td class="property"
id="stores-changelog-max-message-size-bytes">stores.<span
class="store">store-name</span>.changelog.max.message.size.bytes</td>
+ <td class="default"></td>
+ <td class="description">
+ This property sets the maximum size of the messages
allowed in the changelog.
+ The maximum allowed value and the default value both
are 1 MB.
Review comment:
I wasn't referring to the 1MB number specifically. It's fine as 1MB or 5MB.
I was referring to the language used of "maximum allowed value". Why is
there a maximum allowed value for this config?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services
