-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using a view filter during a replication doesn't work #37
Comments
so there is likely 1 of 2 issues here either
can you try again but passing a function to the filter instead of a design doc ? |
If I pass in a filter function it works fine:
-> Object {ok: true, start_time: Thu Jun 23 2016 15:47:49 GMT+0300 (EAT), docs_read: 2, docs_written: 2, doc_write_failures: 0…} |
are either of the dbs http dbs or are they all local ones ? |
I've tried replicating to both local and to an external couch with the same
|
I'm seeing this issue also when using Mango queries to filter replication. A work around that might work for some projects is to create a temporary database without crypto enabled, doing a full replication to that, doing the filtered replication between the temporary database and the target database, then destroying the temporary database. However even after the temporary database is destroyed, an attacker might be able to recover it. |
Hi folks! We just published version 4.0 which includes a significant refactor and many different dependencies. Could you try this again and let me know how it goes? I can help you debug from there :) |
If I try and do a replication from a pouchdb with crypto-pouch applied it works fine. But when I then use the option:
{filter:"_view",view:"results"} // results is a view
no documents are transferred.
If I replicate the encrypted db to an unencrypted db, and then do the same replication from the unencrypted db it works fine.
The text was updated successfully, but these errors were encountered: