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

Revert build breaking change from Lucene upgrade to 9.3.0 #1994

Closed
wants to merge 1 commit into from

Conversation

cwperks
Copy link
Member

@cwperks cwperks commented Aug 4, 2022

Signed-off-by: Craig Perkins cwperx@amazon.com

Description

Reverts #1990. Core is reverting the Lucene upgrade for a future release and we will re-apply this change in tandem.

  • Category (Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation)

Maintenance

Check List

  • New functionality includes testing
  • New functionality has been documented
  • Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Signed-off-by: Craig Perkins <cwperx@amazon.com>
@peternied
Copy link
Member

@cwperks Is there a tracking issue on OpenSearch?

@cwperks cwperks closed this Aug 5, 2022
@peternied
Copy link
Member

@cwperks It seems like there was more of a story here, could you help me understand what happened?

@cwperks
Copy link
Member Author

cwperks commented Aug 8, 2022

@peternied There was some back-and-forth regarding whether the Lucene 9.3.0 upgrade should be moved to a future release or included in the 2.2.0 release. This PR was drafted to revert the coordinated change in security in the event that core decided to downgrade back to Lucene 9.2.0.

@peternied
Copy link
Member

@cwperks Thanks for the context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants