- Elasticsearch & MySQL Sync Challenge(1)
- Elasticsearch & MySQL Sync Challenge(2): Event Driven
- Elasticsearch & MySQL Sync Challenge(3): Implementation
- Elasticsearch & MySQL Sync Challenge(4): Quality Attributes
- Elasticsearch & MySQL Sync Challenge(5): Redesign
- Load yml file into environment property source
- Bind property source into config model class
The readConcern option allows you to control the consistency and isolation properties of the data read from replica sets and replica set shards. Through the effective use of write concerns and read concerns, you can adjust the level of consistency and availability guarantees as appropriate, such as waiting for stronger consistency guarantees, or loosening consistency requirements to provide higher availability. MongoDB drivers updated for MongoDB 3.2 or later support specifying read concern.
The business database query request is delayed as little as possible because Syncer listening change by Master-slave sync (binlog/oplog).
- For collection field: getter and setter will all be invoked -- this behavior depends on Spring Boot
- If only invoke getter?
- For list and map field, has different behavior:
- list:
list = getList(); list.clear(); list.add(xxx); setList(list);
- map:
map = getMap(); map.add(xxx); setMap(map);
- list:
- For now, mapping document value using
toString()
: {@link XContentBuilder#unknownValue}- java.sql.Timestamp format: 'yyyy-MM-dd HH:mm:ss.SSS'. For now, if you need other format, you have to format it to string by yourself
- Shutdown process
- Producer starter shutdown
- Connector shutdown
- Starter service shutdown
- Consumer starter shutdown
- Output stater shutdown
- Output channel shutdown
- Batch service shutdown
- Filter-output service shutdown
- Output stater shutdown
- Producer starter shutdown