New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to create filtered alias, using range, data_nanos and negative offsets(now-7d) #54315
Comments
Pinging @elastic/es-search (:Search/Search) |
Pinging @elastic/es-core-features (:Core/Features/Indices APIs) |
This issue maybe originated from this line in Line 154 in 5a98fc2
|
This is correct @gaobinlong thanks for looking. Would you like to provide a pull request to fix this since you already found the issue ? |
@jimczi I'm glad to do that. |
…led (elastic#54785) Modify the value of nowInMillis in queryShardContext to current timestamp, because the value will be used lately when validating the filtered alias which uses now in a date_nanos range query. Closes elastic#54315
…led (elastic#54785) Modify the value of nowInMillis in queryShardContext to current timestamp, because the value will be used lately when validating the filtered alias which uses now in a date_nanos range query. Closes elastic#54315
Elasticsearch version (
bin/elasticsearch --version
): OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.Version: 7.6.1, Build: default/docker/aa751e09be0a5072e8570670309b1f12348f023b/2020-02-29T00:15:25.529771Z, JVM: 13.0.2
Plugins installed: []
JVM version (
java -version
): openjdk version "13.0.2" 2020-01-14OpenJDK Runtime Environment AdoptOpenJDK (build 13.0.2+8)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 13.0.2+8, mixed mode, sharing)
OS version (
uname -a
if on a Unix-like system): Linux ad9271944652 4.19.76-linuxkit #1 SMP Thu Oct 17 19:31:58 UTC 2019 x86_64 x86_64 x86_64 GNU/LinuxError is returned when attempting to create a filtered alias that uses a range, with a data_nanos field, using now, and a negative offset (such as now-7d)
This error does not appear when using date fields or when using positive offsets (such as now+7d)
Steps to reproduce:
The text was updated successfully, but these errors were encountered: