Extract the distribution tar.gz file created on the previous step and run the following command
cd open-metadata-<version>sh bootstrap/openmetadata-ops.sh drop-create
Why Needed: The script simplifies the setup and execution of OpenMetadata by handling Java dependencies, configurations, and environment variables automatically.
Note To understand more about openmetadata-ops.sh file click here
Add a new Run/Debug configuration like the below screenshot.
Click on Intellij - Run menu
Click on “Edit Configurations”
Click + sign and Select Application and make sure your config looks similar to the below image
Note that if you want to test the connectors (Ingestion) while having the server running locally and the ingestion
running as a container, you will need to ensure that both components can properly talk to each other. To do so,
pass the following environment variable to IntelliJ when starting the server:
Right-click on openmetadata-serviceClick on “Open Module Settings”Go to “Dependencies”Click “+” at the bottom of the dialog box and click “Add”Click on LibraryIn that list look for “jersey-client:2.25.1”Select it and click “OK”.We also need to set the folder ‘generated-resources’ in some module’s target folder as “source” folder. IntelliJ IDEA mark target folder as “excluded” by default, we could change it in the module setting. The openmetadata-spec and openmetadata-java-client modules have generated code, need to be changed.Now run/debug the application.
If you see a blank page at http://localhost:8585, check the logs at logs/openmetadata.log. You might be encountering one of the following errors:
connection refused or unreachable - please confirm that MySQL and ES are reachable outside of docker by running docker ps and checking that ports 3306 and 9200 are listening on 0.0.0.0
If ElasticSearch in Docker on Mac is crashing, try changing Preferences -> Resources -> Memory to 4GB
If ElasticSearch logs show high disk watermark [90%] exceeded, try changing Preferences -> Resources -> Disk Image Size to at least 16GB
Public Key Retrieval is not allowed - verify that the JDBC connect URL in conf/openmetadata.yaml is configured with the parameter allowPublicKeyRetrieval=true
Browser console shows javascript errors, try doing a clean build. Some npm packages may not have been built properly.