dependabot[bot] opened a new pull request, #1277: URL: https://github.com/apache/cxf/pull/1277
Bumps `cxf.hazelcast.version` from 5.2.3 to 5.3.0. Updates `hazelcast` from 5.2.3 to 5.3.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/hazelcast/hazelcast/releases";>hazelcast's releases</a>.</em></p> <blockquote> <h2>v5.3.0-BETA-2</h2> <p>This document lists the new features, enhancements, fixed issues and, removed or deprecated features for Hazelcast Platform 5.3-BETA-2 release. The numbers in the square brackets refer to the issues and pull requests in Hazelcast's GitHub repository.</p> <h2>New Features</h2> <ul> <li><strong>Connector for Kafka Connect source</strong>: Import data from an external system directly into a Hazelcast data pipeline without the need of a Kafka cluster.</li> <li><strong>Partition-Aware SQL Client</strong>: Send the SQL commands only to the members having the relevant data, which reduces the network hops and improves the query performances.</li> <li><strong>Connector for MongoDB</strong>: Set up read-through/write-through caching in MongoDB via this connector without writing any code.</li> </ul> <h2>Breaking Changes</h2> <ul> <li>Renamed the <code>DataLinkFactory</code> interface as <code>DataConnection</code>. <a href="https://redirect.github.com/hazelcast/hazelcast/issues/24224";>#24224</a></li> <li>Changed the default cloud coordinator URL from <code>coordinator.hazelcast.cloud</code> to <code>api.viridian.hazelcast.com</code>. The default configuration now connects to <a href="https://viridian.hazelcast.com/sign-in?next=/%5BHazelcast";>https://viridian.hazelcast.com/sign-in?next=/[Hazelcast</a> Viridian^] instead of Hazelcast Cloud. If you want to continue accessing your Hazelcast Cloud clusters, you need to set the <code>hazelcast.client.cloud.url</code> property to <code>https://coordinator.hazelcast.cloud</code> in your configuration. <a href="https://redirect.github.com/hazelcast/hazelcast/issues/23290";>#23290</a></li> </ul> <h2>Enhancements</h2> <h3>Cloud</h3> <ul> <li>Hazelcast was sending requests to Kubernetes API when deploying an application with embedded Hazelcast and <code>service-dns</code> (DNS lookup mode) specified to a Kubernetes cluster. This was causing the requests to be unsuccessful and the application not to start. This mechanism has been improved by creating Kubernetes client only for the DNS lookup mode. <a href="https://redirect.github.com/hazelcast/hazelcast/issues/23883";>#23883</a></li> <li>When advanced networking is enabled, the Kubernetes discovery plugin might have been discovering several endpoints (per each port) for each member's pod. The discovery plugin now matches only the private IP per endpoint, ignoring the port values. <a href="https://redirect.github.com/hazelcast/hazelcast/issues/23766";>#23766</a></li> <li>Added support of link:<a href="https://aws.amazon.com/about-aws/whats-new/2022/10/amazon-machine-images-support-instance-metadata-service-version-2-default/#:~:text=Posted%20On%3A%20Oct%203%2C%202022,depth%20against%20unauthorized%20metadata%20access.%5BIMDSv2%5E%5D";>https://aws.amazon.com/about-aws/whats-new/2022/10/amazon-machine-images-support-instance-metadata-service-version-2-default/#:~:text=Posted%20On%3A%20Oct%203%2C%202022,depth%20against%20unauthorized%20metadata%20access.[IMDSv2^]</a> for Hazelcast's AWS Discovery plugin. <a href="https://redirect.github.com/hazelcast/hazelcast/issues/23545";>#23545</a></li> <li>Enhanced the handling of errors coming from the Kubernetes API: ** Not detecting the intent correctly whenever the cluster is shutdown, so the cluster was not restarted successfully. ** Extensive amount of Kubernetes API calls were being logged when Automatic State Management feature is enabled. <a href="https://redirect.github.com/hazelcast/hazelcast/issues/23538";>#23538</a></li> <li>Added the support of discovering ECS and EC2 members on AWS. See [Deploying a Cluster on Amazon AWS]. <a href="https://redirect.github.com/hazelcast/hazelcast/pull/22411%5B#22411%5D(https://redirect.github.com/hazelcast/hazelcast/issues/22411)">hazelcast/hazelcast#22411</a></li> <li>Enhanced the experience of using Hazelcast with persistence under Kubernetes by removing requirements for manual interventions. Previously, when there is a restart on such a cluster, the cluster states were needed to be changed manually. For some cases, this might have led to data loss. Now, the shutdown process is automated. See [Configuring Kubernetes] for details. <a href="https://redirect.github.com/hazelcast/hazelcast/issues/21844";>#21844</a></li> </ul> <h3>Storage</h3> <ul> <li>Disk tier option of Tiered Storage is now disabled by default. <a href="https://redirect.github.com/hazelcast/hazelcast/issues/23747";>#23747</a></li> </ul> <h3>Distribution</h3> <ul> <li>Added the Kafka connector to the distribution. <a href="https://redirect.github.com/hazelcast/hazelcast/issues/23312";>#23312</a></li> <li>Shaded dependencies for Hazelcast Platform have been combined in a dedicated package (<code>com.hazelcast.shaded</code>). <a href="https://redirect.github.com/hazelcast/hazelcast/issues/23124";>#23124</a></li> </ul> <h3>Networking</h3> <ul> <li>Added socket options for per-socket keep-alive configuration: <code>keep-count</code>, <code>keep-idle-seconds</code>, and <code>keep-interval-seconds</code>. You can set these options using either the advanced network configurations or Hazelcast system properties. See [Configuring TCP Keep-Alive]. <a href="https://redirect.github.com/hazelcast/hazelcast/issues/23816";>#23816</a>, <a href="https://redirect.github.com/hazelcast/hazelcast/issues/24050";>#24050</a></li> </ul> <h3>SQL Engine</h3> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/hazelcast/hazelcast/commits";>compare view</a></li> </ul> </details> <br /> Updates `hazelcast-spring` from 5.2.3 to 5.3.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/hazelcast/hazelcast/releases";>hazelcast-spring's releases</a>.</em></p> <blockquote> <h2>v5.3.0-BETA-2</h2> <p>This document lists the new features, enhancements, fixed issues and, removed or deprecated features for Hazelcast Platform 5.3-BETA-2 release. The numbers in the square brackets refer to the issues and pull requests in Hazelcast's GitHub repository.</p> <h2>New Features</h2> <ul> <li><strong>Connector for Kafka Connect source</strong>: Import data from an external system directly into a Hazelcast data pipeline without the need of a Kafka cluster.</li> <li><strong>Partition-Aware SQL Client</strong>: Send the SQL commands only to the members having the relevant data, which reduces the network hops and improves the query performances.</li> <li><strong>Connector for MongoDB</strong>: Set up read-through/write-through caching in MongoDB via this connector without writing any code.</li> </ul> <h2>Breaking Changes</h2> <ul> <li>Renamed the <code>DataLinkFactory</code> interface as <code>DataConnection</code>. <a href="https://redirect.github.com/hazelcast/hazelcast/issues/24224";>#24224</a></li> <li>Changed the default cloud coordinator URL from <code>coordinator.hazelcast.cloud</code> to <code>api.viridian.hazelcast.com</code>. The default configuration now connects to <a href="https://viridian.hazelcast.com/sign-in?next=/%5BHazelcast";>https://viridian.hazelcast.com/sign-in?next=/[Hazelcast</a> Viridian^] instead of Hazelcast Cloud. If you want to continue accessing your Hazelcast Cloud clusters, you need to set the <code>hazelcast.client.cloud.url</code> property to <code>https://coordinator.hazelcast.cloud</code> in your configuration. <a href="https://redirect.github.com/hazelcast/hazelcast/issues/23290";>#23290</a></li> </ul> <h2>Enhancements</h2> <h3>Cloud</h3> <ul> <li>Hazelcast was sending requests to Kubernetes API when deploying an application with embedded Hazelcast and <code>service-dns</code> (DNS lookup mode) specified to a Kubernetes cluster. This was causing the requests to be unsuccessful and the application not to start. This mechanism has been improved by creating Kubernetes client only for the DNS lookup mode. <a href="https://redirect.github.com/hazelcast/hazelcast/issues/23883";>#23883</a></li> <li>When advanced networking is enabled, the Kubernetes discovery plugin might have been discovering several endpoints (per each port) for each member's pod. The discovery plugin now matches only the private IP per endpoint, ignoring the port values. <a href="https://redirect.github.com/hazelcast/hazelcast/issues/23766";>#23766</a></li> <li>Added support of link:<a href="https://aws.amazon.com/about-aws/whats-new/2022/10/amazon-machine-images-support-instance-metadata-service-version-2-default/#:~:text=Posted%20On%3A%20Oct%203%2C%202022,depth%20against%20unauthorized%20metadata%20access.%5BIMDSv2%5E%5D";>https://aws.amazon.com/about-aws/whats-new/2022/10/amazon-machine-images-support-instance-metadata-service-version-2-default/#:~:text=Posted%20On%3A%20Oct%203%2C%202022,depth%20against%20unauthorized%20metadata%20access.[IMDSv2^]</a> for Hazelcast's AWS Discovery plugin. <a href="https://redirect.github.com/hazelcast/hazelcast/issues/23545";>#23545</a></li> <li>Enhanced the handling of errors coming from the Kubernetes API: ** Not detecting the intent correctly whenever the cluster is shutdown, so the cluster was not restarted successfully. ** Extensive amount of Kubernetes API calls were being logged when Automatic State Management feature is enabled. <a href="https://redirect.github.com/hazelcast/hazelcast/issues/23538";>#23538</a></li> <li>Added the support of discovering ECS and EC2 members on AWS. See [Deploying a Cluster on Amazon AWS]. <a href="https://redirect.github.com/hazelcast/hazelcast/pull/22411%5B#22411%5D(https://redirect.github.com/hazelcast/hazelcast/issues/22411)">hazelcast/hazelcast#22411</a></li> <li>Enhanced the experience of using Hazelcast with persistence under Kubernetes by removing requirements for manual interventions. Previously, when there is a restart on such a cluster, the cluster states were needed to be changed manually. For some cases, this might have led to data loss. Now, the shutdown process is automated. See [Configuring Kubernetes] for details. <a href="https://redirect.github.com/hazelcast/hazelcast/issues/21844";>#21844</a></li> </ul> <h3>Storage</h3> <ul> <li>Disk tier option of Tiered Storage is now disabled by default. <a href="https://redirect.github.com/hazelcast/hazelcast/issues/23747";>#23747</a></li> </ul> <h3>Distribution</h3> <ul> <li>Added the Kafka connector to the distribution. <a href="https://redirect.github.com/hazelcast/hazelcast/issues/23312";>#23312</a></li> <li>Shaded dependencies for Hazelcast Platform have been combined in a dedicated package (<code>com.hazelcast.shaded</code>). <a href="https://redirect.github.com/hazelcast/hazelcast/issues/23124";>#23124</a></li> </ul> <h3>Networking</h3> <ul> <li>Added socket options for per-socket keep-alive configuration: <code>keep-count</code>, <code>keep-idle-seconds</code>, and <code>keep-interval-seconds</code>. You can set these options using either the advanced network configurations or Hazelcast system properties. See [Configuring TCP Keep-Alive]. <a href="https://redirect.github.com/hazelcast/hazelcast/issues/23816";>#23816</a>, <a href="https://redirect.github.com/hazelcast/hazelcast/issues/24050";>#24050</a></li> </ul> <h3>SQL Engine</h3> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/hazelcast/hazelcast/commits";>compare view</a></li> </ul> </details> <br /> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cxf.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
