-
Notifications
You must be signed in to change notification settings - Fork 29
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
Make use of new database setting for determining conf directory #719
Conversation
74a0ae5
to
4856577
Compare
} | ||
return neo4jConfFolder; | ||
} | ||
return neo4jConfig.get(configuration_directory).toString(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't comment directly on the correct line, but where this is used now has an incorrect comment, can you fix that up? :) also the log info is wrong now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could the log say something like this?
return neo4jConfig.get(configuration_directory).toString(); | |
String neo4jConfFolder = neo4jConfig.get(configuration_directory).toString(); | |
log.info("from database setting: server.directories.configuration=%s", neo4jConfFolder); | |
return neo4jConfFolder; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm actually, that line is about setting a system property. Do we even need that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we need the loging any more. Omitting it and updating the comment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Super
Makes use of the new setting introduced in PR. This allows for the removal of the previously hacky way of determining the conf directory. Removes associated tests and updates tests that previously depended on the hack.