Considering the elastic data migration, maybe it is better to use it as an ETL tool, for John is familiar with it. But we also need to spend more time and effort on it, do we have extra energy to take good care of it?
zhangli...@apache.org <zhangli...@apache.org> 于2018年12月17日周一 下午3:16写道： > Hi, > > ShardingSphere need a distributed job framework to async execute > retrying and compensation for Saga transaction. > And in future, ShardingSphere also need a job framework as an ETL tool for > elastic data migration. > I plan including elastic-job[1] as a sub project of ShardingSphere or > could use directly. > > Because elastic-job need more works to do, for example: > > 1. Upgrade quartz for elastic-job's dependency, quartz 2.1.1 is use c3p0 > which is LGPL license. > 2. New features, like sharding rule with elastic-job > > So, I prefer make elastic-job as a sub project of ShardingSphere, If the > idea is fine, I can communicate with company, and begin to prepare SGA, any > suggestion? > > [1] https://github.com/elasticjob/elastic-job-lite > > ------------------ > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > -- Juan Pan (Trista) Apache ShardingSphere
