WritableManifest has invalid value #10557
Comments
|
Thanks for reaching out @7pandeys ! I wasn't able to replicate this with the following simple example: {{
config(
materialized='incremental'
)
}}
select 1 as idUsing dbt 1.4: dbt build --target-path dbt-artifactsThen change Switch to dbt 1.8: Could you share a simplified example of your relevant model(s) along with your log output so we can try to reproduce what you are seeing? |
|
Example: 1.8 As you can see, I have intention to disable contract in v1.8 version #10298 - it is same case which I am facing now in CI(jenkins). dbt-bigquery version: 1.8.2 |
|
Thanks for providing this @7pandeys, but I still wasn't able to reproduce any errors. Here's what I tried: v1.4{{
config(
materialized='incremental',
)
}}
select 1 as idversion: 2
models:
- name: my_model
config:
contract:
enforced: true
alias_types: false # true by defaultRun these commands: dbt build --target-path dbt-artifactsv1.8{{
config(
materialized='incremental',
on_schema_change='fail',
)
}}
select 2 as idversion: 2
models:
- name: my_model
config:
contract:
enforced: false
alias_types: false # true by defaultRun these commands: dbt build --threads 8 --exclude resource_type:seed resource_type:test --select @state:new @state:modified.body @state:modified.configs @state:modified.macros --state ./dbt-artifacts --vars '{"full_data": false}'Here's the output that I got: Do you get an error if you run these? If not, are you able to tweak them to reproduce the error you are reporting? |
|
is it possible to test for dbt-bigquery ? Jenkins ### Logs dbt build --threads 8 --exclude resource_type:seed resource_type:test --select https://github.com/State:new https://github.com/State:modified.body https://github.com/State:modified.configs https://github.com/State:modified.macros --state ./dbt-artifacts --vars {"full_data": true} |
@7pandeys I changed this example to work with the dbt-bigquery adapter, and it did reproduce the error you saw. See below for details. v1.4
select 1 as dummy
{{
config(
materialized='incremental',
unique_key='id',
)
}}
select 1 as id, 1 as my_number
from {{ ref("dual") }}
version: 2
models:
- name: my_model
config:
contract:
enforced: true
alias_types: false # true by defaultRun these commands: dbt build --target-path dbt-artifactsv1.8
{{
config(
materialized='incremental',
unique_key='id',
on_schema_change='fail',
)
}}
select 2 as id, 2 as my_number
from {{ ref("dual") }}
version: 2
models:
- name: my_model
config:
contract:
enforced: false
alias_types: false # true by defaultRun these commands: dbt build --threads 8 --exclude resource_type:seed resource_type:test --select @state:new @state:modified.body @state:modified.configs @state:modified.macros --state ./dbt-artifacts --vars '{"full_data": false}'Here's the output that I got: |
|
@7pandeys I don't know all the details leading to this error message, but it looks to me that a big reason is that dbt model contracts weren't introduced until dbt v1.5. So I'd suggest removing all the contract-related config when you are running dbt v1.4 and reproduce your Since model contracts weren't introduced until v1.4 and there's a path forward for you to resolve this, I'm going to close this as "not planned". |
dbeatty10
added
wontfix
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a new bug in dbt-core?
Current Behavior
WritableManifest has invalid value when upgrading dbt version from 1.4 to 1.8
Expected Behavior
manifest.json should get created
Steps To Reproduce
dbt build --threads 8 --exclude resource_type:seed resource_type:test --select @state:new @state:modified.body @state:modified.configs @state:modified.macros --state ./dbt-artifacts --vars {"full_data": false}Relevant log output
No response
Environment
Which database adapter are you using with dbt?
bigquery
Additional Context
No response
Tasks
The text was updated successfully, but these errors were encountered: