Error when validating a package with primary/foreign key relations #623

sapetti9 · 2021-03-16T13:48:49Z

sapetti9
Mar 16, 2021
Maintainer

I'm having some trouble validating a package with primary/foreign key relations - I get the following:

{
    "version": "4.1.0",
    "time": 0.036,
    "errors": [
        {
            "code": "task-error",
            "name": "Task Error",
            "tags": [],
            "note": "'str' object has no attribute 'keys'",
            "message": "The task has an error: 'str' object has no attribute 'keys'",
            "description": "General task-level error."
        }
    ],
    "tasks": [],
    "stats": {
        "errors": 1,
        "tasks": 0
    },
    "valid": false
}

Primary keys and foreign keys seem to be defined ok and I'm at a loss to know what this error means.

The package follows a basic star schema and if I remove the FK relations on the main data table resource the package validates fine. I've copied the FK definition which appears at the end of the table resource (I've tried the fields both with and without an array - the documentation is a bit confusing, but the result re the error is the same):

"foreignKeys": [
          {
            "fields": [
              "crop_type"
            ],
            "reference": {
              "resource": "crop_types_data",
              "fields": [
                "crop_name"
              ]
            }
          },
          {
            "fields": [
              "liming_factor_level"
            ],
            "reference": {
              "resource": "liming_factor_data",
              "fields": [
                "factor_level_name"
              ]
            }
          },
          {
            "fields": [
              "p_factor_level"
            ],
            "reference": {
              "resource": "p_factor_data",
              "fields": [
                "factor_level_name"
              ]
            }
          },
          {
            "fields": [
              "k_factor_level"
            ],
            "reference": {
              "resource": "k_factor_data",
              "fields": [
                "factor_level_name"
              ]
            }
          }
        ]

Any idea why this is happening?