cunningt opened a new pull request, #21551:
URL: https://github.com/apache/camel/pull/21551

   # Description
   
   In Hazelcast 5.5+, the CP subsystem is removed from the community edition, 
and is only available in the enterprise edition.
   
   It appears like if we move to hazelcast 5.5+, the hazelcast-atomicvalue 
(atomicnumber) component either needs to be removed or the data structure 
backing it needs to change - the IAtomicLong it uses is a CP subsystem only 
feature https://docs.hazelcast.com/hazelcast/5.6/data-structures/iatomiclong .  
  We can replace most of the functionality with a PNCounter 
https://docs.hazelcast.com/hazelcast/5.6/data-structures/pn-counter with one 
limitation - PNCounter does not offer a compare/compareAndSet method.      I 
think offering a new component here (hazelcast-pncounter) seems like a better 
approach because it is more descriptive of the underlying data structure used 
and because we would be removing significant functionality because no 
compareAndSet is available.
   
   We should deprecate hazelcast-atomicvalue (atomicnumber) in 4.19.0 and 
create a hazelcast-pncounter to replace it.    We can then safely remove 
hazelcast-atomicvalue in a future release and safely upgrade to hazelcast 5.5.0 
or 5.6.0.
   
   
   # Target
   
   - [ x] I checked that the commit is targeting the correct branch (Camel 4 
uses the `main` branch)
   
   # Tracking
   - [x ] If this is a large change, bug fix, or code improvement, I checked 
there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for 
the change (usually before you start working on it).
   
   # Apache Camel coding standards and style
   
   - [x ] I checked that each commit in the pull request has a meaningful 
subject line and body.
   
   - [x ] I have run `mvn clean install -DskipTests` locally from root folder 
and I have committed all auto-generated changes.
   
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to