I see for the object type you have the field enabled in case you don't want to index it in
subsequent calls. How can you not index a core type field. Meaning you have an initial mapping where you set your fields.
But some later call to index can have a core type field that I don't want to index. As it is now, correct me if I'm wrong, it
will get dynamically mapped. How can I avoid that.
If I change the mapping I have for a document by adding a new field, dynamically or not, it will cause a re-indexing of the already indexed documents?
On Wednesday, February 9, 2011 at 7:49 PM, stelios wrote:
Hi,
Two questions regarding the mapping process.
I see for the object type you have the field enabled in case you don't
want to index it in
subsequent calls. How can you not index a core type field. Meaning you have
an initial mapping where you set your fields.
But some later call to index can have a core type field that I don't want to
index. As it is now, correct me if I'm wrong, it
will get dynamically mapped. How can I avoid that.
You can set the dynamic flag to false on the root object mapping.
If I change the mapping I have for a document by adding a new field,
dynamically or not, it will cause a re-indexing of the already indexed
documents?
No, you don't need to reindex. Introducing new fields does not require reindexing.
How can I not index the field "successful". When I do a mapping and not
include this field but then index a document that has this
field then it gets mapped dynamically. Of course I can set dynamic mapping
off and it will work as I want but there are other cases where dynamic
mapping is handy.
On Wednesday, February 9, 2011 at 7:49 PM, stelios wrote:
Hi,
Two questions regarding the mapping process.
I see for the object type you have the field enabled in case you don't
want to index it in
subsequent calls. How can you not index a core type field. Meaning you have
an initial mapping where you set your fields.
But some later call to index can have a core type field that I don't want
to
index. As it is now, correct me if I'm wrong, it
will get dynamically mapped. How can I avoid that.
You can set the dynamic flag to false on the root object mapping.
If I change the mapping I have for a document by adding a new field,
dynamically or not, it will cause a re-indexing of the already indexed
documents?
No, you don't need to reindex. Introducing new fields does not require
reindexing.
Just to clarify I know that I can use "enabled" : false in the "1_0" object
so it will not map the "successful" field but it won't map any other fields
as well. What I really need is to do something like "successful" :
"not_mapped". Is this possible at the moment?
How can I not index the field "successful". When I do a mapping and not
include this field but then index a document that has this
field then it gets mapped dynamically. Of course I can set dynamic mapping
off and it will work as I want but there are other cases where dynamic
mapping is handy.
On Wednesday, February 9, 2011 at 7:49 PM, stelios wrote:
Hi,
Two questions regarding the mapping process.
I see for the object type you have the field enabled in case you don't
want to index it in
subsequent calls. How can you not index a core type field. Meaning you
have
an initial mapping where you set your fields.
But some later call to index can have a core type field that I don't want
to
index. As it is now, correct me if I'm wrong, it
will get dynamically mapped. How can I avoid that.
You can set the dynamic flag to false on the root object mapping.
If I change the mapping I have for a document by adding a new field,
dynamically or not, it will cause a re-indexing of the already indexed
documents?
No, you don't need to reindex. Introducing new fields does not require
reindexing.
How can I not index the field "successful". When I do a mapping and
not include this field but then index a document that has this
field then it gets mapped dynamically. Of course I can set dynamic
mapping off and it will work as I want but there are other cases where
dynamic mapping is handy.
Have a look at "index": "analyzed|not_analyzed|no" on this page:
How can I not index the field "successful". When I do a mapping and
not include this field but then index a document that has this
field then it gets mapped dynamically. Of course I can set dynamic
mapping off and it will work as I want but there are other cases where
dynamic mapping is handy.
Have a look at "index": "analyzed|not_analyzed|no" on this page:
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.