featurebase/http
Travis Turner 95f05ca4d0
WIP: allow translate log entry buffer to grow
In the case where a translate log entry contained
many key/id pairs, it was possible for the read
buffer (which was allocated at 65536 bytes) to
fail to handle it. This happened when the serialized
LogEntry was larger than 65536 bytes.

This PR adds logic which returns a custom error called
ErrTranslateReadTargetUndersized notifying the reader
to reallocate a larger read buffer and try the read
again.

TODO:
- [ ] Add a max buffer size check to prevent this from doubling the
buffer size with no limit.
- [ ] Add tests.
2018-12-18 09:26:26 -06:00
..
client.go Replace the /fragment/data endpoint to support cluster resizing 2018-12-18 08:34:47 -06:00
client_test.go change exists field to _exists 2018-12-17 15:44:50 -06:00
error.go Fix linter issues: vet 2018-07-19 11:37:50 -05:00
handler.go WIP: allow translate log entry buffer to grow 2018-12-18 09:26:26 -06:00
handler_internal_test.go index trackExistence is true by default 2018-10-01 17:45:21 +03:00
handler_test.go Merge branch 'develop' into newpql 2018-06-22 09:11:00 -05:00
translator.go added v2 notation 2018-10-17 17:58:52 -05:00
translator_test.go revert to existing api with panic per jaffee 2018-10-17 10:29:58 -05:00