Unable to disable the _source field


(Sergio Bossa) #1

Hi,

I tried to disable the _source field by modifying the dynamic mapping.
I changed the dynamic mapping location by setting the
index.mapper.dynamicMappingLocation property, and created the
following json mapping configuration:

{
"default" : {
"_source" : {"enabled" : false}
}
}

Too bad, I still get the _source field in search results.

Am I missing something?
Thanks!

Sergio B.

--
Sergio Bossa
http://www.linkedin.com/in/sergiob


(Shay Banon) #2

This looks like a bug. I will have a look at this.

-shay.banon

On Sat, Jul 24, 2010 at 3:18 PM, Sergio Bossa sergio.bossa@gmail.comwrote:

Hi,

I tried to disable the _source field by modifying the dynamic mapping.
I changed the dynamic mapping location by setting the
index.mapper.dynamicMappingLocation property, and created the
following json mapping configuration:

{
"default" : {
"_source" : {"enabled" : false}
}
}

Too bad, I still get the _source field in search results.

Am I missing something?
Thanks!

Sergio B.

--
Sergio Bossa
http://www.linkedin.com/in/sergiob


(Sergio Bossa) #3

On Sun, Jul 25, 2010 at 10:48 AM, Shay Banon
shay.banon@elasticsearch.com wrote:

This looks like a bug. I will have a look at this.

Great. Thanks.

--
Sergio Bossa
http://www.linkedin.com/in/sergiob


(Shay Banon) #4

Opened a case for this:
http://github.com/elasticsearch/elasticsearch/issues/issue/274, will push a
fix later today. What I would really want to have is the default mapping
to form the basis for any mapping definition, so even when you put a
mapping, it will be used as well (unless explicitly overridden in the put
mapping definition).

-shay.banon

On Sun, Jul 25, 2010 at 11:53 AM, Sergio Bossa sergio.bossa@gmail.comwrote:

On Sun, Jul 25, 2010 at 10:48 AM, Shay Banon
shay.banon@elasticsearch.com wrote:

This looks like a bug. I will have a look at this.

Great. Thanks.

--
Sergio Bossa
http://www.linkedin.com/in/sergiob


(Sergio Bossa) #5

On Sun, Jul 25, 2010 at 11:18 AM, Shay Banon
shay.banon@elasticsearch.com wrote:

Opened a case for
this: http://github.com/elasticsearch/elasticsearch/issues/issue/274, will
push a fix later today.

Great: I'll give it a try as soon as available.

What I would really want to have is the default
mapping to form the basis for any mapping definition, so even when you put a
mapping, it will be used as well (unless explicitly overridden in the put
mapping definition).

Absolutely agree.

Cheers,

Sergio B.

--
Sergio Bossa
http://www.linkedin.com/in/sergiob


(Shay Banon) #6

Managed to get this into upcoming 0.9 (with a breaking change):
http://github.com/elasticsearch/elasticsearch/issues/closed#issue/275.

-shay.banon

On Sun, Jul 25, 2010 at 12:29 PM, Sergio Bossa sergio.bossa@gmail.comwrote:

On Sun, Jul 25, 2010 at 11:18 AM, Shay Banon
shay.banon@elasticsearch.com wrote:

Opened a case for
this: http://github.com/elasticsearch/elasticsearch/issues/issue/274,
will
push a fix later today.

Great: I'll give it a try as soon as available.

What I would really want to have is the default
mapping to form the basis for any mapping definition, so even when you
put a
mapping, it will be used as well (unless explicitly overridden in the put
mapping definition).

Absolutely agree.

Cheers,

Sergio B.

--
Sergio Bossa
http://www.linkedin.com/in/sergiob


(system) #7