Does Bulk Update affect cardinality statistics of GemfireXD tables ?
According to Derby's website normal operation can cause cardinality statistics to go stale/out-of-date which can cause less-then-optimal query planing. As such, Derby offers two system procs
Does GemfireXD have the same issue of stale cardinality statistics, say after a bulk upload to a table with pre-defined index. Does GemfireXD have comparable tools or is this not an issue in GemfireXD?
Please sign in to leave a comment.