nickva commented on PR #4291:
URL: https://github.com/apache/couchdb/pull/4291#issuecomment-1486220073

   > * Nouveau endpoints return 404 if disabled and no attempt is made by the 
nouveau erlang app to contact the JVM side for background indexing.
   > * update=true|false is supported but stable=true|false is not. nouveau 
always sorts by _id as the tie-breaker so the instability that clouseau 
exhibits is much reduced.
   > * mango integration is done.
   > * indexes are deleted if nouveau is up when the database is deleted (same 
as dreyfus/clouseau)
   > * nouveau indexes are independent, same as dreyfus
   
   The idea is to have some basic coverage for those cases and others 
mentioned. If mango integration breaks, we'd want to find out, same for 
`update=false` etc. Indexes are independent but it's a good idea to actually 
test more than one at a time. We had a recent mishap with replication jobs 
unintentionally become singletons.
   
   > * I've not yet written a new _search_cleanup endpoint but the java side 
supports it (and is regularly exercised)
   > * include_docs=true not yet implemented (the README says so)
   
   I saw the README, but wasn't sure it was current with the latest update as 
it doesn't mention Lucene 4 at all.  No worries about cleanup and include_docs, 
it can implemented later.
   
   > * not sure what you mean specifically by "Collation (sort order) checks."
   
   Is there any support for altering result sort order. Going by README it 
mentioned both sorting and facets.
    For collation support, it would be checking if unicode data can be indexed 
and returned and if there is some normalization (NFD/NFC) or a way to set a 
locale. It's fine if there isn't, but users will at some point pass non-ASCII 
encoded data so it would be good to assert what happens in that case.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to