You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if this is the right place to ask, but given the tight integration Dreyfus/Clouseau provide between CouchDB/Lucene, it would be nice to somehow have list functions work with search indexes.
Something like adding these endpoints: /db/_design/design-doc/_search_list/list-name/index-name /db/_design/design-doc/_search_list/list-name/other-ddoc/index-name
Looking at the protocol, it seems like it wouldn't require any changes to the query server? Object passed in head and objects returned by getRow would be slightly different, but the spirit is the same. In fact many list functions designed for regular views would work unchanged (e.g., those that work on getRow().doc).
Does this seem feasible?
The text was updated successfully, but these errors were encountered:
I don't know if this is the right place to ask, but given the tight integration Dreyfus/Clouseau provide between CouchDB/Lucene, it would be nice to somehow have list functions work with search indexes.
Something like adding these endpoints:
/db/_design/design-doc/_search_list/list-name/index-name
/db/_design/design-doc/_search_list/list-name/other-ddoc/index-name
Looking at the protocol, it seems like it wouldn't require any changes to the query server? Object passed in
head
and objects returned bygetRow
would be slightly different, but the spirit is the same. In fact many list functions designed for regular views would work unchanged (e.g., those that work ongetRow().doc
).Does this seem feasible?
The text was updated successfully, but these errors were encountered: