-
Notifications
You must be signed in to change notification settings - Fork 17
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
apply_dimension: Clarification of behaviour #357
Comments
good point, you can not just "drop" a dimension without describing how the values along that dimension are "reduced" |
Yes, I think this was meant to say something like that:
So this is essentially: Move the data from source to target after processing it, but target must basically be empty / have a single label only. |
Just wondering: what is the use case that makes this "target_dimension" feature in |
I think the initial use-case was to "convert" data, e.g. you go in with a e.g. temporal dimension and your result is non-termporal data. So you'd need to specify another dimension that could hold the data. I think that is still valid. As far as I know, apply_dimension was spec'ed before drop and rename were defined so the alternative was not present. |
Process ID: apply_dimension
Describe the issue:
Documentation states:
We don't understand how this is supposed to work.
For example what would the result be in the following case:
The text was updated successfully, but these errors were encountered: