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

Make the prediction on cube measures for integer values #39

Open
evshvarov opened this issue Dec 12, 2019 · 1 comment
Open

Make the prediction on cube measures for integer values #39

evshvarov opened this issue Dec 12, 2019 · 1 comment
Milestone

Comments

@evshvarov
Copy link
Contributor

Coul you autodetect for the measures upon the values? e.g. it's a measure if first 10 values are integers
Would be great

@psteiwer psteiwer added this to the v2.0 milestone Mar 8, 2021
@psteiwer
Copy link
Owner

psteiwer commented Mar 8, 2021

We had this initially but removed it because it was doing things like turning medical codes and zip codes into measures, which is not desired. If we auto detect something, we do not want users to need to switch it back to the "default" option of dimension, when they may not yet understand what are measures and what are dimensions. It is slightly easier to understand what is happening if the values default to dimensions when they should be measures vs defaulting to measure when they should be dimensions. A measure can still be useful as a dimension, but a dimension is rarely useful as a measure.

It would certainly be nice to add this back in, but we would want to do it in a way where defaulting to dimension is the safe choice and auto detecting a numeric value that is actually a measure is the advanced logic.

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

No branches or pull requests

2 participants