-
Notifications
You must be signed in to change notification settings - Fork 1.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
[Remove] Remove deprecated methods from JodaCompatibleZonedDateTime which are called by scripts #3346
Conversation
❌ Gradle Check failure 68f49f4f93b2df18c7c805aeb8e1ce5f130c423e |
@@ -427,120 +401,7 @@ public ZonedDateTime withZoneSameInstant(ZoneId zone) { | |||
return dt.withZoneSameInstant(zone); | |||
} | |||
|
|||
@Deprecated |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you also looking at backporting this to 2.0?
If not, can we start curating a breaking changes meta issue for 3.0?
This is a breaking change and there could be plugins in the wild using these methods.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, sorry, forgot to add the labels.
start gradle check |
@reta precommit is failing because of a forbidden API:
|
❌ Gradle Check failure 68f49f4f93b2df18c7c805aeb8e1ce5f130c423e |
❌ Gradle Check failure 1562f9ff898feb42ff7cf4f294035fc81d10d1d9 |
…called by scripts Signed-off-by: Andriy Redko <andriy.redko@aiven.io>
I believe this might be a large breaking change to get merged into 2.0. OpenSearch Dashboards and visualizes utilizes painless scripts. I did not expect that we were removing this for 2.0 so a lot of tests are failing and I can see others who have their painless scripts defined will need to ensure update them prior to migrating to OpenSearch 2.0. It's okay but I think this is a huge impact to the community and even I was caught by surprise even though I'm a maintainer on OpenSearch Dashboards. Maybe I missed this heads up but was this called out a head of time? |
@kavilla its fair. Ideally deprecated method usage should have been migrated. But we agree it was not the right practice we removed it after launching RC1. It should have been in the RC1 but we missed the train. @reta I'll go revert this in 2.0, 2.x line and let it go out in 3.x to unblock the build for 2.0 release. I've removed the entry in 2.0 breaking changes(#2480) and added this into 3.0 (#3351) |
@saratvemulapalli sounds good, thank you, sorry for that @kavilla |
@kavilla I will create an issue on OpenSearch Dashboards, the deprecated methods introduce significant overhead because of the deprecation logger (vs actual useful work the methods do), we have to migrate the scripts to use the non-deprecated variants. |
Sample data and functional tests were utilizing deprecated methods for painless scripts. However these deprecated methods were removed in: opensearch-project/OpenSearch#3346 This is to ensure sample data and ftr tests work but end users saved objects might contain painless scripts that we might not be able to address. So we should research if this it is possible to help mitigate this. Related issue: opensearch-project#1600 Signed-off-by: Kawika Avilla <kavilla414@gmail.com>
* [Build][Tests] handle painless scripts update Sample data and functional tests were utilizing deprecated methods for painless scripts. However these deprecated methods were removed in: opensearch-project/OpenSearch#3346 This is to ensure sample data and ftr tests work but end users saved objects might contain painless scripts that we might not be able to address. So we should research if this it is possible to help mitigate this. Related issue: #1600 Signed-off-by: Kawika Avilla <kavilla414@gmail.com>
* [Build][Tests] handle painless scripts update Sample data and functional tests were utilizing deprecated methods for painless scripts. However these deprecated methods were removed in: opensearch-project/OpenSearch#3346 This is to ensure sample data and ftr tests work but end users saved objects might contain painless scripts that we might not be able to address. So we should research if this it is possible to help mitigate this. Related issue: opensearch-project#1600 Signed-off-by: Kawika Avilla <kavilla414@gmail.com>
* [Build][Tests] handle painless scripts update Sample data and functional tests were utilizing deprecated methods for painless scripts. However these deprecated methods were removed in: opensearch-project/OpenSearch#3346 This is to ensure sample data and ftr tests work but end users saved objects might contain painless scripts that we might not be able to address. So we should research if this it is possible to help mitigate this. Related issue: opensearch-project#1600 Signed-off-by: Kawika Avilla <kavilla414@gmail.com>
* Revert "Remove deprecated methods from JodaCompatibleZonedDateTime which are called by scripts (#3346) (#3347)" This reverts commit 3537b5a. Signed-off-by: Sarat Vemulapalli <vemulapallisarat@gmail.com> * Bumping 2.x to 2.2 Signed-off-by: Sarat Vemulapalli <vemulapallisarat@gmail.com> * Updating lucene verion for 2.1 Signed-off-by: Sarat Vemulapalli <vemulapallisarat@gmail.com>
* [Build][Tests] handle painless scripts update Sample data and functional tests were utilizing deprecated methods for painless scripts. However these deprecated methods were removed in: opensearch-project/OpenSearch#3346 This is to ensure sample data and ftr tests work but end users saved objects might contain painless scripts that we might not be able to address. So we should research if this it is possible to help mitigate this. Related issue: opensearch-project#1600 Signed-off-by: Kawika Avilla <kavilla414@gmail.com>
Signed-off-by: Andriy Redko andriy.redko@aiven.io
Description
There are number of deprecated methods in
JodaCompatibleZonedDateTime
which are still available in scripts. Those should be removed since in some cases they pose significant performance overhead (due to deprecation warnings).Issues Resolved
Closes #3156 and #3345
Check List
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.