Added message cleaner configuration. Added database schema. Added micronaut details for DomainEventDispatcher. Fixed rabbitmq docs. #42
Conversation
| ==== Configuring a cleaner | ||
|
|
||
| Cdc can automatically remove old messages from message table and received_message table. | ||
| Example configuration: |
There was a problem hiding this comment.
Please describe what this configuration does.
Also, please have properties for configuring received_message table too
| ... | ||
| ---- | ||
|
|
||
| If pipeline is specified, pipeline database configuration is used. |
There was a problem hiding this comment.
Why would the user NOT want to specify the pipeline?
There was a problem hiding this comment.
I don't know. But probably we discussed this option when I was working on implementation.
| ... | ||
| ---- | ||
|
|
||
| Full list of configuration properties |
There was a problem hiding this comment.
Something seems to be missing here that explains what EVENTUATE_CDC_CLEANER_C3 is, e.g. eventuate.cdc.cleaner is some root property name, c3 is the name of a specific cleaner.
| @@ -595,6 +595,87 @@ The Eventuate Tram CDC supports `eventuate-tram` and `eventuate-local` | |||
|
|
|||
| |=== | |||
|
|
|||
| ==== Configuring a cleaner | |||
|
|
|||
| Cdc can automatically remove old messages from message table and received_message table. | |||
There was a problem hiding this comment.
This should explain that you configure one or more named cleaners.
Each clean can clean a message table and/or a received_message table.
There was a problem hiding this comment.
ok, I will add that
dartartem
changed the title
| @@ -396,7 +396,7 @@ If polling fails, reader will try again using the specified interval. | |||
| | Pipeline property name | |||
|
|
|||
| | eventuate.database.schema | |||
| | Schema which is listened by the CDC service | |||
| | Schema which is listened by the CDC service (use `NONE` for default from jdbc connection) | |||
There was a problem hiding this comment.
I don't think eventuate.database.schema is used to configure the CDC.
It's used to configure the application/service.
There was a problem hiding this comment.
It is used. Each reader has datasource. But I added info for application.
|
|
||
| In default eventuate images, tables are located in 'eventuate' schema. | ||
| If you created necessary tables (see further) in some custom schema, please specify it in `eventuate.database.schema` property or use value `NONE` for it. | ||
| See <<Single pipeline - Pipeline Properties>> and <<Configuring a pipeline>> |
There was a problem hiding this comment.
Is this a hyperlink? If not, it should be
| If you created necessary tables (see further) in some custom schema, please specify it in `eventuate.database.schema` property or use value `NONE` for it. | ||
| See <<Single pipeline - Pipeline Properties>> and <<Configuring a pipeline>> | ||
|
|
||
| ==== Mysql schema example for eventuate local |
There was a problem hiding this comment.
Capitalization:
- eventuate => Eventuate
- Mysql => MySQL
| ); | ||
| ---- | ||
|
|
||
| ==== Full Database Schema |
There was a problem hiding this comment.
Move these links into the respective sections.
Please use proper links:
* [MySQL schema for ...](...)
|
|
||
| ==== `OFFSET_STORE` table | ||
|
|
||
| When publishing messages to Apache ActiveMQ, RabbitMQ, Redis, the MySql binlog reader records the current binlog position in this table. | ||
|
|
||
| ---- | ||
| CREATE TABLE eventuate.offset_store( |
| @@ -807,16 +896,145 @@ The CDC service requires various infrastructure services including: | |||
| The Eventuate CDC service requires several tables. | |||
| The Eventuate MySQL and Postgres images define these tables. | |||
|
|
|||
|
|
|||
| In default eventuate images, tables are located in 'eventuate' schema. | |||
There was a problem hiding this comment.
typos and capitalization: 'In the default Eventuate images'
dartartem
changed the title
No description provided.