The steps I take to create custom mapping on a couchdb database:
Create a new couchdb called test_db
Add a document with _id - user_id
Create index called 'custom _index'
Create custom mapping - very basic for the time being for testing purpose
( {'properties': {'last_name': {'type': 'string'}}})
Put this mapping on custom index.
Now create my river using custom_index
Add another document with _id - user_id_2 to my couchdb.
Now when I look at the status of my index, its taken my custom mapping
correctly -all good, however when I query it it only shows the doc that was
added after the river was created. Am I right in assuming that the river on
setup should find all the existing docs? Clearly on river creation with
dynamic mapping the index picks up all the existing docs. What I am doing
differently?
I don't think the issue is related to your mapping. I have never used
the CouchDB river, but it seems like the river will only pick up new
changes. It is probably scanning the change log (or whatever the CouchDB
equivalent is called).
The steps I take to create custom mapping on a couchdb database:
Create a new couchdb called test_db
Add a document with _id - user_id
Create index called 'custom _index'
Create custom mapping - very basic for the time being for testing purpose
( {'properties': {'last_name': {'type': 'string'}}})
Put this mapping on custom index.
Now create my river using custom_index
Add another document with _id - user_id_2 to my couchdb.
Now when I look at the status of my index, its taken my custom mapping
correctly -all good, however when I query it it only shows the doc that was
added after the river was created. Am I right in assuming that the river on
setup should find all the existing docs? Clearly on river creation with
dynamic mapping the index picks up all the existing docs. What I am doing
differently?
CouchDb river get all _changes from a given point (sequence).
When you start the river the first time, no sequence is defined so it should get all existing document.
Can you gist a curl recreation with all commands you did (create db, add doc, create river, add doc, search)?
--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 2 mars 2013 à 02:33, Ivan Brusic ivan@brusic.com a écrit :
I don't think the issue is related to your mapping. I have never used the CouchDB river, but it seems like the river will only pick up new changes. It is probably scanning the change log (or whatever the CouchDB equivalent is called).
The steps I take to create custom mapping on a couchdb database:
Create a new couchdb called test_db
Add a document with _id - user_id
Create index called 'custom _index'
Create custom mapping - very basic for the time being for testing purpose ( {'properties': {'last_name': {'type': 'string'}}})
Put this mapping on custom index.
Now create my river using custom_index
Add another document with _id - user_id_2 to my couchdb.
Now when I look at the status of my index, its taken my custom mapping correctly -all good, however when I query it it only shows the doc that was added after the river was created. Am I right in assuming that the river on setup should find all the existing docs? Clearly on river creation with dynamic mapping the index picks up all the existing docs. What I am doing differently?
Hi guys, thanks for your replies, I think I have resolved this problem now.
I was only creating my mapping afresh each time I tried to get this
working. My river was never recreated so it got all the changes from the db
on my first go at creating a manual mapping but on subsequent goes there
were no changes in the db so obviously no results in my new index. To
resolve this I just start with a new river and new index for each mapping I
try to create.
On Friday, 1 March 2013 13:14:35 UTC, Teddy777 wrote:
The steps I take to create custom mapping on a couchdb database:
Create a new couchdb called test_db
Add a document with _id - user_id
Create index called 'custom _index'
Create custom mapping - very basic for the time being for testing purpose
( {'properties': {'last_name': {'type': 'string'}}})
Put this mapping on custom index.
Now create my river using custom_index
Add another document with _id - user_id_2 to my couchdb.
Now when I look at the status of my index, its taken my custom mapping
correctly -all good, however when I query it it only shows the doc that was
added after the river was created. Am I right in assuming that the river on
setup should find all the existing docs? Clearly on river creation with
dynamic mapping the index picks up all the existing docs. What I am doing
differently?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.
