Support for CouchDb views

Elastic Stack Elasticsearch
1

For the last year I've been using David Pilato's modified CouchDb River
that supports Views. [1]

Reading a view rather than the whole document greatly reduces the volume of
data that ES has to store/index.

But, it appears that the functionality still hasn't made it into the master
CouchDb River.

But, I see that the CouchDb River now has a filtering capability [2]. If
the purpose of my CouchDb View was to ensure that only one element of my
document got indexed, does Filtering offer an equivalent capability?

Cheers,
Ian

[1]. https://github.com/dadoonet/elasticsearch-river-couchdb
[2]. https://github.com/elasticsearch/elasticsearch-river-couchdb#filtering

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

2

Hey Ian,

You should look at CouchDb filters doc: http://guide.couchdb.org/draft/notifications.html#filters
A filter is IMHO a simple way to say if a document should be indexed or not.
A view is a way to rearrange a document in many other subset.

If you store books in couchDb and each book has an array of chapters.
If you want to index chapters in Elasticsearch (not books), you will probably use a view to split a book in chapters.

That's the main difference I see between filters and views.
Filter -> Yes or No
Views -> from one single doc to many other docs or the opposite or rewrite content of a doc

So you are using my modified river in production? For a year?
That sounds it safe to merge it in official repo now. :wink:

BTW, I merged some changes in my repo about views from Olivier Bornet: https://github.com/dadoonet/elasticsearch-river-couchdb/commit/f8546ab19685a657dc7fdb3b5b2a679f2ca4dcef

I will look at it and some other things I have in my backlog:


Cheers

David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 5 avr. 2013 à 12:21, ian mayo ian@planetmayo.com a écrit :

For the last year I've been using David Pilato's modified CouchDb River that supports Views. [1]

Reading a view rather than the whole document greatly reduces the volume of data that ES has to store/index.

But, it appears that the functionality still hasn't made it into the master CouchDb River.

But, I see that the CouchDb River now has a filtering capability [2]. If the purpose of my CouchDb View was to ensure that only one element of my document got indexed, does Filtering offer an equivalent capability?

Cheers,
Ian

[1]. https://github.com/dadoonet/elasticsearch-river-couchdb
[2]. https://github.com/elasticsearch/elasticsearch-river-couchdb#filtering

You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

3

On Saturday, 6 April 2013 08:26:29 UTC+1, David Pilato wrote:
[...]

If you store books in couchDb and each book has an array of chapters.
If you want to index chapters in Elasticsearch (not books), you will
probably use a view to split a book in chapters.

That's the main difference I see between filters and views.
Filter -> Yes or No
Views -> from one single doc to many other docs or the opposite or rewrite
content of a doc

I guess that in this metaphor, I just wish to index the Title Page (author,
date, title, etc), and ignore the rest of the document.

So, I'm pretty sure I need a view.

So you are using my modified river in production? For a year?
That sounds it safe to merge it in official repo now. :wink:

I'd love to say that, but I can't. It's a development instance (hosted at
Found.no). I suspect it's just indexed a few thousand documents via your
View river.

But, I'd like to do all I can to get make it 'official'. The Found.No
charging structure will change soon, and I'll reluctantly have to move on.
Whilst Found.No were happy to accomodate this modified plugin, it looks
like other providers aren't going to be as flexible. So, getting it into
the core distribution seems my best chance.

Anybody have any suggestions for getting this fork into the 'trunk'?

[...]

David :wink:

Thanks again David,

Ian

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.