Mapping transform field type?

Elastic Stack Elasticsearch
1

Hi,

Should we or can we specify a field type when using a mapping transform
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-transform.html?
E.g. if we do some calculation, should we specify the result type is an
integer? Or is the result type auto-detected and there's no was to specify
a type mapping for the field?

Thanks,
Ben

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/cbece670-2518-4f40-8250-8ae035783b35%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

2

Hi Ben,

Even when using mapping transform, dynamic mappings will work as usual and
try to detect the type of the field that you are trying to index. But you
can also add a mapping for this field explicitely in your mappings.

On Sat, Nov 15, 2014 at 6:51 PM, Ben McCann benjamin.j.mccann@gmail.com
wrote:

Hi,

Should we or can we specify a field type when using a mapping transform
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-transform.html?
E.g. if we do some calculation, should we specify the result type is an
integer? Or is the result type auto-detected and there's no was to specify
a type mapping for the field?

Thanks,
Ben

--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/cbece670-2518-4f40-8250-8ae035783b35%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/cbece670-2518-4f40-8250-8ae035783b35%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
Adrien Grand

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAL6Z4j6bruONjs1pMpSbmkJ6eLi01tG_0u0SCFefUdYMtZt04w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

3

Gotcha. The part that confused me was that I thought the mapping transform
was where you specified the mapping. I didn't realize you would specify the
transform and the mapping separately.

Thanks,
Ben

On Mon, Nov 17, 2014 at 3:06 AM, Adrien Grand <
adrien.grand@elasticsearch.com> wrote:

Hi Ben,

Even when using mapping transform, dynamic mappings will work as usual and
try to detect the type of the field that you are trying to index. But you
can also add a mapping for this field explicitely in your mappings.

On Sat, Nov 15, 2014 at 6:51 PM, Ben McCann benjamin.j.mccann@gmail.com
wrote:

Hi,

Should we or can we specify a field type when using a mapping transform
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-transform.html?
E.g. if we do some calculation, should we specify the result type is an
integer? Or is the result type auto-detected and there's no was to specify
a type mapping for the field?

Thanks,
Ben

--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/cbece670-2518-4f40-8250-8ae035783b35%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/cbece670-2518-4f40-8250-8ae035783b35%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
Adrien Grand

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/tF5FHUCPeTo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAL6Z4j6bruONjs1pMpSbmkJ6eLi01tG_0u0SCFefUdYMtZt04w%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAL6Z4j6bruONjs1pMpSbmkJ6eLi01tG_0u0SCFefUdYMtZt04w%40mail.gmail.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAH3cagO%2Bas7UXadJmsHCkGvyCiEgky3coV3paC%3DZeOvF3o45Hw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.