use filter query parameter #163

Open
ravelab opened this Issue Jun 27, 2012 · 3 comments

Projects

None yet

2 participants

@ravelab
ravelab commented Jun 27, 2012

Hi, is it possible to use a filter=designdocname/filtername (maybe optional in the .ini file) when requesting change notification so that in many cases the traffic can be greatly reduced? thanks.

@rnewson
Owner
rnewson commented Jun 27, 2012

Nope but it sounds like a neat idea, I'd merge a decent patch. Are you really having issues with the traffic, though? It should all be over the loopback interface usually. Did you put your couchdb-lucene server on a different box to the couchdb server?

B.

On 27 Jun 2012, at 16:30, ravelab wrote:

Hi, is it possible to use a filter=designdocname/filtername (maybe optional in the .ini file) when requesting change notification so that in many cases the traffic can be greatly reduced? thanks.


Reply to this email directly or view it on GitHub:
#163

@ravelab
ravelab commented Jun 28, 2012

I'm not really having issues. I was just thinking that if I need to put a filter (because most changes to the documents don't require reindexing), I probably want to put it as upstream as possible. One concern is that having filter=designdocname/filtername in .ini file feels like a hack because then we can only have one filter. Maybe you have a good approach?

@rnewson
Owner
rnewson commented Jun 29, 2012

I would stick it in the design document and then teach couchdb-lucene to look for it and use it when it calls _changes. e.g,;

"filters": {
"foo":"…"
},
"fulltext": {
"bar": {
"filter":"foo",
"index":" …"
}
}

B.

On 28 Jun 2012, at 18:15, ravelab wrote:

I'm not really having issues. I was just thinking that if I need to put a filter (because most changes to the documents don't require reindexing), I probably want to put it as upstream as possible. One concern is that having filter=designdocname/filtername in .ini file feels like a hack because then we can only have one filter. Maybe you have a good approach?


Reply to this email directly or view it on GitHub:
#163 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment