-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
allow logging to be configurable using env variables and tone it down by default #176
Comments
Part 2 due to the character limit of 65536:
|
Right now it is extremely verbose. See <https://docs.liquibase.com/concepts/connections/creating-config-properties.html>. Partly addresses #176.
Right now it is extremely verbose. See <https://docs.liquibase.com/concepts/connections/creating-config-properties.html>. Partly addresses #176.
The corresponding environment variable is |
After more research I I found the liquibase issue has two parts:
|
Liquibase v4.25.0 was released on November 13 and mentions the pull request in the "New Features" section: https://github.com/liquibase/liquibase/releases/tag/v4.25.0 |
The "Running Changeset" messages are now gone after upgrading to Liquibase v4.25.0. |
backend:
image: ghcr.io/onto-med/top-backend:v0.6.9
[...]
environment:
- LIQUIBASE_LOG_LEVEL=WARNING $ docker compose logs backend | grep liquibase
backend-1 | 2023-12-18 09:21:08.932 INFO 1 --- [ main] liquibase.database : Set default schema name to public
backend-1 | 2023-12-18 09:21:08.987 INFO 1 --- [ main] liquibase.lockservice : Successfully acquired change log lock
backend-1 | 2023-12-18 09:21:09.004 INFO 1 --- [ main] liquibase.changelog : Reading resource: db/changelog/changesets/202210170901-init-db.yaml
[...] Even though the env var is set inside the container: $ docker compose exec backend /bin/bash
root@77f229d94447:/usr/src/top-backend# echo $LIQUIBASE_LOG_LEVEL
WARNING |
Strangely, the liquibase INFO messages still occur with backend version v0.7.0-beta-10 where d9bf3f9 is included. |
* for convenience: added google-java-format script * fixed response; removed unused imports * started implementing the functionality to replicate the conceptGraphs returned by concept-graphs-api in the neo4j db with backend methods * continuing; relationships are added. but there are also duplicates and DocumentNodeEntity are not created * added methods to remove and add related nodes from within each NodeEntity as well as methods to convert them to its respective API counterpart * seems like I need to use cypher queries in java to create the network like I want and can't use SDN * update concept caching; fixed some bugs; need to rework the neo4j node creation (probably still with explicit Cypher Queries) * basic neo4j concept cluster creation implemented for the backend. now we need to adapt top-api accordingly * Re-enable OLS related tests Looks like they were accidentally disabled due to merging issues * Fix plugin detection with `reflections` (#186) * update liquibase, helps with #176 (#185) * google-java-format and implemented call to create concept graphs * wrong override? * fixed caching * Threading of concept cluster creation in neo4j per process only; not for each graph. Added logging filter for neo4j except error since massive amounts of warnings of deprecation where thrown that are beyond our control * bump pom version * fixed google format * Remove google java style scripts They should not be included in this repository * Reduce version number We are still in preparation for the v0.7.0 release * review: requested changes * review: requested changes - working on tests * only conceptById test; the other is not feasible * disabled test for neo4j. it works when just running it as a single test but when run with more tests somehow the database is not accessible anymore. need to look into it before enabling. * google format... --------- Co-authored-by: Christoph Beger <[email protected]> Co-authored-by: Konrad Höffner <[email protected]>
Part of Onto-Med/top-deployment#44.
Right now there is a large amount of unnecessary log output:
The text was updated successfully, but these errors were encountered: