Skip to content
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

Terms API: Support numbers/dates #78

Closed
kimchy opened this issue Mar 22, 2010 · 1 comment
Closed

Terms API: Support numbers/dates #78

kimchy opened this issue Mar 22, 2010 · 1 comment

Comments

@kimchy
Copy link
Member

kimchy commented Mar 22, 2010

Terms API should support numbers and dates natively, and not treat them as strings. This means that from/to should support numbers/dates, and the terms returned should be in the number/date format and not in their internal format.

The convert parameter should be removed also since it is not required anymore.

@kimchy
Copy link
Member Author

kimchy commented Mar 22, 2010

Terms API: Support numbers/dates, closed by 93e0253.

dadoonet pushed a commit that referenced this issue Jun 5, 2015
For legal reasons, we need to store our ES backups in S3 using server side encryption.

Closes #78.

(cherry picked from commit b3f9e12)
rmuir pushed a commit to rmuir/elasticsearch that referenced this issue Nov 8, 2015
Currently tika exceptions are swallowed with no log message.
We'd like to be able to know when/if this occurs and for what reason.

Closes elastic#78.

(cherry picked from commit 36b0117)
maabernethy pushed a commit to maabernethy/elasticsearch that referenced this issue Mar 20, 2017
henningandersen pushed a commit to henningandersen/elasticsearch that referenced this issue Jun 4, 2020
With this commit we ensure that statistics get still derived properly
even if there are no hits.
williamrandolph pushed a commit to williamrandolph/elasticsearch that referenced this issue Jun 4, 2020
mindw pushed a commit to mindw/elasticsearch that referenced this issue Sep 5, 2022
…lastic#78)

* Add branch to create a branch from a tag on all active repos

To support creating release branches, wrote a script that will iterate over all
active, top level, repos, verify that tag exists, and branch from that point.

If branch name is not supplied, script will name it `release/<tag>_YYYY.MM.DD`

Approved-by: Rich Nessel
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
Use new metrics store in eu-central-1 for night-rally and update
new Kibana URL in README.md

Relates elastic#78
emilykmarx pushed a commit to emilykmarx/elasticsearch that referenced this issue Dec 26, 2023
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant