Troubleshooting Databricks collector issues
Collector runtime and troubleshooting
The catalog collector may run in several seconds to many minutes depending on the size and complexity of the system being crawled.
If the catalog collector runs without issues, you should see no output on the terminal, but a new file that matching *.dwec.ttl should be in the directory you specified for the output.
If there was an issue connecting or running the catalog collector, there will be either a stack trace or a *.log file. Both of those can be sent to support to investigate if the errors are not clear.
A list of common issues and problems encountered when running the collectors is available here.
Issue 1: Not all desired tables displayed after the collector run is complete
Cause: The parameters all-schemas or schema is missing from the Command line or YAML file.
Solution: Check your command or YAML file to make sure the all-schemas or schema parameter is setup properly.