Skip to content

Commit e0caf3f

Browse files
authored
Unmute rollover docs test (#62603)
The underlying issue was fixed a while ago in Lucene: https://issues.apache.org/jira/browse/LUCENE-9517 and went away when lucene snapshot version was upgraded. Also the name of the index to rollover had to be slightly changed, so that it doesn't collide with data stream template's namespace. (a regular index can't be created in the namespace that is managed by a template that creates data streams) Closes #62043
1 parent fe2ce8a commit e0caf3f

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

docs/reference/indices/rollover-index.asciidoc

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -371,7 +371,7 @@ which is incremented every time the index is rolled over. For instance:
371371
[source,console]
372372
--------------------------------------------------
373373
# PUT /<logs-{now/d}-1> with URI encoding:
374-
PUT /%3Clogs-%7Bnow%2Fd%7D-1%3E <1>
374+
PUT /%3Clogs_%7Bnow%2Fd%7D-1%3E <1>
375375
{
376376
"aliases": {
377377
"logs_write": {}
@@ -394,10 +394,10 @@ POST /logs_write/_rollover <2>
394394
}
395395
}
396396
--------------------------------------------------
397-
// TEST[skip:"AwaitsFix https://github.com/elastic/elasticsearch/issues/62043"]
397+
// TEST[s/now/2016.10.31%7C%7C/]
398398

399-
<1> Creates an index named with today's date (e.g.) `logs-2016.10.31-1`
400-
<2> Rolls over to a new index with today's date, e.g. `logs-2016.10.31-000002` if run immediately, or `logs-2016.11.01-000002` if run after 24 hours
399+
<1> Creates an index named with today's date (e.g.) `logs_2016.10.31-1`
400+
<2> Rolls over to a new index with today's date, e.g. `logs_2016.10.31-000002` if run immediately, or `logs-2016.11.01-000002` if run after 24 hours
401401

402402
//////////////////////////
403403
@@ -410,12 +410,12 @@ GET _alias
410410
[source,console-result]
411411
--------------------------------------------------
412412
{
413-
"logs-2016.10.31-000002": {
413+
"logs_2016.10.31-000002": {
414414
"aliases": {
415415
"logs_write": {}
416416
}
417417
},
418-
"logs-2016.10.31-1": {
418+
"logs_2016.10.31-1": {
419419
"aliases": {}
420420
}
421421
}

0 commit comments

Comments
 (0)