Question

I have defined the following view:

{ "_id":"_design/test",
  "language":"javascript",
  "views":
  { "test": 
    { "map": "function(doc) { for (var k in doc.data) emit(doc.data[k],null);}",
      "options": {"collation":"raw"}
    }
  }
}

When querying the view without any parameters, I get the expected result (sorted as “AB…ab” instead of “aAbB” because I specified a raw collation):

http://localhost:5985/test/_design/test/_view/test

{"total_rows":13,"offset":0,"rows":[
  {"id":"-","key":"A","value":null},
  {"id":"-","key":"B","value":null},
  {"id":"-","key":"C","value":null},
  {"id":"-","key":"D","value":null},
  {"id":"-","key":"E","value":null},
  {"id":"-","key":"F","value":null},
  {"id":"-","key":"a","value":null},
  {"id":"-","key":"b","value":null},
  {"id":"-","key":"c","value":null},
  {"id":"-","key":"d","value":null},
  {"id":"-","key":"e","value":null},
  {"id":"-","key":"f","value":null},
  {"id":"-","key":"g","value":null}
]}

I then use startkey and endkey to ask for the range between B and a, and I expect to receive keys BCDEFa, but instead I receive the following error message:

http://localhost:5985/test/_design/test/_view/test?startkey=%22B%22&endkey=%22a%22

{ "error": "query_parse_error",
  "reason": "No rows can match your key range, reverse your start_key and 
             end_key or set descending=true"
}

Why does it say that no rows can match the key range, when rows B,C,D,E,F and a will match ?

EDIT: I have a single document (revision and ID omitted):

{ "_id": "-", 
  "_rev": "-", 
  "data": [ "A", "B", "C", "D", "E", "F", "a", "b", "c", "d", "e", "f", "g" ] 
}

Answer 1

After looking again through wads of documentation and asking around, it seems that this behavior is unintended. I have submitted a JIRA bug for this. I currently have no general-purpose workaround to suggest, though I have been able to work around the problem in my specific situation.