-
Notifications
You must be signed in to change notification settings - Fork 493
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
apoc extended on 5.2 throws errors for missing config values #3358
Comments
@jexp - We got this exact problem and have been trying the whole week to figure this out. Still no luck to bypass the error How do we get pass this for now? We can get the cluster up and running but the error messages are misleading 👍 Note: also occurs for the config |
@conker84 this should hopefully address it.
|
Had to set both these values to avoid errors on startup:
|
@cramatt Where do I set these values? neo4j.conf? I see in your other post #3359, you have it in a separate apoc.conf file. Are you able to get any apoc functions working? I have a similar docker setup. When I run I get the error
|
@RedFour yes I have two config files in the config directory: neo4j.conf I think this might be a change in 5.x where there are 2 different files. In the past I recall configuring things in a single files. I'm also not sure in the docs where I discovered this. Also I did notice apoc.version() is NOT in both core and extended... I guess to the thread #3359 this is only in core. I'm wondering if they should consider namespacing Core vs. Extended functions to clear some of this up. |
I was able to get it running via docker following this
Notice I'm just loading APOC Core in my docker-compose file. The docs suggest you DON'T need to download this but I found it only worked if I did download and map to volume like shown above. |
Thanks, I'm able to get my apocs to work with your apoc core link in the other thread. |
…ing config values
In reply to this comment in #3358 (comment):
In fact, the doc is incomplete, but based on your findings, I tried installing automatically the core plugin with the following env var and it works: |
we should probably not throw on non-existing for getBoolean in commons-config but give it a default value of false
The text was updated successfully, but these errors were encountered: