Releases: mpareja/gearshaft
Releases · mpareja/gearshaft
v0.15.8: avoid global pg configurations (2022-12-02)
v0.15.7: upgrade dependencies, including pg (2022-12-01)
Highlights
- postgres: upgrade
pg
dependency to version 8.8.0. No significant impact on performance (or subtle improvement).
Commits
- (
b2bf2e3
) package: upgrade pg and uuid - (
c0ef290
) package: upgrade dev dependencies - (
8417f8c
) package: pin message-db while npm package is sorted out - (
535cad8
) tools: add compare-latest-results script - (
15a66ad
) benchmark: new baselines (node 18, machine, message-db 1.3.0) - (
e77ebf8
) package: upgrade pg dependency (w/ before-after benchmarks) - (
6131f2b
) package: update dev dependencies
v0.15.6: expose consumer parameters (2021-03-29)
Highlights
- consumer: expose the configuration parameters used when creating a consumer
Commits
- (
a072de4
) consumer: exposes configuration parameters - (
381e859
) package: upgrade message-db version used for testing - (
2271749
) package: upgrade dev dependencies: pino, dependency-cruiser - (
7a334eb
) package: use simple-git-hooks instead of husky - (
2b8acbd
) package: upgrade systeminformation and migrate existing results format
v0.15.5: upgrade dependencies, including pg (2020-12-26)
Highlights
- postgres: upgrade
pg
dependency to version 8.5.1. No significant impact on performance.
Commits
- (
bda6ae4
) package: upgrade dependencies (including [email protected])
v0.15.4: upgrade dependencies, including pg (2020-10-30)
Highlights
- postgres: upgrade
pg
dependency to version 8.4.2. Performance either improved or remained the same across all benchmarks.
Commits
- (
2d45b8e
) package: upgrade dependencies (including [email protected]), update benchmarks - (
cf5c657
) benchmark: add script and refresh benchmarks
v0.15.3: consumer & retry enhancements (2020-09-11)
Highlights
- consumer: allow specifying identifier without consumer group details. Unique identifiers must be provided when operating multiple consumers on the same stream to ensure consumer positions are tracking distinctly.
- retry: propagate the value returned by the function being retried
Commits
v0.15.2: support custom filters via read (2020-08-07)
Highlights
- message-store: read: following up on the last release which introduced SQL filters when retrieving messages, we've now added support for such filters when reading all messages in a stream.
- message-store: read: addressed an issue reading an entire stream when the global batch size was not specified.
Commits
v0.15.1: support custom filters when retrieving messages (2020-07-28)
Highlights
- message-store: postgres: support custom filtering of messages retrieved via
get
/getCategory
/getStream
.get
/getCategory
/getStream
now accept a SQL fragment via thecondition
option. The SQL fragment is appended to the WHERE clause used to retriving messages viaget_stream_messages
andget_category_messages
.- WARNING: great care must be taken as the
condition
option could be used as a SQL Injection attack vector. - NOTE: Message DB requires the
message_store.sql_condition
setting be configured toon
. Using this feature without activating the configuration option will result in an error. - Thanks go out to sid-360 for contributing custom filtering!
Commits
- (
007239f
) package: upgrade [email protected], [email protected] - (
44f8074
) message-store: no need to grow examplePutCategory API to track stream names - (
a808809
) Merge pull request #4 from sid-360/postgres-get-add-sql-condition - (
4acd378
) message-store: postgres: update getCategory - (
6251830
) message-store: postgres: update examplePutCategory - (
cd4cf39
) message-store: postgres: rename test description - (
9e939d7
) message-store: postgres: update getStream
v0.15.0: entity-store enhancement (2020-07-08)
Highlights
- BREAKING entity-store: fetchRecord now returns a version of
-1
instead ofundefined
when the entity stream in question has no messages. Returning-1
(stream not initialized) is beneficial for handlers that support both initializing a new entity stream and appending to an existing entity stream. Such handlers can simply forwardversion
as theexpectedVersion
for subsequent writes and rest assured that concurrency controls will be enforced for both initial stream writes and existing stream writes.
Commits
v0.14.0: upgrade pg package to v8 (2020-05-18)
Highlights
- BREAKING upgrade
pg
package to v8. Review the minimal breaking changes for details. Minor performance improvements have been observed. - host:
pause
/unpause
/stop
now forward arguments to corresponding runner methods. Custom runners can use the contextual information during theirpause
/unpause
/stop
processing. Runners are not guaranteed to receive arguments since process kill signals do not provide contextual information.
Commits
- (
32a37c5
) package: refresh benchmarks after upgrades - (
06b0362
) README: use newer pg in example - (
1a2205c
) package: upgrade dependencies - (
76deffc
) host: pause/unpause/stop support forwarding arguments to runners - (
81f538d
) README: add link to example project. - (
cf91a28
) consumer: update noop-consumer benchmarks - (
a9399a2
) package: upgrade pg from 7 to version 8 - (
f67ee27
) package: upgrade dev dependencies - (
7e0ff7a
) package: add missing GitHub links - (
28afdff
) message-store: add benchmarks for batched writes