>>So, for example "trials where >>(parameters['parameter1'] == 10 AND parameters['parameter2'] >= 42)"
Whether this can be accomplished inside CouchDB or not, it should be possible to do inside a Lucene index based off CouchDB data. I don't currently do the right thing for numbers in range queries, but when I fix that this kind of query should return _id,_rev pairs; ../dbname/_fti?q=parameter1:10 AND parameter2:[0 TO 42] the current issue (for my code) is that 0 to 42 is evaluated lexicographically, which is wrong. I have a planned fix but no time this week to commit it. It'll appear at http://github.com/rnewson/couchdb-lucene when it does. I expect the query to evaluate very quickly, even when you change the start and end points (in fact my approach expects you to re-query with different points). B. On Tue, Feb 10, 2009 at 3:34 PM, Chris Anderson <jch...@apache.org> wrote: > On Tue, Feb 10, 2009 at 12:09 PM, Paul Davis > <paul.joseph.da...@gmail.com> wrote: >> >> Trunk has support for streaming writes when a Content-Length header is >> present. Chris Anderson was just working the other day on streaming >> writes to disk in the absence of a Content-Length header. That >> basically means that if your HTTP client sends a content-length >> header, the sky's the limit. If you don't send a Content-Length >> header, you'll be limited by the available RAM on the machine running >> CouchDB until Chris finishes his patch. > > Just to clear up, currently attachment PUTs without Content-Length > headers are rejected. I think that we fixed the RAM buffering issue > after all: > > https://issues.apache.org/jira/browse/COUCHDB-189 (fixed) > > So if you know the length of the attachment, PUT should work for you > no matter how big it is. > > -- > Chris Anderson > http://jchris.mfdz.com >
