Skip to content

[Snyk] Security upgrade org.apache.solr:solr-solrj from 8.11.1 to 9.0.0 - #770

Open
pushkala-datastax wants to merge 1 commit into
2.10_dsfrom
snyk-fix-729da2705f0e77b06714c0fdf3ba2f64
Open

[Snyk] Security upgrade org.apache.solr:solr-solrj from 8.11.1 to 9.0.0#770
pushkala-datastax wants to merge 1 commit into
2.10_dsfrom
snyk-fix-729da2705f0e77b06714c0fdf3ba2f64

Conversation

@pushkala-datastax

Copy link
Copy Markdown
Collaborator

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

  • pulsar-io/solr/pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue Score Upgrade
high severity Infinite loop
SNYK-JAVA-IONETTY-18230935
  721   org.apache.solr:solr-solrj:
8.11.1 -> 9.0.0
Major version upgrade No Known Exploit

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

@pushkala-datastax

Copy link
Copy Markdown
Collaborator Author

Merge Risk: High

This major version upgrade from Solr 8.x to 9.0.0 introduces significant breaking changes that require developer action. The upgrade involves a mandatory Java version bump, critical changes to the SolrJ client libraries, and the removal of major server-side features.

Key Breaking Changes:

  • Java 11 Requirement: Solr 9.0.0 requires a minimum Java version of 11 to run. Any application using the solr-solrj client must be running in a Java 11 or later environment.
  • CloudSolrClient Refactoring: The primary client for SolrCloud, CloudSolrClient, has been significantly changed. It now supports HTTP/2 and uses a new Builder for instantiation. The previous client implementation has been renamed to CloudLegacySolrClient and is now deprecated. Code that creates CloudSolrClient instances will break and must be updated.
  • New ZooKeeper Dependency: ZooKeeper-related dependencies have been extracted from the main solr-solrj artifact into a new solr-solrj-zookeeper module. Applications using CloudSolrClient must now explicitly add this new dependency to their build.
  • Client Deprecations: HttpSolrClient and LBHttpSolrClient are now deprecated due to their lack of HTTP/2 support.
  • Removed Server-Side Features: Several major features have been completely removed from the Solr server, and any client code interacting with them will fail. This includes the Data Import Handler (DIH), the autoscaling framework, and Cross-Data Center Replication (CDCR).

Recommendation:
This is a high-impact upgrade. Developers must:

  1. Ensure the application environment is updated to Java 11 or newer.
  2. Update CloudSolrClient instantiation to use the new builder pattern.
  3. Add the org.apache.solr:solr-solrj-zookeeper dependency if using SolrCloud.
  4. Review code for any interaction with removed features like DIH or autoscaling APIs and refactor accordingly.

Source: Apache Solr 9.0 Release Notes, Solr 9 Upgrade Guide

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

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