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

Deriving an aggregated dataset #408

Open
arvind opened this issue Sep 27, 2016 · 0 comments
Open

Deriving an aggregated dataset #408

arvind opened this issue Sep 27, 2016 · 0 comments
Labels

Comments

@arvind
Copy link
Member

arvind commented Sep 27, 2016

When a mark property is bound to aggregated data, we currently produce a new dataset if a new groupby field is introduced or amend an existing dataset for new summary fields. However, if additional transforms (e.g., filter, formula) are added to an aggregated dataset, the above logic will fail to transfer the transforms over.

A naive approach to copying transforms over, however, will fail because the schemas of the two datasets may not be equivalent. Consider this flow:

  1. User binds groupby fields A & B and a summary field C.
  2. User adds a filter transformation using B.
  3. User unbinds B from the mark.
  4. User binds groupby field D.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants