Skip to content
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

Update from original #1

Merged
merged 37 commits into from
Jul 4, 2017
Merged

Update from original #1

merged 37 commits into from
Jul 4, 2017

Conversation

stdob
Copy link
Owner

@stdob stdob commented Jul 4, 2017

No description provided.

spacecowboy and others added 30 commits March 23, 2017 10:14
add setting "dbms.directories.import" "/import" neo4j.conf
Configuration from not hardcoded env variables
Copy work in 3.2 to other versions
This fixes a bug where dbms.mode would be set multiple times in the
config. Turns out that this is fine for all values EXCEPT
dbms.mode=ARBITER.

In that case we rely on parsing the config from bash which runs into a
problem due to:
https://github.com/neo4j/neo4j/blob/6cc2ebb93b39405976801f57173079deea45fd11/packaging/standalone/src/main/distribution/shell-scripts/bin/neo4j-shared.m4#L157

If an entry is defined multiple times, it is regarded as a cumulative
option. This is used for JAVA_OPTS and similarly. But for Arbiter we
set a different main class. So having multiple dmbs.mode entries will
set an incorrect value which means the default main class is called,
instead of the Arbiter's.

So this fix makes sure to only replace uncommented values in the
config, and otherwise always append to the end. Previously we would
replace even commented values, but since dmbs.mode is listed twice
in the 3.1/3.2/3.3 config (once in the HA-section, once in CC-section)
it would get set twice.
spacecowboy and others added 7 commits May 18, 2017 13:13
Ensure config only has single entries
Store logs from tests for easier debugging from CI
* For values which had old hardcoded versions we would always override
  the new kind. If the old variable had no value then we wrote that
  empty value.
* Now only sets the values conditionally: if no value for the new kind
  of variable exists, and then only if the previous variable has a
  value. And if not, then we write whatever is the default (or nothing).
Fixed setting config values via environment values
@stdob stdob merged commit 2c5b1e7 into stdob:master Jul 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants