You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2018/10/31 14:36:54 UTC

[GitHub] ufobat commented on issue #346: _replicate vs _replication API endpoints

ufobat commented on issue #346: _replicate vs _replication API endpoints
URL: https://github.com/apache/couchdb-documentation/issues/346#issuecomment-434711304
 
 
   
   FYI
   ```
   <vatamane> ufobat: try checking  _scheduler/docs/ instead
   <vatamane> _replicate endpoint is to create replications that are not backed by a document from the _replicator database
   <vatamane> also note there is  the http /_replicate endpoint and a _replicator database I think you might be confusing the two
   <ufobat> vatamane, when if i only use _replicator db? 
   <ufobat> i can POST and GET from there?
   <ufobat> i just care about the configruation, not of the replication results/states
   <vatamane> you can create replications by creating documents in the _replicator database
   <ufobat> vatamane, i actually did :-( 
   <vatamane> these replication will persist even after a server is restarted (unlike replication from the _replicate endpoint)
   <vatamane> to check the status of your replication try http://docs.couchdb.org/en/stable/api/server/common.html#scheduler-docs
   <ufobat> because of my confusion i wrote https://github.com/apache/couchdb-documentation/issues/346
   <vatamane> thanks ufobat, I'll update the ticket with more info
   <ufobat> is the scheduler-doc information about which documents in which db where replicated?
   <ufobat> my db is currently empty
   <vatamane> _scheduler/doc allows you to track the state of replications which are backed by a document in a _replicator database
   <ufobat> ah and _scheduler/jobs is for the _replicate api?
   <vatamane> _scheduler/jobs tracks replication jobs that started broth from the _replicate endpoint and by creating documents in the _replicator db
   <ufobat> and this applys also if i have a "custom_replicator" database, because docs says i could use one ( which would fit perfectly for my script approach, cause i wouldnt see other replications that dont belong to me)
   <vatamane> you could use one, yeah, any database that end with the /_replicator suffix will work as a replicator db
   <vatamane> when you query _scheduler/docs you'd have to pass that database name in the path explicitly like say _scheduler/docs/mycustom/_replicator
   <ufobat> i think thats missin in the documentation as well
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services