PawasChhokra 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_r289091779
 
 

 ##########
 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.
+                    </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"></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
+                        we end up serializing every time before putting the 
values in the cache.
+                        When this property is turned on, we ignore the value of
+                        <a href="#stores-drop-large-messages" 
class="property">stores.*.drop.large.messages</a>.
+                        The default value for this config is false. When this 
property is not set,
+                        <a href="#stores-drop-large-messages" 
class="property">stores.*.drop.large.messages</a>
+                        defines the behaviour to be executed.
+                    </td>
+                </tr>
+
+                <tr>
+                    <td class="property" 
id="stores-drop-large-messages">stores.<span 
class="store">store-name</span>.drop.large.messages</td>
+                    <td class="default"></td>
 
 Review comment:
   Yes, added.

----------------------------------------------------------------
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:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to