Skip to content
This repository has been archived by the owner on May 4, 2023. It is now read-only.

FEATURE REQUEST: Indexing views #29

Closed
marcolz opened this issue Nov 4, 2009 · 5 comments
Closed

FEATURE REQUEST: Indexing views #29

marcolz opened this issue Nov 4, 2009 · 5 comments

Comments

@marcolz
Copy link

marcolz commented Nov 4, 2009

No description provided.

@marcolz
Copy link
Author

marcolz commented Nov 4, 2009

Or documentation about how to do it - If already available.

@rnewson
Copy link
Owner

rnewson commented Nov 4, 2009

An explanation on how it would be possible to index a view would be welcome. I believe it cannot be done, which is why it's not possible.

@marcolz
Copy link
Author

marcolz commented Nov 4, 2009

I guess I'm confused because I found this:

"""
Indexing Strategy

The basics now revolve around a _design/lucene document in your database. Any view defined in this document will be indexed by Lucene. In order to be indexed appropriately you should make sure that all of the emit(key, value) calls specify doc._id as the key.
"""
http://www.davispj.com/2009/01/18/couchdb-lucene-indexing.html

@rnewson
Copy link
Owner

rnewson commented Nov 4, 2009

That is a different (and abandoned) project altogether. :)

@marcolz
Copy link
Author

marcolz commented Nov 4, 2009

Great! Thanks for the replies ; )

This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants