mona-loading Recently we have received many complaints from users about site-wide blocking of their own and blocking of their own activities please go to the settings off state, please visit： https://githubmemory.com/settings/account ，20 minutes to take effect。
llarbodiere

llarbodiere

Member Since 1 year ago

Experience Points
0
follower
Lessons Completed
0
follow
Lessons Completed
3
stars
Best Reply Awards
0
repos

6 contributions in the last year

Pinned
Activity
Apr
12
1 month ago
Activity icon
issue

llarbodiere issue comment dbt-labs/dbt-core

llarbodiere
llarbodiere
llarbodiere
llarbodiere CONTRIBUTOR
createdAt 1 month ago
  • enhancement

    • Future art for exposures

    Describe the feature

    What other properties should exposures get?

    • tags
    • meta
      • we do want some traditional meta fields (e.g. owner) to be required or top-level
      • still could be nice as a catch-all for structured key-value properties users would want to define, beyond what'd be available via tags or description
    • new type options:
      • "reverse pipeline", e.g. a census sync
      • users supplying their own string types
    • new maturity options
      • higher than high? "mission-critical"
      • ...

    Should exposures be ref-able?

    • exposures that depend on other exposures: one exposure for each Mode query / Looker view, one exposure for the dashboard that depends on those queries / views
    • models that depend on exposures: modeled input to data science --> data science as exposure --> modeled output
      • what exactly would ref('my_exposure') return?

    Describe alternatives you've considered

    We're likely to keep these bare-bones for a little while. I'm still curious to hear what community members want!

    Who will this benefit?

    Users of the exposures resource type, which is new in v0.18.1

    llarbodiere
    llarbodiere
    llarbodiere
    llarbodiere
    comment in 1 month ago

    Additional use case at Ludia/JamCity: We have 2 data stacks with inter-depencies. Some of our models are used downstream by tables and dashboards/reports.

    We would like to define those downstream tables as exposure or external tables to reflect it in our DAG. But also have the possibility to put exposures (tableau dashboards) depending on other exposures (the downstream tables) so we can rebuild the DAG for the most important reports.

    Thanks a lot, Lucas

    Mar
    30
    1 month ago
    Activity icon
    issue

    llarbodiere issue dbt-labs/dbt-docs

    llarbodiere
    llarbodiere
    llarbodiere
    llarbodiere NONE
    createdAt 1 month ago
  • enhancement

    • [DAG] Find model in the dag as in the 'LIKE' sql function ('%my_model%')

    Describe the feature

    We have a LOOOT of model with different sources. A cool feature in the DAG under the --select category, would be to allow using the % operator in the same way of the LIKE function. It would allow to not know by hearth the name of each model and be able to find it really fast.

    Describe alternatives you've considered

    Having a correct naming convention? (lol)

    Additional context

    Not really

    Who will this benefit?

    All dbt cloud dag user

    Are you interested in contributing this feature?

    Sure ! Let me know how I can help

    Mar
    21
    2 months ago
    Activity icon
    issue

    llarbodiere issue dbt-labs/docs.getdbt.com

    llarbodiere
    llarbodiere
    llarbodiere
    llarbodiere NONE
    createdAt 2 months ago
  • content
  • improvement

    • [Feature] DAG: different color for the model, test and sources failing

    Contributions

    • I have read the contribution docs, and understand what's expected of me.

    Link to the page on docs.getdbt.com requiring updates

    https://docs.getdbt.com/docs/building-a-dbt-project/documentation

    What part(s) of the page would you like to see updated?

    Hello,

    It would be amazing to be able to see errors directly in the dag:

    • Sources: display a different color than green if the freshness test does not pass
    • Model runs: display a different color than blue if it fails (suggestion: red)
    • Model tests: display a different color than blue if test is failing (maybe light orange) or warning (light yellow)

    In order to reduce noise, it would also be great having a Yes/No selector on that to be able to either enable or disable this feature.

    Additional information

    If you need help to build it I would love to give an hand. I'm not a software engineer but a motivated analytics engineer :D .

    Activity icon
    issue

    llarbodiere issue comment dbt-labs/dbt-core

    llarbodiere
    llarbodiere
    llarbodiere
    llarbodiere NONE
    createdAt 2 months ago
  • enhancement

    • [CT-367] [Feature] DAG: different color for the model, test and sources failing

    Is there an existing feature request for this?

    • I have searched the existing issues

    Describe the Feature

    Hello,

    It would be amazing to be able to see errors directly in the dag:

    • Sources: display a different color than green if it is not fresh
    • Model runs: display a different color than blue if it fails (suggestion: red)
    • Model tests: display a different color than blue if test is failing (maybe light orange) or warning (light yellow)

    In order to reduce noise, it would be great to have a Yes/No selector on that to be able to either enable or disable this feature.

    Describe alternatives you've considered

    Building a dag with the api

    Who will this benefit?

    Data observability so everyone ! I find it a bit time consuming to look at a test failing and looking for the corresponding test.

    Are you interested in contributing this feature?

    YEEEEES ! I'm not a software engineer though

    Anything else?

    Love for the product <3

    llarbodiere
    llarbodiere
    llarbodiere
    llarbodiere
    comment in 2 months ago

    Hello @jtcohen6 !

    Thanks for the response. I will recreate the issue on the dbt-docs github. I would also love to help you work on this.

    Lucas

    Mar
    16
    2 months ago
    Activity icon
    issue

    llarbodiere issue dbt-labs/dbt-core

    llarbodiere
    llarbodiere
    llarbodiere
    llarbodiere NONE
    createdAt 2 months ago
  • enhancement
  • triage

    • [Feature] DAG: different color for the model, test and sources failing

    Is there an existing feature request for this?

    • I have searched the existing issues

    Describe the Feature

    Hello,

    It would be amazing to be able to see errors directly in the dag:

    • Sources: display a different color than green if it is not fresh
    • Model runs: display a different color than blue if it fails (suggestion: red)
    • Model tests: display a different color than blue if test is failing (maybe light orange) or warning (light yellow)

    In order to reduce noise, it would be great to have a Yes/No selector on that to be able to either enable or disable this feature.

    Describe alternatives you've considered

    Building a dag with the api

    Who will this benefit?

    Data observability so everyone ! I find it a bit time consuming to look at a test failing and looking for the corresponding test.

    Are you interested in contributing this feature?

    YEEEEES ! I'm not a software engineer though

    Anything else?

    Love for the product <3

    Feb
    23
    3 months ago
    started
    llarbodiere

    llarbodiere started re-data/re-data

    started time in 2 months ago
    ucloud ads