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

Data Modeling: Datasets #18659

Closed
29 of 32 tasks
dpsutton opened this issue Oct 25, 2021 · 4 comments
Closed
29 of 32 tasks

Data Modeling: Datasets #18659

dpsutton opened this issue Oct 25, 2021 · 4 comments
Labels
.Epic Feature Implementation or Project Querying/Models aka Datasets
Milestone

Comments

@dpsutton
Copy link
Contributor

dpsutton commented Oct 25, 2021

Data Modeling: Datasets

Ability to used saved datasets as the source of a query. Initial deliverable is to use the saved-questions functionality and create a UX that promotes and eases their use.

Links

Milestone 1

Backend

Frontend

Milestone 2

Frontend

Backend

Milestone 3

Frontend

Backend

Misc / Polish

  • Fix revision history messages when a question is turned into a dataset and vice-versa (Add revision messages for datasets #18875)
  • Display datasets correctly in recent searches (Display datasets in recent searches and on activity page #18987)
  • Data selector: skip raw data step when there is only one database when navigating back from a selected table
  • Data selector: when opening the selector with a dataset selected, "Saved Questions" opens instead of "Datasets"
  • Show if a dataset is in an official collection (maybe also show if a question is based on an official dataset)
  • Disallow creating datasets based on native questions using variables
  • Add a warning icon to questions built on archived datasets
  • List datasets together with questions when adding things to dashboards
  • Cleanup data selector UI (comments from Maz)
  • Verify dataset UI
  • Handle databases without nested queries support
  • Should be possible to pick a Dataset as a target when configuring click behavior on a dashboard card (Slack converation)
@dpsutton dpsutton added .Epic Feature Implementation or Project Querying/Models aka Datasets labels Oct 25, 2021
@rlotun rlotun added this to the 0.42 milestone Nov 2, 2021
@rcronin
Copy link

rcronin commented Jan 15, 2022

I noticed that the datasets essentially turn the underlying query into a subselect when adding filters, joins, etc. to it. How is it going to be handled when the query for a dataset needs to be filtered from a variable? Specific scenario would be when the base of a dataset is a native sql question and there's a variable for a date filter?

@flamber
Copy link
Contributor

flamber commented Jan 16, 2022

@rcronin It's currently not supported to pass-thru variables: #6449

@rcronin
Copy link

rcronin commented Jan 16, 2022

@rcronin It's currently not supported to pass-thru variables: #6449

Will it be supported at some point? This would be extremely valuable feature and seems to be noted that way in the issue referenced.

@flamber
Copy link
Contributor

flamber commented Jan 16, 2022

@rcronin I cannot tell you if or when, but upvote the issue by clicking 👍 on the first post. And follow the roadmap: https://www.metabase.com/roadmap/

@kulyk kulyk closed this as completed Jan 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
.Epic Feature Implementation or Project Querying/Models aka Datasets
Projects
None yet
Development

No branches or pull requests

5 participants