```meltano | Loading failed (2): CRITICAL ['Traceb...
# plugins-general
j
Copy code
meltano | Loading failed (2): CRITICAL ['Traceback (most recent call last):\n', ' File "/projects/default/.meltano/loaders/target-bigquery/venv/lib/python3.6/site-packages/target_bigquery/__init__.py", line 93, in main\n for state in state_iterator:\n', ' File "/projects/default/.meltano/loaders/target-bigquery/venv/lib/python3.6/site-packages/target_bigquery/process.py", line 40, in process\n for s in handler.handle_record_message(msg):\n', ' File "/projects/default/.meltano/loaders/target-bigquery/venv/lib/python3.6/site-packages/target_bigquery/processhandler.py", line 110, in handle_record_message\n new_rec = filter_by_schema(schema, msg.record)\n', ' File "/projects/default/.meltano/loaders/target-bigquery/venv/lib/python3.6/site-packages/target_bigquery/schema.py", line 75, in filter\n record[key]) # adswerve fix to match schema field name\n', ' File "/projects/default/.meltano/loaders/target-bigquery/venv/lib/python3.6/site-packages/target_bigquery/schema.py", line 84, in filter\n prop_type, _ = get_type(props)\n', ' File "/projects/default/.meltano/loaders/target-bigquery/venv/lib/python3.6/site-packages/target_bigquery/schema.py", line 23, in get_type\n f"\'type\' or \'anyOf\' are required fields in property: {property}"\n', "ValueError: 'type' or 'anyOf' are required fields in property: {}\n"]
meltano | ELT could not be completed: Tap and target failed
d
@jason_waldrip Looks like the tap isn't reporting a type for at least one property! What tap are you using? If you run again in debugging mode (https://meltano.com/docs/command-line-interface.html#debugging), you should see the
SCHEMA
message for the offending stream printed with a
tap-foo (out)
prefix just ahead of the error.
Another user ran into the same issue with tap-shopify earlier this week: https://meltano.slack.com/archives/C013EKWA2Q1/p1608041411245100
j
Well this is from tap-postgres, and it seems to be when loading data into big query, we have a ton of enum and custom data types and I wonder if that could be the underlying issue.
d
Ah, could be, although I'd expect tap-postgres to handle that better. Let's see if the offending property is indeed enum/custom using debugging mode 🙂