Bump hazelcast.version from 5.0.2 to 5.2.0 in /hazelcast-node

[dependabot]

Bumps hazelcast.version from 5.0.2 to 5.2.0.
Updates hazelcast from 5.0.2 to 5.2.0

Release notes

Sourced from hazelcast's releases.

v5.2.0

This document lists the new features, enhancements, fixed issues and, removed or deprecated features for Hazelcast Platform v5.2.0 release. The numbers in the square brackets refer to the issues and pull requests in Hazelcast's GitHub repository.

New Features

• SQL stream-to-stream joins: You can now correlate multiple streams of data with each other using the relational join operation.
• Generic MapStore (BETA): You no longer need to write Java code to get data from an external data store, such as a relational database, into Hazelcast by implementing the MapStore or MapLoader interfaces.
• JDBC connector (BETA): You can now use SQL to connect to and query any database that supports the JDBC interface.
• CP Subsystem Leadership Priority: To ensure the availability of the CP subsystem, you can now transfer CP member leadership to another member: There are cases when some CP members should not act as a leader. For example, a member with high load would not be a good leader, or, in a WAN deployment, members in a primary datacenter may be preferred in order to minimize the latency between the clients and leader. You can transfer the leadership using the cp-member-priority configuration element. See Configuring Leadership Priority.
• User Defined Types (Experimental): You can now query nested objects within Java, compact, and portable mappings using the User Defined Types (UDTs).

Breaking Changes

• Introduced a check to control the versions of Hazelcast Platform members and Hazelcast CLI are matched. Previously, it was possible to submit a job using a different version of CLI from the member version. Generally, it would work when there were no change in the serialized form of pipeline. Now, Hazelcast fails earlier in this case. #22224
• Removed the BETA annotations from the compact serialization and GenericRecord related classes, i.e., they are stable. Now, compact serialization is enabled by default; the enabled attribute within the compact-serialization configuration block does not exist anymore. #21997

Enhancements

Performance

• MapStore Offloading: Added offload element to map store configuration. It is used to offload map store and loader operations for each map in the cluster. This way, a map store operation does not block the next operations by blocking a partition thread indefinitely. Partition threads are one of the most important shared resources in a cluster; this offloading enables faster completion of the operations in these threads. See Offloading MapStore and MapLoader Operations. #21651

SQL Engine

• Multiple performance enhancements in the SQL engine.

Distribution

• Removed hazelcast-hibernate53 dependency from the main Hazelcast Platform distribution as it is not needed anymore. #22282
• Minor versions of Hazelcast Platform are now released as X.Y.0, instead of the previous X.Y versioning scheme. #22218

Serialization

• Added support of List, ArrayList, Set, HashSet, Map, and HashMap for the zero-config serializers. #21980

• Added a check to the array of Compact and GenericRecord object fields, that does not allow different item types and schemas in such fields. #21958

• Moved the GenericRecord and GenericRecordBuilder interfaces to the new serialization.genericrecord package. #21955

• In case there is a field type that is not supported by the reflective serializer, now Hazelcast fails with an exception; all JDK classes are now excluded from the zero-config serialization, meaning, they cannot be used as types, field types, or array component types in the reflective serializers. #21918

• Hazelcast now does not provide methods to read a default value in case of a missing field in the data. Instead, the following method has been introduced in CompactReader to check the existence of a field with its name and kind.+

  FieldKind getFieldKind(String fieldName);

  You can use this method for fields that have changed or have a potential to change in the future. #21876

• Moved the type-name and class configuration elements into the compact-serialization block. Removed the registered-classes element. #21861

• Renamed the cloneWithBuilder() method as newBuilderWithClone() in the GenericRecord class. #21730

• Added support for char fields in the compact serialization format. With this, char, char[], Character, and Character[] fields are now supported in the reflective compact serializers. #21054

Configuration

... (truncated)

Commits

• 1ab7271 version update for 5.2.0 release
• e2669d0 Handle null in creation of KubernetesDiscoveryStrategy (#22585)
• 58648d1 Start k8s sts monitor only when tracker enabled [5.2.0] (#22548)
• 184c69b Finalizing 5.2.0 OS release notes.
• da72b39 Sort postgres error codes alphabetically [5.2.0] (#22545)
• 21eea8f Update protobuf to 3.19.6 (#22544)
• 2f7ea3b Add index only on local during MapProxy init [5.2.0] (#22503)
• 2b4d98f Improvements for running Hazelcast persistence on kubernetes [5.2.0] (#22501)
• 814709e Update Hazelcast 3 dependency [5.2.0] (#22469)
• 6b753ca Address Viliam's comments.
• Additional commits viewable in compare view

Updates hazelcast-jet-cdc-mysql from 5.0.2 to 5.2.0

Updates hazelcast-jet-cdc-debezium from 5.0.2 to 5.2.0

Updates hazelcast-jet-elasticsearch-7 from 5.0.2 to 5.2.0

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 commands and options

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)

[dependabot]

Superseded by #53.