8000 Remove extended APOC config from core by Lojjs · Pull Request #166 · neo4j/apoc · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Remove extended APOC config from core #166

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

Merged
merged 7 commits into from
Sep 8, 2022
Merged

Conversation

Lojjs
Copy link
Contributor
@Lojjs Lojjs commented Sep 1, 2022

Parts of the APOC config was only used from extended (or in some cases fully unused). This PR removes them from core, while neo4j-contrib/neo4j-apoc-procedures#3157 introduce corresponding config to the extended. repo. It also removes the possibility to have APOC config in the neo4j.conf file

Lojjs added 4 commits August 29, 2022 14:54
These were not used in either core or extended.
This will be added to extended repo instead.
As it is now only used in extended.
As it is now only used in extended.
@@ -46,23 +44,15 @@
import static org.neo4j.configuration.GraphDatabaseSettings.transaction_logs_root_path;

public class ApocConfig extends LifecycleAdapter {
public static final String SUN_JAVA_COMMAND = "sun.java.command";
protected static final String SUN_JAVA_COMMAND = "sun.java.command";
public static final String APOC_IMPORT_FILE_ENABLED = "apoc.import.file.enabled";
public static final String APOC_EXPORT_FILE_ENABLED = "apoc.export.file.enabled";
public static final String APOC_IMPORT_FILE_USE_NEO4J_CONFIG = "apoc.import.file.use_neo4j_config";
public static final String APOC_TTL_SCHEDULE = "apoc.ttl.schedule";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are some TTL configs still in core? I thought all TTL procedures were in extended

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reason I kept this as well as some UUID constant here was because of them being used in the file ApocSettings.java. I also tried out to move those settings to a ExtendedApocSettings file in extended, but then I would have to copy over all the code under // copy apoc settings from neo4j.conf for legacy support in ApocConfig to the ExtendedApocConfig as well if we want to keep the old behaviour.

I'm not sure if this legacy support is really needed in 5.x though as the comment in ApocSettings sounds a bit like that is something to make it easier for people to use the 3.x way in 4.x. If we think we can get rid of it all together, I could move over those constants as well as do further cleanup.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah okay, I think the main thing for me is that it feels strange to have extended settings still in core. It might be nice to see if it is possible to remove the legacy stuff so core can move these out :) maybe ask the team?

Support for apoc config in Neo4j config file will be dropped.
Default values are now handled directly in ApocConfig.java
@Lojjs Lojjs force-pushed the 5.0-remove-extended-config branch from 464e71c to c924bf0 Compare September 6, 2022 14:10
Copy link
Contributor
@gem-neo4j gem-neo4j left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Nice with this all cleaned up 😄

@Lojjs Lojjs merged commit ec8257f into dev Sep 8, 2022
@Lojjs Lojjs deleted the 5.0-remove-extended-config branch September 8, 2022 13:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
619E
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0