chrislu b463ca1a2f filer replication: compare content changes directly ... Fix https://github.com/seaweedfs/seaweedfs/issues/3714 The destination chunks may be empty. For example, the file is updated and the volume is vacuumed. In this case, the sync would miss the old chunks. This is fine. However, the entry would have correct metadata but missing chunks. For this case, the simple metadata comparison would be wrongly skipping data changes, and the file will stay empty unless file content md5 is changed.		2022-09-20 08:35:10 -07:00
..
azuresink	filer.backup: backup small files if the file is saved in filer (saveToFilerLimit > 0)	2022-08-19 23:00:56 -07:00
b2sink	filer.backup: backup small files if the file is saved in filer (saveToFilerLimit > 0)	2022-08-19 23:00:56 -07:00
filersink	filer replication: compare content changes directly	2022-09-20 08:35:10 -07:00
gcssink	filer.backup: backup small files if the file is saved in filer (saveToFilerLimit > 0)	2022-08-19 23:00:56 -07:00
localsink	refactor: Directory readability (#3665)	2022-09-14 10:11:31 -07:00
s3sink	simplify	2022-08-27 00:21:57 -07:00
replication_sink.go	move to https://github.com/seaweedfs/seaweedfs	2022-07-29 00:17:28 -07:00