[DOCS] Replace twitter dataset in docs (#60604)

Author: jrodewig

docs/reference/cluster/health.asciidoc

@@ -184,6 +184,6 @@ The following is an example of getting the cluster health at the
 
 [source,console]
 --------------------------------------------------
-GET /_cluster/health/twitter?level=shards
+GET /_cluster/health/my-index-000001?level=shards
 --------------------------------------------------
-// TEST[setup:twitter]
+// TEST[setup:my_index]

docs/reference/cluster/stats.asciidoc

@@ -1100,7 +1100,7 @@ Number of selected nodes using the distribution flavor and file type.
 --------------------------------------------------
 GET /_cluster/stats?human&pretty
 --------------------------------------------------
-// TEST[setup:twitter]
+// TEST[setup:my_index]
 
 The API returns the following response:
 

docs/reference/commands/shard-tool.asciidoc

@@ -57,7 +57,7 @@ operation that removes corrupted data from the shard.
 
 [source,txt]
 --------------------------------------------------
-$ bin/elasticsearch-shard remove-corrupted-data --index twitter --shard-id 0
+$ bin/elasticsearch-shard remove-corrupted-data --index my-index-000001 --shard-id 0
 
 
     WARNING: Elasticsearch MUST be stopped before running this tool.

docs/reference/docs/delete.asciidoc

@@ -63,7 +63,7 @@ Example to delete with routing
 
 [source,console]
 --------------------------------------------------
-PUT /my-index-000001/_doc/1?routing=kimchy
+PUT /my-index-000001/_doc/1?routing=shard-1
 {
   "test": "test"
 }
@@ -73,7 +73,7 @@ PUT /my-index-000001/_doc/1?routing=kimchy
 
 [source,console]
 --------------------------------------------------
-DELETE /my-index-000001/_doc/1?routing=kimchy
+DELETE /my-index-000001/_doc/1?routing=shard-1
 --------------------------------------------------
 // TEST[continued]
 

docs/reference/eql/eql-search-api.asciidoc

@@ -506,14 +506,14 @@ The following EQL search request searches for events with an `event.category` of
 `file` that meet the following conditions:
 
 * A `file.name` of `cmd.exe`
-* An `agent.id` other than `my_user`
+* An `agent.id` other than `8a4f526c`
 
 [source,console]
 ----
 GET /my-index-000001/_eql/search
 {
   "query": """
-    file where (file.name == "cmd.exe" and agent.id != "my_user")
+    file where (file.name == "cmd.exe" and agent.id != "8a4f526c")
   """
 }
 ----
@@ -614,7 +614,7 @@ that:
 --
 * An `event.category` of `file`
 * A `file.name` of `cmd.exe`
-* An `agent.id` other than `my_user`
+* An `agent.id` other than `8a4f526c`
 --
 . Followed by an event with:
 +
@@ -631,7 +631,7 @@ GET /my-index-000001/_eql/search
 {
   "query": """
     sequence by agent.id
-      [ file where file.name == "cmd.exe" and agent.id != "my_user" ]
+      [ file where file.name == "cmd.exe" and agent.id != "8a4f526c" ]
       [ process where stringContains(process.executable, "regsvr32") ]
   """
 }

docs/reference/frozen-indices.asciidoc

@@ -64,9 +64,9 @@ or sorted search requests.
 
 [source,console]
 --------------------------------------------------
-POST /twitter/_forcemerge?max_num_segments=1
+POST /my-index-000001/_forcemerge?max_num_segments=1
 --------------------------------------------------
-// TEST[setup:twitter]
+// TEST[setup:my_index]
 
 [role="xpack"]
 [testenv="basic"]
@@ -81,9 +81,9 @@ the query parameter `ignore_throttled=false`.
 
 [source,console]
 --------------------------------------------------
-GET /twitter/_search?q=user:kimchy&ignore_throttled=false
+GET /my-index-000001/_search?q=user.id:kimchy&ignore_throttled=false
 --------------------------------------------------
-// TEST[setup:twitter]
+// TEST[setup:my_index]
 
 [role="xpack"]
 [testenv="basic"]
@@ -95,16 +95,16 @@ Frozen indices are ordinary indices that use search throttling and a memory effi
 
 [source,console]
 --------------------------------------------------
-GET /_cat/indices/twitter?v&h=i,sth
+GET /_cat/indices/my-index-000001?v&h=i,sth
 --------------------------------------------------
-// TEST[s/^/PUT twitter\nPOST twitter\/_freeze\n/]
+// TEST[s/^/PUT my-index-000001\nPOST my-index-000001\/_freeze\n/]
 
 The response looks like:
 
 [source,txt]
 --------------------------------------------------
-i         sth
-twitter   true
+i                 sth
+my-index-000001   true
 --------------------------------------------------
 // TESTRESPONSE[non_json]
 

docs/reference/index-modules/blocks.asciidoc

@@ -74,9 +74,9 @@ Adds an index block to an index.
 
 [source,console]
 --------------------------------------------------
-PUT /twitter/_block/write
+PUT /my-index-000001/_block/write
 --------------------------------------------------
-// TEST[setup:twitter]
+// TEST[setup:my_index]
 
 
 [discrete]

docs/reference/index-modules/index-sorting.asciidoc

@@ -14,7 +14,7 @@ For instance the following example shows how to define a sort on a single field:
 
 [source,console]
 --------------------------------------------------
-PUT twitter
+PUT my-index-000001
 {
   "settings": {
     "index": {
@@ -39,7 +39,7 @@ It is also possible to sort the index by more than one field:
 
 [source,console]
 --------------------------------------------------
-PUT twitter
+PUT my-index-000001
 {
   "settings": {
     "index": {

docs/reference/index-modules/slowlog.asciidoc

@@ -29,7 +29,7 @@ All of the above settings are _dynamic_ and can be set for each index using the
 
 [source,console]
 --------------------------------------------------
-PUT /twitter/_settings
+PUT /my-index-000001/_settings
 {
   "index.search.slowlog.threshold.query.warn": "10s",
   "index.search.slowlog.threshold.query.info": "5s",
@@ -41,7 +41,7 @@ PUT /twitter/_settings
   "index.search.slowlog.threshold.fetch.trace": "200ms"
 }
 --------------------------------------------------
-// TEST[setup:twitter]
+// TEST[setup:my_index]
 
 By default thresholds are disabled (set to `-1`).
 
@@ -108,7 +108,7 @@ All of the above settings are _dynamic_ and can be set for each index using the
 
 [source,console]
 --------------------------------------------------
-PUT /twitter/_settings
+PUT /my-index-000001/_settings
 {
   "index.indexing.slowlog.threshold.index.warn": "10s",
   "index.indexing.slowlog.threshold.index.info": "5s",
@@ -117,7 +117,7 @@ PUT /twitter/_settings
   "index.indexing.slowlog.source": "1000"
 }
 --------------------------------------------------
-// TEST[setup:twitter]
+// TEST[setup:my_index]
 
 By default Elasticsearch will log the first 1000 characters of the _source in
 the slowlog. You can change that with `index.indexing.slowlog.source`. Setting

docs/reference/indices/aliases.asciidoc

@@ -302,19 +302,23 @@ exist in the mapping:
 
 [source,console]
 --------------------------------------------------
-PUT /test1
+PUT /my-index-000001
 {
   "mappings": {
     "properties": {
-      "user" : {
-        "type": "keyword"
+      "user": {
+        "properties": {
+          "id": {
+            "type": "keyword"
+          }
+        }
       }
     }
   }
 }
 --------------------------------------------------
 
-Now we can create an alias that uses a filter on field `user`:
+Now we can create an alias that uses a filter on field `user.id`:
 
 [source,console]
 --------------------------------------------------
@@ -323,7 +327,7 @@ POST /_aliases
   "actions": [
     {
       "add": {
-        "index": "test1",
+        "index": "my-index-000001",
         "alias": "alias2",
         "filter": { "term": { "user.id": "kimchy" } }
       }