Hm, this is not a public API, but you should theoretically be able to use
TestBlockId if you like. Internally, we just use the BlockId's natural
hashing and equality to do lookups and puts, so it should work fine.
However, since it is in no way public API, it may change even in
maintenance releases.
On Sun, Jul 20, 2014 at 10:25 PM, william <k...@qq.com> wrote:
> When spark is 0.7.3, I use SparkEnv.get.blockManager.getLocal("model") and
> SparkEnv.get.blockManager.put("model", buf, StorageLevel.MEMORY_ONLY,
> false) to cached model object
>
> When I porting to spark 1.0.1, I found SparkEnv.get.blockManager.getLocal
> & SparkEnv.get.blockManager.put's APIs changed to use BlockId instead of
> String.
>
> And BlockId has 5 concrete class, which one should I use? None of them
> have a string input parameter.
>
> Thx
>
