Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LogicLayer "matches multiple levels in this dimension" #305

Open
palamago opened this issue Feb 8, 2021 · 1 comment
Open

LogicLayer "matches multiple levels in this dimension" #305

palamago opened this issue Feb 8, 2021 · 1 comment

Comments

@palamago
Copy link

palamago commented Feb 8, 2021

In a LogicLayer's query like: data?Year=2020&Generic+Career=66,81,77,12,247,194,109,6,63,105&Institution=3,45,71,10,2,85,89&Preference+Status=24&cube=demre_applications&drilldowns=Institution,Generic+Career,Year&measures=Last%20Enrolled%20Score&parents=false&sparse=false

Tesseract returns 404with a message:
"3 matches multiple levels in this dimension." being 3 the id set in the cut param.

It means that this id 3 is present as a key in more than one members across all members and dimensions.

Is this behavior correct?
Why do we require to have different ids on differents levels inside same dimension?
Why is not enough to have unique ids per level?

@frabarz
Copy link
Contributor

frabarz commented Feb 8, 2021

It sounds like it's trying to parse the 3 as a cut level instead of a member id. We should check the debug logs to solve this.
Set the env var TESSERACT_DEBUG to true and look for a line with the content Aggregate query: LogicLayerQueryOpt { cube: ... }, that should contain what tesseract understood as the query.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants