{
"error" : "Incorrect HTTP method for uri [/%3Call-dns-%7Bnow/d%7D%25-0000013E?pretty=&pretty=true] and method [PUT], allowed: [POST]",
"status" : 405
}
Changing the method to POST is no better:
{
"error" : "no handler found for uri [/%3Call-dns-%7Bnow/d%7D%25-0000013E?pretty=&pretty=true] and method [POST]"
}
This used to work, because I just changed the name in prior commands devtools.
Using the date math {now/d} will put the current date at rollover in the index name at each rollover event. If you use a literal date for the first index, that date will be used in all future indices.
Hmmm I will need to validate for myself as I was not aware of that / not my understanding ... unfortunately to validate I need to wait for a UTC date rollover to trigger the date portion in 20 hours (pretty sure I have manually bootstrapped many indices with the literal... but perhaps I am wrong or something has changed) either way now I have to know Thanks for pointing out.
It burned me early in ILM, it's been awhile, it's possible it's fixed, but I think it needs the {date/d} in the "provided_name" field in the index to know a date isn't a constant.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.