Uploaded image for project: 'Fluid Engage'
  1. Fluid Engage
  2. ENGAGE-387

CouchDB query keys cannot be guaranteed to be issued in a stable order

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • 0.3b
    • 0.3b
    • Kettle
    • None

    Description

      As noted in ENGAGE-383, we are using plain JSON.stringify to serialise mini-objects which are issued as Couch keys. This does not guarantee to emit the keys in a stable order, although we have generally "been lucky" so far. The breakage of 2 views over the weekend was as a result of an apparently unrelated change which disturbed the order of key serialisation. In order to ensure that the entire system does not unexpectedly break when in production, we need a custom serializer for these structures which guarantees that keys are emitted in the order determined in the map.js function

      For reference, collation rules here:

      http://wiki.apache.org/couchdb/View_collation

      Attachments

        Activity

          People

            colin Colin Clark
            antranig Antranig Basman
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: