getSince implementation makes a multi-couch-db-to-one-elasticsearch-index setup impossible

[maxlath]

getSince takes its seq id from the targeted ElasticSearch index, which is then passed to follow to generated the CouchDB changes feed. Thus, several couch2elastic4sync processes following different CouchDB databases but putting docs to the same ElasticSearch index (typically under different types) would share the same seq id. The result is that only the database with the highest CouchDB seq number gets to trigger a change event

[ryanramage]

good point.

I think I will get the uuid from the source couch (eg found at http://localhost:5984/)
and the source couch db name to form a unique id for that couch database, eg

b896858f43d8b51206b466009997f8ca~dbname

and then store it at

http://elastic:9200/indexname/_mapping/seq~b896858f43d8b51206b466009997f8ca~dbname

That way it would be possible to have many sync processes not interfere with each other.

Thanks for this suggestion

[maxlath]

FYI, it seems that the concept of types will be removed from ElasticSearch >= 6, so the use case of this issue might be discouraged in the future