I'm using ES in combination with CouchDB and have come across a hiccup that
I haven't managed to solve.
The CouchDB River plugin for ES worked perfectly for me right up until the
point where I started allowing documents to be deleted in my app. The
deletes are visible in Couch's change log, but don't seem to
be propagating to ES. The ES log doesn't seem to contain anything
enlightening and a cursory glance through the plugin source code hasn't
helped. Subsequent writes to CouchDB are picked up correctly and deleting
those docs directly via HTTP works fine.
Is this familiar to anyone or am I going to have to get my debugging pants
on?
strange, I haven't heard of a user noticing that, and did not see something
like that in my tests... . One thing you can do is set in the logging.yml
file river.couchdb to TRACE, it will log all the operations received and
executed from the _changes stream
I'm using ES in combination with CouchDB and have come across a hiccup that
I haven't managed to solve.
The CouchDB River plugin for ES worked perfectly for me right up until the
point where I started allowing documents to be deleted in my app. The
deletes are visible in Couch's change log, but don't seem to
be propagating to ES. The ES log doesn't seem to contain anything
enlightening and a cursory glance through the plugin source code hasn't
helped. Subsequent writes to CouchDB are picked up correctly and deleting
those docs directly via HTTP works fine.
Is this familiar to anyone or am I going to have to get my debugging pants
on?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.