incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Cheers <>
Subject PUT responds with 201 but GET returns 404
Date Tue, 03 Jul 2012 23:50:46 GMT

I have a question on behaviour I'm seeing POSTing docs to the database but then not always
being able to immediately GET them. Generally it takes 2 attempts for a successful fetch.
I had assumed a POST is synchronous and document would then be immediately available.

Not sure if it makes a difference, delayed_commits is set to false currently. Though I've
tried both settings. I've looked at couch's durability matrix page and also assumed that is
outside the scope of this.

Thanks, Matt


Example output:
Loading key: test-key

PUT 'http://couch:5984/keys/test-key
Updating Key: test-key Response: 201

GET 'http://couch:5984/keys/test-key
Getting Key: test-key Response: 404

PUT 'http://couch:5984/keys/test-key
Updating Key: test-key Response: 201

GET 'http://couch:5984/keys/test-key
Getting Key: test-key Response: 200
Taken 2 attempts to create.


    println "Loading key: ${key}"
    put(key, json)

    def attempts = 1
    while (!get(key)) {
        put(key, json)
    println "Taken ${attempts} attempts to create."

def put(String key, json) {
    def params = [path: "/keys/${key}", body: json]
    def response = client.put(params)
    println "Updating Key: ${key} Response: ${response.status}"

def get(String key) {
    def params = [path: "/keys/${key}"]
    def response = client.get(params).data
    println "Getting API Key: ${apiKey} Response: ${response.status}"

This email (including any attachments) is confidential and may be privileged. If you have
received it in error, please notify the sender by return email and delete this message from
your system. Any unauthorised use or dissemination of this message in whole or in part is
strictly prohibited. Please note that emails are susceptible to change and we will not be
liable for the improper or incomplete transmission of the information contained in this communication
nor for any delay in its receipt or damage to your system. We do not guarantee that the integrity
of this communication has been maintained nor that this communication is free of viruses,
interceptions or interference.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message