Troubleshooting JSON File Ingestion Error in DataHub UI

ingestion
1

Original Slack Thread

<@U06TM7M40RK> How to resolve below error while ingesting a json file from datahub UI.

Failed to configure the source (json-schema): 2 validation errors for JsonSchemaSourceConfig
path
  Expecting value: line 1 column 1 (char 0) (type=value_error.jsondecode;```
2

I’m not able to find any data sources to answer your question. Could you provide more details about the JSON schema and the configuration you are using? If this doesn’t help, please reach out to the DataHub support team for further assistance. :+1: 0 button :-1: 0 button :bulb: Hint: Mention @runllm in the thread for followups.

3

Hey there! :wave: Make sure your message includes the following information if relevant, so we can help more effectively!

  1. Are you using UI or CLI for ingestion?
  2. Which DataHub version are you using? (e.g. 0.12.0)
  3. What data source(s) are you integrating with DataHub? (e.g. BigQuery)

<@U06TM7M40RK> Can you help with the questions in this thread?

:information_source: We’re experimenting with a new AI assistant for questions in the <#CUMUWQU66> channel to help you track down helpful resources more quickly. Keep in mind that responses may not always be spot-on; feel free to ask it follow-up questions and don’t forget to provide its responses a :thumbsup: or :thumbsdown: so other folks in the Community know if you’re still looking for help on the topic!

4

To help you more effectively, could you please provide the following information?

  1. Are you using the UI or CLI for ingestion?
  2. Which DataHub version are you using? (e.g., 0.12.0)?
  3. What data source(s) are you integrating with DataHub? (e.g., BigQuery)?

Based on the error message you provided, it seems like there might be an issue with the JSON file or the URL you are trying to ingest. The error Expecting value: line 1 column 1 (char 0) typically indicates that the JSON decoder is encountering an empty response or an invalid JSON format.

Here are a few steps you can take to troubleshoot this issue:

  1. Verify the URL: Ensure that the URL <https://gofile.io/d/gvUTo9> is accessible and returns a valid JSON file. You can try opening the URL in a browser or using a tool like curl to check the response.

  2. Check JSON Format: Make sure that the JSON file at the URL is correctly formatted. You can use online JSON validators to check the syntax.

  3. Run with Debug Mode: As suggested in the error message, run the ingestion process with the --debug flag to get the full stack trace. This can provide more detailed information about where the error is occurring.

  4. Localize the JSON File: If the URL is not accessible or the JSON file is too large, consider downloading the JSON file locally and providing the local path for ingestion.

If you provide the additional information requested, I can give you more specific guidance.

Sources:

  • <Slack Slack Thread>
  • <Slack Slack Thread> :+1: 0 button :-1: 0 button :bulb: Hint: Mention @runllm in the thread for followups.