tolitius / chazel Goto Github PK

I know there is a 1.6 snapshot, but it's not published currently. This problem may be changed by now.

Since we can send arbitrary functions, why can't I send something like...

(partial eval '(defn say [arg] (println arg)))

?

This is serializable. It should be interpreted on the cluster instance. Basically should provide a means to patch things at runtime and distribute stuff over the cluster. As it stands, nothing seems to happen. Certainly no changes to the namespace, but no errors either. I do get errors if I send a repl-generated function, like (fn [] ...) as a Runnable, since the classloader complains. Again, this could be a function of older versions though.

In principle it seems like this should be possible, and it would add a degree of flexibility (e.g. I don't have to AOT compile everything and distribute as a dependency to ensure identical classes, etc.). I guess the other option is to have a simple function/message handler that uses ns-resolve to find the function and the like.

Just curious if I am running against architectural constraints or not.

The text before a list says
chazel has all 3 listeners available as wrapper functions and ready to roll
when it appears that there are 4 listener types.

This was probably missed a few days ago when evicted-entry listeners were added.

Hi there,

I'm sure you're aware but one of Hazelcast's offerings is a distributed IAtomicReference. On top of this, one can build a distributed atom - e.g. https://github.com/jimpil/hazel-atom/blob/master/src/hazel_atom/core.clj.

Are you interested in this? Perhaps the implementation can be further improved given Hazelcast v5, or maybe not - i haven't exactly looked at it recently...in any case, having a distributed atom would be a neat feature, right?

Hello!

Currently your project.clj contains [com.hazelcast/hazelcast "3.5.3"] and [com.hazelcast/hazelcast-client "3.5.3"] dependencies. These deps can hang client during connection to a cluster.
I've updated my project.clj like this and now I can connect to hazelcast 3.6 (docker image)

             [com.hazelcast/hazelcast "3.6"]
             [com.hazelcast/hazelcast-client "3.6"]
             [chazel "0.1.7"
              :exclusions [com.hazelcast/hazelcast com.hazelcast/hazelcast-client]] ;caching

this thread hazelcast/hazelcast#5815 tells that hazelcast 3.5 have some bugs.

Mike.

Hazelcast 3.11 introduced a new event type, "LOADED"

See https://docs.hazelcast.org/docs/3.12.1/javadoc/com/hazelcast/core/EntryEventType.html#LOADED

This is missing from https://github.com/tolitius/chazel/blob/master/src/chazel/core.clj#L18
but the list isn't complete anyway as there are EXPIRED and REMOVED events that don't seem to be covered

Hi,

1st of all I would like to say thank you for the great work.

Do you have any plans to implement a simple MapStore implementation
that would allow any storage backend to be plugged into HazelCast?

I would love to contribute to such a feature if required.