[infinispan-dev] Write-only commands

Radim Vansa rvansa at redhat.com
Tue Jun 27 03:31:08 EDT 2017


Hi,

I am working on entry version history (again). In Como we've discussed 
that previous values are needed for (continuous) query and reliable 
listeners, so I wonder what should we do with functional write-only 
commands. These are different to commands with flags, because flags 
(other than ignore return value) are expected to break something. I see 
the available options as:

1) run write-only commands 'optimized', ignoring any querying and such 
(warn user that he will break it)

2) run write-only without any optimization, rendering them useless

3) detect when querying is set up (ignoring listeners and maybe other 
stuff that could get broken)

4) remove write-only commands completely (and probably functional 
listeners as well because these will lose their purpose)

Right now I am inclined towards 4). There could be some internal use 
(e.g. multimaps) that could use 1) which is ran without a fancy setup, 
though, but it's asking for trouble.

WDYT?

Radim

-- 

Radim Vansa <rvansa at redhat.com>
JBoss Performance Team



More information about the infinispan-dev mailing list