Update mappings all the time


(James Cook) #1

It seems that every time I index a document, I get the update mapping log
statements.

Indexing document, index [ppkc], type [activities], key
[5260d986257c472db42d405f91158062]
[Stacy X] processing [update-mapping [ppkc][activities]]: execute
[Stacy X] [ppkc] update_mapping [activities] (dynamic)
[Stacy X] cluster state updated: version [8], source [update-mapping
[ppkc][activities]]

It's a pretty quick operation, but I don't understand why it is happening. I
am not using dynamic mapping so I am unsure why this is happening?

-- jim


(David Pilato) #2

Can you gist some activities documents ?

David :wink:

Le 20 sept. 2011 à 02:32, James Cook jcook@tracermedia.com a écrit :

It seems that every time I index a document, I get the update mapping log statements.

Indexing document, index [ppkc], type [activities], key [5260d986257c472db42d405f91158062]
[Stacy X] processing [update-mapping [ppkc][activities]]: execute
[Stacy X] [ppkc] update_mapping [activities] (dynamic)
[Stacy X] cluster state updated: version [8], source [update-mapping [ppkc][activities]]

It's a pretty quick operation, but I don't understand why it is happening. I am not using dynamic mapping so I am unsure why this is happening?

-- jim


(Shay Banon) #3

If you are not using dynamic mapping, then you shouldn't see this messages.
Can you gist a recreation?

On Tue, Sep 20, 2011 at 8:08 AM, David Pilato david@pilato.fr wrote:

Can you gist some activities documents ?

David :wink:

Le 20 sept. 2011 à 02:32, James Cook jcook@tracermedia.com a écrit :

It seems that every time I index a document, I get the update mapping log
statements.

Indexing document, index [ppkc], type [activities], key
[5260d986257c472db42d405f91158062]
[Stacy X] processing [update-mapping [ppkc][activities]]: execute
[Stacy X] [ppkc] update_mapping [activities] (dynamic)
[Stacy X] cluster state updated: version [8], source [update-mapping
[ppkc][activities]]

It's a pretty quick operation, but I don't understand why it is
happening. I am not using dynamic mapping so I am unsure why this is
happening?

-- jim


(James Cook) #4

Hmmm, well we aren't using dynamic mapping, but we do put our mappings into
a directory for ES to discover. Could it be that ES starts up with dynamic
mapping, then discovers the mapping files I have for each type? Then when I
index a document, it issues an update_mapping call even though I am indexing
a document to one of my types that is mapped?


(Shay Banon) #5

What do you mean by putting it in a directory for elasticsearch to discvoer?
Mappings in the config location are applied when the index gets created
(which happens before a document gets indexed).

On Wed, Sep 21, 2011 at 1:00 AM, James Cook jcook@tracermedia.com wrote:

Hmmm, well we aren't using dynamic mapping, but we do put our mappings into
a directory for ES to discover. Could it be that ES starts up with dynamic
mapping, then discovers the mapping files I have for each type? Then when I
index a document, it issues an update_mapping call even though I am indexing
a document to one of my types that is mapped?


(James Cook) #6

Right, but if I explicitly create the mappings using the API as part of the
index creation, I do not see the log statements in the original post.

[Stacy X] processing [update-mapping [ppkc][activities]]: execute
[Stacy X] [ppkc] update_mapping [activities] (dynamic)
[Stacy X] cluster state updated: version [8], source [update-mapping
[ppkc][activities]]

What triggers the update-mapping log statements, and why does it say
(dynamic)?


(Shay Banon) #7

The log message comes from an index operation causing for un mapped fields
to be introduced. I think we can move faster I can somehow recreate it?

On Wed, Sep 21, 2011 at 6:41 AM, James Cook jcook@tracermedia.com wrote:

Right, but if I explicitly create the mappings using the API as part of the
index creation, I do not see the log statements in the original post.

[Stacy X] processing [update-mapping [ppkc][activities]]: execute
[Stacy X] [ppkc] update_mapping [activities] (dynamic)
[Stacy X] cluster state updated: version [8], source [update-mapping
[ppkc][activities]]

What triggers the update-mapping log statements, and why does it say
(dynamic)?


(James Cook) #8

Thanks for the hint. I will look at our mappings and make sure no new
properties are being introduced. I will gist if that isn't the problem.
Thanks.


(system) #9