2.4.0

Features :

• Supported version options. (#220)
• Upgrade nuget package to .net core 2.2.

Breaking Changes

In order to support the "version isolation" feature, we introduced a new version field in version 2.4.0 to isolate different versions of the message, so this requires some adjustments to the database table structure. You can use the following SQL to add a version field to your database CAP related table.

MySQL

ALTER TABLE `cap.published` ADD Version VARCHAR(20) NULL;
ALTER TABLE `cap.received` ADD Version VARCHAR(20) NULL;

SQL Server

ALTER TABLE Cap.[Published] ADD Version VARCHAR(20) NULL;
ALTER TABLE Cap.[Received] ADD Version VARCHAR(20) NULL;

PostgreSQL

ALTER TABLE cap.published ADD  "Version" VARCHAR(20) NULL;
ALTER TABLE cap.received ADD "Version" VARCHAR(20) NULL;

MongoDb

db.CapPublishedMessage.update({},{"$set" : {"Version" : "1"}});
db.CapReceivedMessage.update({},{"$set" : {"Version" : "1"}});

Bug Fixed:

• Fixed different groups of the same topic name in one instance will cause routing bug. (#235)
• Fixed message presistence bug. (#240)
• Fixed RabbitMQ topic name contains numbers will cause exception bug. (#181)

2.3.1

Features:

• Add Source Link Support
• Upgrade dependent NuGet packages.

Bug Fixed:

• Fixed dashboard messages requeue error. ( #205 )
• Adjustment snowflake workerId to random id.
• Fixed flush unclaer data bug.

2.3.0

In this version, we made some breaking changes for the publisher API, you can see this blog to understand the story behind.

If you have any migration question, please comment in issue #190.

Breaking Changes:

• Removed app.UseCap() from Startup.cs
• Message table primary key data type has been modified to Bigint and non auto-Increment. (#180)
• New publisher Api. (#188)

Features:

• MongoDb supported. (#143)
• Automatic commit transaction. (#191)

Bug Fixed:

• When the transaction fails, the message is still sent. (#118)
• Multiple events in one transaction. (#171)

2.2.5

Features:

• Performance improvement

Bug Fixed:

• Fixed message enqueue exception.
• Fixed Retry processor bugs.
• Fixed Kafka producer exception log without logging when publish message.
• Fixed Incorrect local IP address judgment of IPv6. (#140)
• Fixed DateTime localization format conversion error to sql. (#139)
• Fixed dashboard message page re-requeue and re-executed operate bug. #158
• Fixed SendAsync or ExecuteAsync recursion retries bug. (#160)
• Fixed configuration options of FailedThresholdCallback could not be invoke when the value less then three. (#161)

2.2.4

Because version 2.2.3 was not released to nuget, so released 2.2.4.

2.2.3

Features:

• Improved log output.
• Upgrade nuget packages.
• Support pattern matching for consumer. (#132)

Bug Fixed:

• Fixed exception thrown when terminate the program with Ctrl+C. (#130)

2.2.2

Features:

• Improved log output. #114
• Add default timeout configuration for kafka client.
• Rename configuration options FailedCallback to FailedThresholdCallback.

Bug Fixed:

• Fixed message enqueue exception.
• Fixed retry processor bugs.
• Fixed kafka producer exception log without logging when publish message.

2.2.1

Bug Fixed:

• Fixed message enqueue bug in v2.2

2.2.0

Features:

• Remove database queue mode. #102
• Support for Diagnostics. #112
• Upgrade dependent nuget packages.

Bug Fixed:

• Fixed bug of the FailedRetryCount does not increase when raised SubscribeNotFoundException. #90

2.1.4

Features:

• Remove TableNamePrefix option from MySqlOptions to EFOptions.
• Upgrade nuget package

Bug Fixed:

• Fixed the connection bug of getting message from table. (#83)
• Fixed entityframework rename table name prefix bug. (#84)
• Fixed sql server scripts bug of create table scheme. (#85)
• Fixed thread safety issue about KafkaOptions.(#89)