1.0.0.0.RC1 breaking changes: multi_field documentation


(Brian Yoder) #1

Looking at the following to prepare for RC1:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/master/_multi_fields.html

I find the following. But shouldn't the semicolon after the first "type" "
"string" be a comma?

Brian

you can now write:

"title": {
"type": "string";
"fields": {
"raw": { "type": "string", "index": "not_analyzed" }
}
}

--
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/008da72d-f2a3-4f76-a9ec-0dd335be8c23%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Luca Cavanna) #2

yes, definitely, that's a typo which I'm going to fix, thanks!

On Monday, January 20, 2014 5:15:36 PM UTC+1, InquiringMind wrote:

Looking at the following to prepare for RC1:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/master/_multi_fields.html

I find the following. But shouldn't the semicolon after the first "type"
" "string" be a comma?

Brian

you can now write:

"title": {
"type": "string";
"fields": {
"raw": { "type": "string", "index": "not_analyzed" }
}
}

--
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/1d0d1395-5e3d-4e5e-8203-53a702025664%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Brian Yoder) #3

Luca,

Thanks for the quick confirmation!

One quick question: the doc also says that:

Existing multi-fields will be upgraded to the new format automatically.

I assume that this means that existing indices with multi-field mappings
will be OK, but whenever I create a new index and add multiple mappings for
a new field, I must use the new syntax and not the old syntax. Is this a
correct assumptions (no problem; I have already converted my mappings in
preparation for RC1 and just want to know that it was worth the time to do
it!)

Thanks!

Brian

--
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/85514003-30a4-440f-a0a4-9a71e212906b%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Luca Cavanna) #4

Hi Brian,
we do upgrade existing mappings converting the old format to the new one.
That means whenever a mapping contains the old format, the get mapping will
output the new one anyway. That works for existing mappings, as well as for
new mappings added using the old format.

That said I'd recommended to switch to the new format anyway, something
that you have already done. Well done then :wink:

On Mon, Jan 20, 2014 at 6:39 PM, InquiringMind brian.from.fl@gmail.comwrote:

Luca,

Thanks for the quick confirmation!

One quick question: the doc also says that:

Existing multi-fields will be upgraded to the new format automatically.

I assume that this means that existing indices with multi-field mappings
will be OK, but whenever I create a new index and add multiple mappings for
a new field, I must use the new syntax and not the old syntax. Is this a
correct assumptions (no problem; I have already converted my mappings in
preparation for RC1 and just want to know that it was worth the time to do
it!)

Thanks!

Brian

--
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/hFhjM8k9hvA/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/85514003-30a4-440f-a0a4-9a71e212906b%40googlegroups.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CADdZ9MUOvo2%3DFkbQXUz8K4ULZkBSiOEBNVaNrEwGoQLfU4j8GQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.


(system) #5