I think we should change the default back to PROPERTY_STORE. The only thing we changed were the api not the actual data represented in ZK. Dont see much value in adding configurable name space.
thanks, Kishore G On Fri, May 31, 2013 at 1:03 PM, Zhen Zhang <[email protected]> wrote: > yes. we can add a namespace parameter to the interface: > > ZkHelixPropertyStore<ZNRecord> getHelixPropertyStore(String namespace); // > namespace is path relative to the cluster root location > > created a jira to track this: > > https://issues.apache.org/jira/browse/HELIX-118 > > Thanks, > > Jason > > > > > On Fri, May 31, 2013 at 12:44 PM, Santiago Perez <[email protected]>wrote: > >> 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 >>
