You can supply a custom mapping for that index BEFORE the index is created,
denoting which fields should and should not be indexed. You cannot change
the source document, but you do have control over what fields are indexed.
--
Ivan
On Mon, Aug 12, 2013 at 7:57 PM, JD jdalecki@tycoint.com wrote:
Hi,****
I have created my river for my MongoDB Asset collection that should be
indexed by Elasticsearch.****To do that I have used the following command:****
Create river for Asset collection****
http://localhost:9200/_river/asset_river/_meta -d '{****
"type": "mongodb",****
"mongodb": {****
"db": "my_database",**** "collection": "Asset"****},****
"index": {****
"name": "asset_index",**** "type": "Asset"****}****
}'
I think this will basically index every field in all my Asset documents –
is that right?.Does it make sense to do that – if I understand it I will have so many
indexes that the searching might be as slow as just searching through the
documents themselves? I am right?****Regards,
Janusz
--
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.