Skip to content

Latest commit

 

History

History
154 lines (84 loc) · 4.85 KB

README.md

File metadata and controls

154 lines (84 loc) · 4.85 KB
Raw

MySQL - ElasticSearch Synchronization

A MySQL-ElasticSearch synchronization tool with Real-Time, No-Lose, One-to-One Relation.

base on alibaba/canal, RxJava.

The Canal is a bin-log parser and subscriber of alibaba

Version

  • 1.0-beta : 2018-09-04

Manuals

中文手册，请点击这里

Requirements

  • Java 1.8 +
  • 2 GB Memory +
  • 2 Core CPU +
  • 100M Free space (for logs)

Features

  • supported ElasticSearch 5.x ~ 6.x.

  • supported No-enable-bin-log MySQL before.

    If MySQL did not enabled the bin-log before, NO PROBLEM, enable it NOW.

    this tool will dumping the history data via "mysqldump".

    See How to work.

  • supported One-to-One relation.

    • Original tables

      • users-table: | id | nickname | xxx |

      • posts-table: | id | user_id | title | content |

    • Use a simple settings to synchronize them all, like:

      • posts-ES-index: | id | user_id | user.id | user.nickname | user.xxx | title | content |

      See Relation.

  • parsing the bin-log's records to synchronize in REAL-TIME, include Create / Update / Delete operations

  • synchronize the relation records in REAL-TIME, Also after them modified.

  • supported multiple primary keys.

  • Backup bin-log position's file

How to work

This tool launchs following these process:

  1. Read Config

  2. Read Bin-log's position file.

    If file exists and the last position exists, skip dump.

  3. Dump the history data via "mysqldump" If the position was not setted.

    • Launch "mysqldump", dump all data to synchronize them to Elastic.

    • And "mysqldump" will returning a new bin-log position when MySQL enabled the bin-log.

    If MySQL do not enable the bin-log, "mysqldump" will not return a position.

    • Dump complete, Goto canal.

  4. Parse the Real-time bin-log via "Canal"

    • Launch the canal with the position.

    • Loop executing:

      1. parse and synchronize the records from bin-log in Real-Time.

      2. Save the newest bin-log position after synchronized

Known issue

  • Do not support the **No-Primary-key's table.

  • If a table's primary key had be modified, like "id", cannot modify the old id to new id in Elastic.

  • If a relation table's primary key had be modified, cannot modify the record to the related index in Elastic.

  • If a column had be added / droped / modified, cannot synchronize.

  • If the settings of tables or relations had be modified, cannot synchronize

Todo

We will Support these features like:

  • Synchronize when Alter table's column (ADD / DROP / MODIFY)
  • Synchronize when the primary key modified
  • Synchronize when the relation's primary key modified
  • Synchronize the Partial columns that you want.
  • Column alias

Similar software

Mysql -> Elastic Search

MySQL(or Oracle) -> Other Driver(include ElasticSearch)

  • DataX [CN]

    A multi-driver synchronization tool, by alibaba. base on canal.

  • tungsten-replicator

    A Enterprise software, supported ES 5

  • maxwell

    MySQL -> maxwell -> json -> kafka -> LogStash(or FileBeat) -> elastic search

Copyright and License

This tool is released under the MIT License

Copyright (C) 2018 Fly-Studio

　　Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

　　The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.