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

Upgrade to lucene-5.1.0-snapshot-1671894. #10468

Merged
merged 1 commit into from Apr 7, 2015

Conversation

jpountz
Copy link
Contributor

@jpountz jpountz commented Apr 7, 2015

This includes a fix for LUCENE-6406.

This includes a fix for LUCENE-6406.
@rmuir
Copy link
Contributor

rmuir commented Apr 7, 2015

+1

jpountz added a commit that referenced this pull request Apr 7, 2015
Upgrade to lucene-5.1.0-snapshot-1671894.
@jpountz jpountz merged commit a24d898 into elastic:master Apr 7, 2015
dadoonet added a commit to elastic/elasticsearch-parent that referenced this pull request Apr 9, 2015
@dadoonet
Copy link
Member

dadoonet commented Apr 9, 2015

Also pushed in parent project: elastic/elasticsearch-parent@998793f

@clintongormley clintongormley added :Core/Infra/Core Core issues without another label and removed >enhancement labels Aug 25, 2015
javanna added a commit to javanna/elasticsearch that referenced this pull request Feb 6, 2024
The newly introduced QueryPhaseTimeoutException extends from QueryPhaseExecutionException.
It can instead subclass directly SearchException. That allows us to enforce that QueryPhaseExecutionException
always has a root cause provided, which helps us enforce that its status code never defaults to 500.

These are no serialization changes involved in this change, as QueryPhaseExecutionException exposes the exact same
instance members as SearchException, which get serialized over the wire.

This change does rename the transport version contant introduced in elastic#10468, but that is safe as the version id
is left untouched. It is a cosmetic change to ensure consistency between the constant name and the now renamed exception.
javanna added a commit that referenced this pull request Feb 6, 2024
The newly introduced QueryPhaseTimeoutException extends from QueryPhaseExecutionException.
It can instead subclass directly SearchException. That allows us to enforce that QueryPhaseExecutionException
always has a root cause provided, which helps us enforce that its status code never defaults to 500.

These are no serialization changes involved in this change, as QueryPhaseExecutionException exposes the exact same
instance members as SearchException, which get serialized over the wire.

This change does rename the transport version contant introduced in #10468, but that is safe as the version id
is left untouched. It is a cosmetic change to ensure consistency between the constant name and the now renamed exception.
felixbarny pushed a commit to felixbarny/elasticsearch that referenced this pull request Feb 8, 2024
…105182)

The newly introduced QueryPhaseTimeoutException extends from QueryPhaseExecutionException.
It can instead subclass directly SearchException. That allows us to enforce that QueryPhaseExecutionException
always has a root cause provided, which helps us enforce that its status code never defaults to 500.

These are no serialization changes involved in this change, as QueryPhaseExecutionException exposes the exact same
instance members as SearchException, which get serialized over the wire.

This change does rename the transport version contant introduced in elastic#10468, but that is safe as the version id
is left untouched. It is a cosmetic change to ensure consistency between the constant name and the now renamed exception.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Core/Infra/Core Core issues without another label >upgrade v2.0.0-beta1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants