upgrade to Lucene-8.7.0-snapshot-61ea26a #61957
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jpountz
approved these changes
Sep 4, 2020
|
@elasticmachine run elasticsearch-ci/packaging-sample-windows |
1 similar comment
|
@elasticmachine run elasticsearch-ci/packaging-sample-windows |
This was referenced Sep 4, 2020
iverase
added a commit
that referenced
this pull request
Sep 4, 2020
tlrx
added a commit
that referenced
this pull request
Sep 7, 2020
…1989) Elasticsearch now uses #61957 which includes https://issues.apache.org/jira/browse/LUCENE-9456. We can remove the corresponding //TODO in SearchableSnapshotsBlobStoreCacheIntegTests.
tlrx
added a commit
that referenced
this pull request
Sep 7, 2020
…1989) (#62030) Elasticsearch now uses #61957 which includes https://issues.apache.org/jira/browse/LUCENE-9456. We can remove the corresponding //TODO in SearchableSnapshotsBlobStoreCacheIntegTests.
ebadyano
added a commit
to ebadyano/rally-tracks
that referenced
this pull request
Oct 1, 2020
From observation in the nightly environment we can see that occasionally the phrase and term query may take >300ms and >1000ms. This leads to unnecessary spikes in the latency charts. Relates to elastic/elasticsearch#61957
ebadyano
added a commit
to elastic/rally-tracks
that referenced
this pull request
Oct 6, 2020
From observation in the nightly environment we can see that occasionally the phrase and term query may take >300ms and >1000ms. This leads to unnecessary spikes in the latency charts. Relates to elastic/elasticsearch#61957
ebadyano
added a commit
to elastic/rally-tracks
that referenced
this pull request
Oct 7, 2020
From observation in the nightly environment we can see that occasionally the phrase and term query may take >300ms and >1000ms. This leads to unnecessary spikes in the latency charts. Relates to elastic/elasticsearch#61957
ebadyano
added a commit
to elastic/rally-tracks
that referenced
this pull request
Oct 7, 2020
From observation in the nightly environment we can see that occasionally the phrase and term query may take >300ms and >1000ms. This leads to unnecessary spikes in the latency charts. Relates to elastic/elasticsearch#61957
ebadyano
added a commit
to elastic/rally-tracks
that referenced
this pull request
Oct 7, 2020
From observation in the nightly environment we can see that occasionally the phrase and term query may take >300ms and >1000ms. This leads to unnecessary spikes in the latency charts. Relates to elastic/elasticsearch#61957
ebadyano
added a commit
to elastic/rally-tracks
that referenced
this pull request
Oct 7, 2020
From observation in the nightly environment we can see that occasionally the phrase and term query may take >300ms and >1000ms. This leads to unnecessary spikes in the latency charts. Relates to elastic/elasticsearch#61957
ebadyano
added a commit
to elastic/rally-tracks
that referenced
this pull request
Oct 7, 2020
From observation in the nightly environment we can see that occasionally the phrase and term query may take >300ms and >1000ms. This leads to unnecessary spikes in the latency charts. Relates to elastic/elasticsearch#61957
ebadyano
added a commit
to elastic/rally-tracks
that referenced
this pull request
Oct 7, 2020
From observation in the nightly environment we can see that occasionally the phrase and term query may take >300ms and >1000ms. This leads to unnecessary spikes in the latency charts. Relates to elastic/elasticsearch#61957
ebadyano
added a commit
to elastic/rally-tracks
that referenced
this pull request
Oct 7, 2020
From observation in the nightly environment we can see that occasionally the phrase and term query may take >300ms and >1000ms. This leads to unnecessary spikes in the latency charts. Relates to elastic/elasticsearch#61957 # Conflicts: # geonames/challenges/default.json
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit upgrades Elasticsearch to a Lucene 8.7.0 snapshot.