Update tutorial-load-dataset.asciidoc #11703
Conversation
| @@ -78,7 +78,7 @@ curl -H 'Content-Type: application/json' -XPUT http://localhost:9200/shakespeare | |||
|
|
|||
| This mapping specifies the following qualities for the data set: | |||
|
|
|||
| * The _speaker_ field is a string that isn't analyzed. The string in this field is treated as a single unit, even if | |||
| * The _speaker_ field is a keyword that isn't analyzed. The text in this field is treated as a single unit, even if | |||
There was a problem hiding this comment.
thoughts on changing this to ...field that isn't analyzed? I think the not analyzed portion overlaps with keyword.
There was a problem hiding this comment.
Yep. That makes sense to me.
Incorporating @jbudz comments
| @@ -78,7 +78,7 @@ curl -H 'Content-Type: application/json' -XPUT http://localhost:9200/shakespeare | |||
|
|
|||
| This mapping specifies the following qualities for the data set: | |||
|
|
|||
| * The _speaker_ field is a string that isn't analyzed. The string in this field is treated as a single unit, even if | |||
| * The _speaker_ field is a field that isn't analyzed. The text in this field is treated as a single unit, even if | |||
There was a problem hiding this comment.
I think I'd flip this around and say, Because the speaker and play_name fields are keyword fields, they are not analyzed. The strings are treated as a single unit even if they contain multiple words." and drop "The same applies to the play_name field."
There was a problem hiding this comment.
That makes sense to me.
|
I think the schema is ok as-is. Not sure about default, it might be better to specify a single type? It would be nice if these curl examples were tested console examples instead. |
Incorporating Deb's comments to change curl commands as console tested
|
|
||
| You should see output similar to the following: | ||
|
|
||
| [source,shell] | ||
| [source,js] |
There was a problem hiding this comment.
any reason why this one was changed to [source,js]?
Using curl command to display indices created
|
@jbudz shall I go back to curl for those commands? Thanks! |
Using shell and console tested command to get the _cat/indices
|
I realize now why we're using _default_ with the shakespeare mappings - there are two types with some overlapping field names. |
Changing the tutorial to update it according to the new ES mappings and adding console tested commands.
Changing the tutorial to update it according to the new ES mappings and adding console tested commands.
Changing the tutorial to update it according to the new ES mappings and adding console tested commands.
Changing the tutorial to update it according to the new ES mappings and adding console tested commands.
Changing the tutorial to update it according to the new ES mappings and adding console tested commands.
Changing the tutorial to update it according to the new ES mappings and adding console tested commands.
Changing the tutorial to update it according to the new ES mappings and adding console tested commands.
This PR is for fixing load sample data into kibana website for 6.0.0_alpha1 https://www.elastic.co/guide/en/kibana/master/tutorial-load-dataset.html
I have updated the mapping for string -> keyword.
1.Do we change the schema on the page to reflect ES mappings? Specifically do I change INT to long? and all the strings into text fields? According to this?
https://www.elastic.co/guide/en/elasticsearch/reference/master/mapping.html#mapping
2.Do I remove the "default" : from the curl command to create mapping?
The data files for logs and accounts.zip are fine. I do need to change the shakespeare.json and pass it to Deb to upload it.