Looking at a staging environment issue with Shi Lu, we realized that when
upgrading helix from 0.5.x to 0.6.1.2 the property store had moved from
PROPERTYSTORE node to HELIX_PROPERTYSTORE.

This causes our cluster to fail to find properties written before the
upgrade.

Talking to Kishore, we discussed that it would also be a problem for their
project and that we should provide a way to make the upgrade transparently.

One possibility that came up is to make the property store location
configurable some how so that when upgrading the version it can be
configured to continue using the old location.

What do you think?

Cheers,
Santiago

Reply via email to