Using Polaris and Classic

BrentOrr

Client has spoke models built in Classic and now considering building Data Hub in Polaris in order to deal with sparsity. On the surface this seem possible but likely a bad idea. Has anyone done anything similar to this? Specifically, what did you have to do to ensure that data was compatible? Any thoughts or suggestions would be appreciated.

lgrady

I haven't done this but agree it's likely a bad idea to have a polaris data hub and classic spokes. (the other way around where your data hub is on classic but your spokes are on polaris i do have some experience with and it's joyous though!)

Is the idea to make one big cube in the data hub and load sparse data into it? If you have a lot of dimensions of any size you're probably going to hit the limit of 2^64 intersections or index calc (https://community.anaplan.com/discussion/156784/dimension-index-calculator-model)

But even if you don't hit that (and don't anticipate lists growing to the point it would ever hit) then in order to get that sparse data down to a classic spoke model you'd probably have to create a unique key that concatenates codes for all intersections create a list in your classic engine spoke models anyway. I'm not seeing much lift in loading data into a sparse cube, having anaplan flatten it and then loading into classic. i'd bet there are data tools upstream that can flatten the data as well as or better than anaplan could.