Id like to be able to disable default Java serialization via global property or command line flag · hazelcast/hazelcast#11925

(0 comments) (2 reactions) (0 assignees)Java (5,737 stars) (1,795 forks)batch import

Estimation: MModule: SerializationPriority: LowSource: InternalTeam: ClientTeam: CoreType: Enhancementgood first issue

Description

Id like to be able to report on usages of default Java serialization and, separately, completely disable Java serialization within my HZ cluster via a command line flag and/or config property. Being able to report on usages of it would be helpful to teams in implementing more efficient serialization mechanisms - so perhaps report only the first instance of a specific class being serialized using the default mechanism so as not to spam the logs (store the seen class names in a Set<>). Ultimately, Id like to disable it completely so that new code doesn't accidentally utilize the default serialization mechanism. There's a workaround if I provide my own custom Global serializer, but I'd like this out of the box since toggling a flag is much easier to do on site than providing custom code and having it deployed.

Contributor guide

Tech stack: java
Domain: backendperformance
Issue type: feature
Difficulty: 3
Estimated time: 3-5 days
Activity status: stale
Clarity: clear
Prerequisites: Understanding of Java serializationFamiliarity with Hazelcast configuration
Newbie friendliness: 30
Research direction: The issue requests a global flag to disable default Java serialization and optionally log usages. Start by examining how Hazelcast currently handles serialization, specifically in classes like SerializationConfig or Config. Look for existing properties that control serialization behavior. Also check if there are any related PRs or discussions. The solution would involve adding a new configuration property and implementing a custom serialization service that respects this flag. Since the issue is old, verify current codebase state before proceeding.