Date Math Not Working for GET #13665
Comments
|
It's not supposed to work AFAIK. Did you see that somewhere in docs? May be using an alias would help you? |
|
This page includes the date math information. Example from page. I try this curl command and get a error. {"error":{"root_cause":[{"type":"index_not_found_exception","reason":"no such index","resource.type":"index_or_alias","resource.id":"<logstash-now","index":"<logstash-now"}],"type":"index_not_found_exception","reason":"no such index","resource.type":"index_or_alias","resource.id":"<logstash-now","index":"<logstash-now"},"status":404} There is also this pull request. |
|
Great. I missed that ! |
|
Thanks for reporting @sirdavidhuang, this is indeed a bug. The issue here is that the index name is cut of at the date rounding ( |
clintongormley
added
the
:Distributed/CRUD
|
Hi @sirdavidhuang we had initially treated this as a bug and fixed it, but afterwards we found out that the fix introduced a regression (#14177), which made us take a step back. Any slash that should not be used as a path separator in a uri should be properly escaped, and it is wrong to try and make distinctions between the different slashes on the server side depending on what surrounds them, that heuristic is not going to fly (in fact it didn't :) ) We are going to revert the initial fix then, the solution to this problem is to escape the '/' in the url like this: |
With elastic#13691 we introduced some custom logic to make sure that date math expressions like <logstash-{now/D}> don't get broken up into two where the slash appears in the expression. That said the only correct way to provide such a date math expression as part of the uri would be to properly escape the '/' instead. This fix also introduced a regression, as it would make sure that unescaped '/' are handled only in the case of date math expressions, but it removed support for properly escaped slashes anywhere else. The solution is to keep supporting escaped slashes only and require client libraries to properly escape them. This commit reverts 93ad696 and makes sure that our REST tests runner supports escaping of path parts, which was more involving than expected as each single part of the path needs to be properly escaped. I am not too happy with the current solution but it's the best I could do for now, maybe not that concerning anyway given that it's just test code. I do find uri encoding quite frustrating in java. Relates to elastic#13691 Relates to elastic#13665 Closes elastic#14177 Closes elastic#14216
With elastic#13691 we introduced some custom logic to make sure that date math expressions like <logstash-{now/D}> don't get broken up into two where the slash appears in the expression. That said the only correct way to provide such a date math expression as part of the uri would be to properly escape the '/' instead. This fix also introduced a regression, as it would make sure that unescaped '/' are handled only in the case of date math expressions, but it removed support for properly escaped slashes anywhere else. The solution is to keep supporting escaped slashes only and require client libraries to properly escape them. This commit reverts 93ad696 and makes sure that our REST tests runner supports escaping of path parts, which was more involving than expected as each single part of the path needs to be properly escaped. I am not too happy with the current solution but it's the best I could do for now, maybe not that concerning anyway given that it's just test code. I do find uri encoding quite frustrating in java. Relates to elastic#13691 Relates to elastic#13665 Closes elastic#14177 Closes elastic#14216
With elastic#13691 we introduced some custom logic to make sure that date math expressions like <logstash-{now/D}> don't get broken up into two where the slash appears in the expression. That said the only correct way to provide such a date math expression as part of the uri would be to properly escape the '/' instead. This fix also introduced a regression, as it would make sure that unescaped '/' are handled only in the case of date math expressions, but it removed support for properly escaped slashes anywhere else. The solution is to keep supporting escaped slashes only and require client libraries to properly escape them. This commit reverts 93ad696 and makes sure that our REST tests runner supports escaping of path parts, which was more involving than expected as each single part of the path needs to be properly escaped. I am not too happy with the current solution but it's the best I could do for now, maybe not that concerning anyway given that it's just test code. I do find uri encoding quite frustrating in java. Relates to elastic#13691 Relates to elastic#13665 Closes elastic#14177 Closes elastic#14216
With elastic#13691 we introduced some custom logic to make sure that date math expressions like <logstash-{now/D}> don't get broken up into two where the slash appears in the expression. That said the only correct way to provide such a date math expression as part of the uri would be to properly escape the '/' instead. This fix also introduced a regression, as it would make sure that unescaped '/' are handled only in the case of date math expressions, but it removed support for properly escaped slashes anywhere else. The solution is to keep supporting escaped slashes only and require client libraries to properly escape them. This commit reverts 93ad696 and makes sure that our REST tests runner supports escaping of path parts, which was more involving than expected as each single part of the path needs to be properly escaped. I am not too happy with the current solution but it's the best I could do for now, maybe not that concerning anyway given that it's just test code. I do find uri encoding quite frustrating in java. Relates to elastic#13691 Relates to elastic#13665 Closes elastic#14177 Closes elastic#14216
I try to get a document using date math, but Elasticsearch returns a error.
Version: Elasticsearch 2.0.0-beta2
Put Document
$ curl -XPUT 'localhost:9200/logstash-2015.09.19/animals/1' -d '{"name":"puppy"}'
{"_index":"logstash-2015.09.19","_type":"animals","_id":"1","_version":1,"_shards":{"total":2,"successful":1,"failed":0},"created":true}
Get Document
$ curl -XGET 'localhost:9200/logstash-2015.09.19/animals/1'
{"_index":"logstash-2015.09.19","_type":"animals","_id":"1","_version":1,"found":true,"_source":{"name":"puppy"}}
Get Document with Date Math
$ curl -XGET 'localhost:9200/
<logstash-{now/d}>/animals/1'No handler found for uri
[/<logstash-now/d>/animals/1]and method [GET]The text was updated successfully, but these errors were encountered: