Skip to content

Frequently Asked Questions

1. How do I install this?

A: dataopsly provides a beautiful opportunity for the data enthusiasts to run the tool either on their own servers or on our managed services(postgres/snowflake), or through snowflake container services. Kindly choose the respective criteria and transform your data(s)!

1. What should I name my profile?

A: We typically use a company name for a profile name, and then use targets to differentiate between dev and prod. Check out the docs on Warehouses for more information.

2. What should I name my target?

A: We typically use targets to differentiate between development and production runs of dbt, naming the targets dev and prod, respectively. Check out the docs on warehouses for more information.

1. Add a seed file

A: - Add a seed file: seeds/country_codes.csv

    country_code,country_name
    US,United States
    CA,Canada
    GB,United Kingdom
    ...

  • Run dbt seed

  • Ref the model in a downstream model [models/something.sql] 

    select * from {{ ref('country_codes') }}

2. How do I exclude a table from a freshness snapshot?

A: Some tables in a data source may be updated infrequently. If you've set a freshness property at the source level, this table 1 is likely to fail checks. To work around this, you can set the table's freshness to null (freshness: null) to "unset" the freshness for a particular table:

models/{filename}.yml

    version: 2

    sources:
    - name: jaffle_shop
    database: raw

    freshness:
    warn_after: {count: 12, period: hour}
    error_after: {count: 24, period: hour}

    loaded_at_field: _etl_loaded_at

    tables:
    - name: orders
    - name: product_skus
            freshness: null # do not check freshness for this table
1. How to use the scheduling of jobs?

A: There are two schedules and one no schedule event provided as of now in the jobs area. The interval schedule is where you can define for every hour/minute/day with respect to the day and time, and enabled will make the job schedule, and disabling it, will unschedule the job. The cron schedular is where you define based on recurring intervals, specified using a format based on unix-cron, for more details refer documentation.

1. Where do I find my login credentials?

A: This is for those who are running on their own servers, the passwords for the database credentials and login credentials are found in the password.txt file in the .data folder.

1. Do I need to add a YAML entry for column for it to appear in the docs site?

A: Fortunately, no!

this tool will introspect your warehouse to generate a list of columns in each relation, and match it with the list of columns in your .yml files. As such, any undocumented columns will still appear in your documentation!

2. Can I document things other than models, like sources, seeds, and snapshots?

A: Yes! You can document almost everything in your project using the 'description:' key.

3. How do I share my documentation with my team members?

A: We are working on that, keep in touch will let you all know, once it is updated. As of now, we have made up permissions area, where a particular user can be allocated for the viewability of the docs.

1. How do I give permissions for the users apart from the default groups?

A: Only admins have the authority and permission to create or grant permissions to users.

Query Form



 



  1. In simplest terms, a table is the direct storage of data in rows and columns. Think excel sheet with raw values in each of the cells. ↩