where Location is the DimensionUsage, location is the shared dimension, and Jowf is a member of level Region.
This leads to 3 major issues:
It's a little strange to have the shared dim as part of the name.
Properties currently have a check which prevents names from being over 3 segments long, and including the shared dim name would violate this (as would just having a hierarchy name, actually). See https://github.com/jazzido/mondrian-rest/blob/public/lib/mondrian_rest/api_helpers.rb#L90 and see specific issue #26. Properties actually work with the less-qualified name (without the shared dim) but this creates an inconsistency in naming schemes.
When referencing the DimensionUsage in a Named Set in the schema, the fully qualified name with shared dim was required, otherwise I received a dreaded #<NoMethodError: undefined methodgetName' for nil:NilClass>when hitting the/cubes` route.
(Side note, for queries, both with and without shared dim in name appear to work)
As mentioned before, I think having shared dim in the name is weird but it's ok as long as it works and is consistent. But removing the need for it would be fine too.
Shared dims are showing up as part of the fully qualified name, e.g.
where
Location
is the DimensionUsage,location
is the shared dimension, andJowf
is a member of levelRegion
.This leads to 3 major issues:
#<NoMethodError: undefined method
getName' for nil:NilClass>when hitting the
/cubes` route.(Side note, for queries, both with and without shared dim in name appear to work)
As mentioned before, I think having shared dim in the name is weird but it's ok as long as it works and is consistent. But removing the need for it would be fine too.
Thanks!