Functionality break issues with maven-org-opensearch-client_opensearch-java 2.14

The issue you're experiencing with maven-org-opensearch-client_opensearch-java 2.14 is likely related to breaking changes introduced in newer versions of the OpenSearch client library. When upgrading from version 2.6 to 2.14, it's common to encounter compatibility issues, especially with parsing responses.

To resolve this problem, you'll need to update your code to accommodate the changes in the newer version of the OpenSearch client. Here are some steps you can take:

1. Review the changelog or release notes for the OpenSearch client library to identify any breaking changes between version 2.6 and 2.14.

2. Update your dependency management system to ensure all related libraries are compatible with the new version of the OpenSearch client.

3. Check for any changes in the API or response structure that might affect how you're parsing the response.get.source as an ObjectNode.

4. Verify that your Jackson library versions (jackson-databind and jackson-datatype-jsr310) are compatible with the new OpenSearch client version. You may need to upgrade these as well.

5. If you're using any custom serializers or deserializers, make sure they're updated to work with the new version.

6. Test your code thoroughly after making these changes to ensure all functionality is working as expected.

If you continue to face issues, you may want to consider temporarily rolling back to the previous working version (2.6) while you investigate and resolve the compatibility problems. Alternatively, you could set up a test environment to experiment with the changes required for the new version without affecting your production system.

Remember that when upgrading major versions of libraries, it's always a good practice to review the documentation, test extensively, and be prepared for potential breaking changes.
Sources
An automated approach to perform an in-place engine upgrade in Amazon OpenSearch Service | AWS Big Data Blog

Dear Customer,

I hope you are doing well !

Thank you for reaching out regarding the issue you're experiencing after upgrading the OpenSearch client library from version 2.6 to 2.14. I understand that you're encountering difficulties parsing the response.get.source as an ObjectNode after the upgrade, even though this worked correctly in the previous version.

Please feel free to correct me if my understanding of the issue differs, and I encourage you to share any additional details you think might be helpful.

To investigate further, could you kindly provide the Amazon OpenSearch domain ARN you're working with? Additionally, I’d appreciate it if you could elaborate on the specific operation you were performing when you first encountered this issue— whether it was a search, or any other action. Could you please elaborate your issue a little more ?

I would be happy to assist on a best-effort basis. The problem you're experiencing seems likely due to breaking changes introduced in the newer version of the OpenSearch client library (2.14). Upgrading from one major version to another can sometimes cause compatibility issues, particularly with how responses are parsed or handled.

To assist you further, here are a few steps you might consider:

• Review the change log or release notes for the OpenSearch client library to identify any breaking changes between version 2.6 and 2.14.

• Update your dependency management system to ensure all related libraries are compatible with the new version of the OpenSearch client.

• Check for any changes in the API or response structure that might affect how you're parsing the response.get.source as an ObjectNode.

• Test your code thoroughly after making these changes to ensure all functionality is working as expected.

As my area of expertise lies primarily with troubleshooting underlying issues and supporting AWS OpenSearch/Elasticsearch clusters, my ability to provide assistance with Java coding issues is somewhat limited. While I would be happy to try to assist on a best-effort basis, I want to ensure that we do not add unnecessary complexity to your case by delving too deeply into code-related concerns outside of my area of focus.

That being said, if you have any cluster-related questions or need help with diagnosing issues within the OpenSearch domain itself, I would be glad to help in any way I can.

Please don’t hesitate to share more details or let me know if you need any further clarification. I’m here to support you as best as possible!

Thanks !