Hi Uma, > If there are still plans to make changes that affect compatibility (the > hybrid RPC and bulk DN work mentioned sound like they would), then we can > cut branch-3 first, or wait to merge until after these tasks are finished. > [Uma] We don’t see that 2 items as high priority for the feature. Users > would be able to use the feature with current code base and API. So, we > would consider them after branch-3 only. That should be perfectly fine IMO. > The current API is very much useful for Hbase scenario. In Hbase case, they > will rename files under to different policy directory. They will not set > the policies always. So, when rename files under to different policy > directory, they can simply call satisfyStoragePolicy, they don’t need any > hybrid API. >
Great to hear. It'd be nice to define which usecases are met by the current version of SPS, and which will be handled after the merge. A bit more detail in the design doc on how HBase would use this feature would also be helpful. Is there an HBase JIRA already? I also spent some more time with the design doc and posted a few questions on the JIRA. Best, Andrew
