You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@james.apache.org by GitBox <gi...@apache.org> on 2021/04/12 04:52:04 UTC

[GitHub] [james-project] chibenwa commented on pull request #377: JAMES-3557 */changes: Fail explicitly when too much entries on a single change

chibenwa commented on pull request #377:
URL: https://github.com/apache/james-project/pull/377#issuecomment-817476106


   > This looks like just a workaround, is there no way to fix this issue to turn into the correct behavior?
   
   No not really. If the chunck is too large, the chunk is too large. The client should use a bigger /changes then.
   
   An alternative would be to , upon insert, generate several smaller changes instead than one big. But I don't like this approach much, to be honnest.


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



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org