Why does the gfsh> Configure Pdx command automatically revert the setting of
“persistence” to false?
Is this by design or a bug?
I have pdf defined as persistent in cluster.xml.
<pdx read-serialized="true" persistent="true">
<pdx-serializer>
Later, when executing scripts that include configure pdf, it turns off my
persistence. I realize that configure pdx does not support —persistence=true
but why turn it off?
gfsh>configure pdx --read-serialized=true
--portable-auto-serializable-classes="com.company.domain.*"
The command would only take effect on new data members joining the distributed
system. It won't affect the existing data members
persistent = false
read-serialized = true
ignore-unread-fields = false
PDX Serializer com.gemstone.gemfire.pdx.ReflectionBasedAutoSerializer
Portable classes [com.company.domain.*]
