-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[CT-3485] Semantic Layer custom calendar config support #9265
Labels
Impact: CA
Impact: SL
Refinement
Maintainer input needed
semantic
Issues related to the semantic layer
user docs
[docs.getdbt.com] Needs better documentation
Milestone
Comments
github-actions
bot
changed the title
Semantic Layer custom calendar config support
[CT-3485] Semantic Layer custom calendar config support
Dec 9, 2023
QMalcolm
added
Refinement
Maintainer input needed
Impact: CA
Impact: SL
user docs
[docs.getdbt.com] Needs better documentation
semantic
Issues related to the semantic layer
labels
Dec 9, 2023
Just to add some color on use case for this - could be super useful for companies/departments that rely heavily on a fiscal calendar ...which is typically available as table(s)/view(s) within the data warehouse |
5 tasks
Opened a new issue in dbt-labs/docs.getdbt.com: dbt-labs/docs.getdbt.com#6075 |
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Impact: CA
Impact: SL
Refinement
Maintainer input needed
semantic
Issues related to the semantic layer
user docs
[docs.getdbt.com] Needs better documentation
Housekeeping
Short description
Details unknown.
The spec for this is still in the ideation phase.
Acceptance criteria
People can specify the attributes necessary for custom calendar support 👀
Impact to Other Teams
Will backports be required?
Not sure if required, but the SL team would prefer a backport to 1.7
Context
This issue should not be considered ready to work on until the work is done in dbt-semantic-interfaces, because the schema we need to implement isn't finalized until that point. Currently there does exist an issue for this work in dbt-semantic-interfaces.
The text was updated successfully, but these errors were encountered: