-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Sorting on a field explicitly mapped as an integer fails when not all types mapped as well #31
Comments
This sort works correctly if all /index/type combinations have num mapped as integer |
Well, I tracked down the problem... . First, the search operation will not hang now (I just pushed a fix for it). The reason this fails is because when there is no mapping for a number, it is treated as a long, and when trying to compare long to ints the reduce phase fails. Now, you will get a failed response because of that. I still need to think how to support this (we should...). |
It now throws an exception correctly |
The `kuromoji` analyzer is not registered as a global analyzer, so this fails: POST /_analyze?analyzer=kuromoji&text=J R 新宿駅の近くにビールを飲みに行こうか { "error": "ElasticsearchIllegalArgumentException[failed to find analyzer [kuromoji]]", "status": 400 } But this succeeds: PUT /t POST /t/_analyze?analyzer=kuromoji&text=J R 新宿駅の近くにビールを飲みに行こうか Closes #31.
Closes #31. (cherry picked from commit 39b83f0)
Closes #31. (cherry picked from commit ab3cde3)
Previously, we track the next wake-up time in Legislator and also have to track the leaderMode (whether publishing or sending a heartbeat). This change gets rid of this state, instead using the FutureExecutor to schedule the future wake-ups.
Changed Readme and added template install
Test script:
The text was updated successfully, but these errors were encountered: