prateekm 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_r297857367
##########
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">1000000</td>
+ <td class="description">
+ This property sets the maximum size of the messages
allowed in the changelog.
+ The default value is 1 MB.
+ </td>
+ </tr>
+
+ <tr>
+ <td class="property"
id="stores-expect-large-messages">stores.<span
class="store">store-name</span>.expect.large.messages</td>
+ <td class="default">false</td>
+ <td class="description">
+ This property, when turned on, tells the system to
expect large messages to be put in the stores.
+ It will then look out for any large messages greater
than
+ <a href="#stores-changelog-max-message-size-bytes"
class="property">stores.*.changelog.max.message.size.bytes</a>
+ and throw a SamzaException when it finds one, stating
that the record is too large.
+ In the case of using CachedStore, it will serialize
the message first, validate
+ its size and then cache it if the size is of
permissible limit.
+ This particular case of using CachedStore causes a
performance degradation since
Review comment:
"Note that if enabled retroactively, this may cause a performance regression
due to the pre-caching serialization."
----------------------------------------------------------------
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
