Open johnjreiser opened 3 years ago
Sorry for the delay responding
DEBUG
statements in the source code: You can turn them on for more details, either directly or by using the "constants" found in the config file: eg "jx_elasticsearch.meta.DEBUG": true,
"$ref": "env://**
are environment variables that are properly set (I think the code complains if not set).
I'm trying to use this tool to take a MySQL backup of our Bugzilla instance and push the details into Elastic. When running bz_etl.py, I receive the following message:
I haven't been able to get the script to produce any other debugging information.
Here's the "settings.json" file used (taken from this repo, with a few modifications.
Ultimately, our specific use case only needs a one-time push and not recurring refreshes, as we moved off of Bugzilla in 2018, but have approximately 13 years of knowledge within, so we'd like to replicate it somewhere in our environment, instead of keeping Bugzilla running, but locked down. I feel like I'm very close to getting this working for this purpose.
Any assistance you can provide on why this seems to immediately stop without other details would be of great help. Thanks!