graphfoundation / ongdb

ONgDB is an independent fork of Neo4j® Enterprise Edition version 3.4.0.rc02 licensed under AGPLv3 and/or Community Edition licensed under GPLv3

ONgDB: Graphs for the People!

What is ONgDB?

ONgDB / Owen-Gee-Dee-Bee / which stands for Open Native Graph Database, is an open source, high performance, native graph store with everything you would expect from an enterprise-ready database, including high availability clustering, ACID transactions, and an intuitive, pattern-centric graph query language. Developers use graph theory-based structures that we call nodes and relationships instead of rows and columns. For many use cases, ONgDB will provide orders of magnitude performance benefits compared to non-native graph, relational and NoSQL databases.

Learn more on the Graph Foundation ONgDB site.

Using ONgDB

ONgDB is available both as a standalone server or an embeddable component.

Extending ONgDB

We encourage experimentation with ONgDB. You can build plugins to ONgDB, develop library or drivers atop the product, or make contributions directly to the product core. You’ll need to sign the Graph Foundation Contributor License Agreement to become a contributor.

Note	This GitHub repository contains mixed GPLv3 and AGPLv3 code. Our Community edition (in the community/ directory) is GPLv3. Our Enterprise edition (enterprise/) is differently licensed under the AGPLv3.

Dependencies

ONgDB is built using Apache Maven version 3.6. Maven requires more memory than the standard configuration which can be achieved with export MAVEN_OPTS="-Xmx512m".

Building ONgDB

Before you start running the unit and integration tests in the ONgDB Maven project on a Linux-like system, you should ensure the limit on open files is set to a reasonable value. You can test it with ulimit -n. We recommend you have a limit of at least 40K.

• Run mvn clean install -DfullBuild -Drevapi.skip=true -DcreateChecksum=true to build end-to-end with all tests.

• In case you want to skip tests add the -DskipTests flag to the previous command.

• You may need to increase the memory available to Maven: export MAVEN_OPTS="-Xmx512m".

Running ONgDB

After building, cd into packaging/standalone/target and extract the edition you want, then

bin/ongdb start

in the extracted folder to start ONgDB on localhost:7474.

On Windows you want to run

bin\ongdb start

instead.

Licensing

ONgDB Community Edition is an open source product licensed under GPLv3.

ONgDB Enterprise Edition expands the functionality of Community Edition with Enterprise-grade features.

ONgDB Enterprise Edition consists of modules from ONgDB Community Edition and modules licensed under AGPLv3 in this repository.

Unaffiliated with Neo4j, Inc.

ONgDB is an independent fork of Neo4j® Enterprise Edition version 3.4.0.rc02 licensed under the AGPLv3 and/or Community Edition licensed under GPLv3. ONgDB and Graph Foundation, Inc. are not affiliated in any way with Neo4j, Inc. or Neo4j Sweden AB. Neo4j, Inc. and Neo4j Sweden AB do not sponsor or endorse ONgDB and Graph Foundation, Inc. Neo4j Sweden AB is the owner of the copyrights for Neo4j® software and commercial use of any source code from Neo4j® Enterprise Edition beyond Neo4j® Enterprise Edition version 3.2.14, Neo4j® Enterprise Edition version 3.3.10, and/or Neo4j® Enterprise Edition version 3.4.0.rc02 is prohibited and could subject the user to claims of copyright infringement.

ongdb's Issues

support for Bolt protocols ('3.0', '4.1', '4.2', '4.3', '4.4', '5.0', '5.1', '5.2', '5.3', '5.4') - exception connecting with python neo4j

Hello.

I am trying to connect using a python script, and I am getting the bellow message:

neo4j._exceptions.BoltHandshakeError: The neo4j server does not support communication with this driver. This driver has support for Bolt protocols ('3.0', '4.1', '4.2', '4.3', '4.4', '5.0', '5.1', '5.2', '5.3', '5.4').

Are we completely out of compatibility with all these Bolt protocol versions? Is there an easy and accessible way to connect python to the ongdb backend, please?

---

Note: It seems related to this jira issue, but the server is down and archive.org has no record of it:
[ONGDB-223] – Bolt version needs to be compatible with driver checks

( https://graphfoundation.org/ongdb/1.0.0-alpha01/ )

details to reproduce the error

1. Create a python script file script.py:

# script.py
from neo4j import GraphDatabase

uri = 'bolt://localhost:7687' # or neo4j://localhost
auth = ('ongdb', 'ongdb')

with GraphDatabase.driver(uri, auth=auth) as driver:
    driver.verify_connectivity()

2. Install python3 and pipenv (debian):

sudo apt-get install python3 pipenv

3. Create an environment on the same directory where the script.py lives, install neo4j python library and run the script:

pipenv shell
pipenv install neo4j
python script.py

Upgrading to lucene 7.1.x to fix

Github security scanner points this out. Would you like to comment that ongdb is not prone to this exploit?

Remediation
Upgrade org.apache.lucene:lucene-core to version 7.1.0 or later. For example:

<dependency>
  <groupId>org.apache.lucene</groupId>
  <artifactId>lucene-core</artifactId>
  <version>[7.1.0,)</version>
</dependency>

Always verify the validity and compatibility of suggestions with your codebase.

CVE-2017-12629
high severity
Vulnerable versions: < 7.1.0
Patched version: 7.1.0
Remote code execution occurs in Apache Solr before 7.1 with Apache Lucene before 7.1 by exploiting XXE in conjunction with use of a Config API add-listener command to reach the RunExecutableListener class. Elasticsearch, although it uses Lucene, is NOT vulnerable to this. Note that the XML external entity expansion vulnerability occurs in the XML Query Parser which is available, by default, for any query request with parameters deftype=xmlparser and can be exploited to upload malicious data to the /upload request handler or as Blind XXE using ftp wrapper in order to read arbitrary local files from the Solr server. Note also that the second vulnerability relates to remote code execution using the RunExecutableListener available on all affected versions of Solr.

There is no procedure with the name `CALL dbms.cluster.routing.getRoutingTable` registered for this database instance.

CALL dbms.routing.getRoutingTable({}, "neo4j")
╒═════╤══════════════════════════════════════════════════════════════════════╕
│"ttl"│"servers" │
╞═════╪══════════════════════════════════════════════════════════════════════╡
│300 │[{"addresses":["localhost:7687"],"role":"WRITE"},{"addresses":["localh│
│ │ost:7687"],"role":"READ"},{"addresses":["localhost:7687"],"role":"ROUT│
│ │E"}] │
└─────┴──────────────────────────────────────────────────────────────────────┘

CALL dbms.cluster.routing.getRoutingTable({},"neo4j")
╒═════╤══════════════════════════════════════════════════════════════════════╕
│"ttl"│"servers" │
╞═════╪══════════════════════════════════════════════════════════════════════╡
│300 │[{"addresses":["localhost:7687"],"role":"WRITE"},{"addresses":["localh│
│ │ost:7687"],"role":"READ"},{"addresses":["localhost:7687"],"role":"ROUT│
│ │E"}] │
└─────┴──────────────────────────────────────────────────────────────────────┘
https://neo4j.com/docs/operations-manual/3.5/clustering-advanced/multi-data-center/load-balancing/

We need both of these procedure... up:)

org.neo4j.driver
neo4j-java-driver
4.0.1

ERROR:

Caused by: org.neo4j.driver.exceptions.ClientException: There is no procedure with the name `dbms.cluster.routing.getRoutingTable` registered for this database instance.

CALL dbms.routing.getRoutingTable({}, "neo4j")
╒═════╤══════════════════════════════════════════════════════════════════════╕
│"ttl"│"servers"                                                             │
╞═════╪══════════════════════════════════════════════════════════════════════╡
│300  │[{"addresses":["localhost:7687"],"role":"WRITE"},{"addresses":["localh│
│     │ost:7687"],"role":"READ"},{"addresses":["localhost:7687"],"role":"ROUT│
│     │E"}]                                                                  │
└─────┴──────────────────────────────────────────────────────────────────────┘

CALL dbms.cluster.routing.getRoutingTable({},"neo4j")
╒═════╤══════════════════════════════════════════════════════════════════════╕
│"ttl"│"servers"                                                             │
╞═════╪══════════════════════════════════════════════════════════════════════╡
│300  │[{"addresses":["localhost:7687"],"role":"WRITE"},{"addresses":["localh│
│     │ost:7687"],"role":"READ"},{"addresses":["localhost:7687"],"role":"ROUT│
│     │E"}]                                                                  │
└─────┴──────────────────────────────────────────────────────────────────────┘

CALL dbms.cluster.routing.getRoutingTable
CALL dbms.directories.data
CALL dbms.directories.import
CALL dbms.connectors.default_listen_address
CALL dbms.connector.bolt.tls_level
CALL dbms.windows_service_name
CALL dbms.database.state("db")
CALL test.driver.longRunningStatement
CALL test.driver.longStreamingResult

YES:

CALL dbms.cluster.role()
CALL dbms.cluster.overview()
CALL dbms.listTransactions()
CALL dbms.components() YIELD edition
CALL dbms.listQueries() YIELD query RETURN query

VERSION:

ongdb-version-3.5.17
neo4j-java-driver-4.1

Upstream version of OngDB

What upstream version is ongdb based on? In browser dashboard under DBMS it says version 3.4.0.

If this is actually based on version 3.4.0 then why versions of 3.5/3.6 has been removed?

I am asking this because we are encountering a bug that was not in 3.5.

Release Roadmap

Hi,
first of all, thanks a lot for the great work!

I would like to ask, if you have a planned release date for ONgDB 2.0? I noticed additional branches "2.0" and "2.0-dev" indicating a new major version, but without feature-commits so far. What are your plans regarding future releases in general? Do you have something like a rough release roadmap to share?

Best regards,
Martin

About ONGDB new data storage slow problem

In the process of data insertion, when the amount of data increases to millions, the problem of slow entry of new data will occur. Whether it is in a single machine or in a cluster mode, the data will be added too slowly, and the insertion problem will occur about once every 3 seconds.
It could be a relationship where I put a unique constraint on the data.
It's not clear exactly what caused it.

When will the latest 4.x version be released?

java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired: 30000/30000 ms

/db/data/transaction/commit java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired: 30000/30000 ms

neo4j similar issue：neo4j/neo4j#10223
ongdb: 3.5.17
os: CentOS-7.5

Feature Request: Document Steps to Create Database in ONgDB Enterprise

Description

Since ONgDB is a fork of Neo4j, I figured that ONgDB Enterprise might be targeting feature parity with Neo4j Enterprise. One of the features of Neo4j Enterprise is the ability to create a new database besides the two default DBs (system and neo4j) by running :use system followed by CREATE DATABASE foo;.

I tried this with ONgDB version 1.0.5, and I got the same error that Neo4j community would give:

$ :use system
$ CREATE DATABASE plzwork

ERROR Neo.ClientError.Statement.UnsupportedAdministrationCommand
Unsupported administration command: EXPLAIN CREATE DATABASE plzwork

I tried finding examples in the ONgDB documentation and this GitHub repository but I wasn't able to find any.

I understand that we're supposed to ask questions like this in StackOverflow, but I see there already is one asking about database creation that remains unanswered after 11 months.

So, I thought I might phrase my questions as a feature request to justify asking them in GH Issues. My questions are:

1. Is the CREATE DATABASE command supported by ONgDB Enterprise?
2. If so, how does it work?
3. Is there any documentation related to CREATE DATABASE for ONgDB, Enterprise or otherwise?
4. If not, would you be willing to add some? I would be happy to help with this part however I can.

System Info

• ONgDB version: 1.0.5
• Host operating system: Ubuntu 22.04.3 LTS (Jammy Jellyfish)
• Container operating system: Debian GNU/Linux 11 (bullseye)
• API/Driver: unsure, running from official image built from this Dockerfile and using the browser-based IDE (the ONgDB equavalent of Neo4j Browser).

Steps to reproduce

1. Pull the image: docker pull graphfoundation/ongdb:1.0.5
2. Start a new container that mounts to this directory: docker run -d --name ongdb-test -p 7474:7474 -v /home/ongdb:/data graphfoundation/ongdb:1.0.5
3. Open the web UI in a browser by navigating to http://localhost:7474 and logging in with ongdb for the username and password.
4. In the query editor at the top of the page, run :use system to use the system database.
5. In the query editor, run CREATE DATABASE plzwork.
6. The error will appear as described above.

Expected behavior

A new database is created alongside the system and neo4j databases.

Actual behavior

An error is thrown which indicates this is an unsupported administration command.

Improve build performance of modules

Hi, I'm now using ongdb. I found that the build time of the project is not very fast when I used  mvn -T 1C install -DskipTests command to build the project during Github Actions. So I try to speed up the build performance of the project. The goal here is to clean up dependencies between maven modules in the project in order to improve the build performance.

Thread usage before cleaning up module dependencies was this:

Using mvn dependency:analyze command I managed to have an overview of the unused dependencies of every module. I focused only on the dependencies between modules. The following dependencies can be cleaned up:

org.graphfoundation.ongdb:ongdb-geequel-compatibility-spec-suite(/enterprise/cypher/compatibility-spec-suite) -> org.graphfoundation.ongdb:ongdb-enterprise-geequel(enterprise/cypher/cypher)
org.graphfoundation.ongdb:ongdb-geequel-acceptance-spec-suite(enterprise/cypher/acceptance-spec-suite) -> org.graphfoundation.ongdb:ongdb-enterprise-geequel(enterprise/cypher/cypher)

After clean up, the build time has been reduced by 1min40s when I use parallel build during Github Actions.
Thread usage after cleaning up module dependencies was this:

Could you help me review this issue? I can submit a PR to improve build performance of the project.

Thank you very much for your attention.
Best regards.

Fix the JDK checks on startup please, and Windows won't start at all

Guidelines

ongdb 1.0.4
Windows Server 2002
AlmaLinux 8.5

Hi all.

This:

ongdb/packaging/standalone/src/main/distribution/shell-scripts/bin/ONgDB-Management/Get-JavaVersion.ps1

Line 110 in 0b53efa

if ($javaVersion -lt '1.8') {

And this:

ongdb/packaging/standalone/src/main/distribution/shell-scripts/bin/ongdb-shell

Line 99 in 182c231

if [[ "${JAVA_VERSION}" < "1.8" ]]; then

Is not how you do a version check. You can't simply compare if a string is less than another and it'll magically understand the periods and the difference between "1.10" and "1.8" or "1.1". What it does mean is ongdb has most likely not been tested, as released, with an different JDK than 1.8.

I know you expect to support all the common JDKs:

ongdb/packaging/standalone/src/main/distribution/shell-scripts/bin/ongdb-shell

Line 105 in 182c231

if ! ("${version_command[@]}" 2>&1 | egrep -q "(Java HotSpot\\(TM\\)|OpenJDK|IBM) (64-Bit Server|Server|Client|J9) VM"); then

You have no ongdb documentation and the project site (https://www.graphfoundation.org/ongdb/) doesn't provide documentation, installation or requirement guidance.

I've been using ongdb on Linux for a year now and I had to comment out the JDK check, but recently had to set it up on Windows and it has been a real pain.

JDK 1.17 would fail (obviously because it's not "1.8") and the service would not launch. The only way to know what the problem is (the JDK version issue) you have to manually run the ongdb batch with Verbose to get a clue: C:\Program Files\ongdb\bin>ongdb.bat start -Verbose

So say I jumped back and installed OpenJDK 1.8. Still no luck. I dug in and tried manually running: "C:\Program Files\ongdb\bin\tools\prunsrv-amd64.exe" "//RS//ongdb" and it would silently fail.

C:\Program Files\ongdb\bin>"C:\Program Files\ongdb\bin\tools\prunsrv-amd64.exe" "//ES//ongdb"

Nothing. I retried it with all the logs deleted:

[2023-02-14 23:26:36] [info]  [ 7428] Commons Daemon procrun (1.0.15.0 64-bit) started
[2023-02-14 23:26:36] [info]  [ 7428] Running 'ongdb' Service...
[2023-02-14 23:26:36] [error] [ 7428] StartServiceCtrlDispatcher for 'ongdb' failed
[2023-02-14 23:26:36] [error] [ 7428] The service process could not connect to the service controller.
[2023-02-14 23:26:36] [error] [ 7428] Commons Daemon procrun failed with exit value: 4 (Failed to run service)
[2023-02-14 23:26:36] [error] [ 7428] The service process could not connect to the service controller.

Odd enough, the first hit for "Commons Daemon procrun failed with exit value: 4 (Failed to run service)" was against a Neo4j issue, that was related to but not conclusive, that the problem with JAVA path related.

I took a look at the Neo4j Github and it seems to have cleaned up the service scripts, and their install guidance cites JDK 1.17 so I assume it can be used.

The problem seems to be that I had to re-install the Windows service AFTER downgrading to the 1.8 JDK because it's embedded into the service call.

Seems like a problem waiting to happen if the admin upgrades to a newer version of Java, the old one will keep being used, not the new patched one. If I uninstalled the old version it would mean the ongdb service wouldn't run.

Expected behavior

I expect to know what the ongdb installation requirements are for Linux and Windows.
I expect to be able to install and use the product as a service on Linux and Windows.

This isn't too vague. Simply try installing with a JDK version newer than 1.8 and it will fail. Trying to track down ongdb installation requirements is impossible. Resorting to using old graphdb or neo4j docs is no longer safe for an administrator because the shell scrips are different now.

Actual behavior

Please add Infrastructure as Code template to get started easily

Dev Ops Feature Request

This seems like a compelling project but it's not clear how to get started. As an engineer I like to get started quickly with infrastructure as code like Terraform, Pulumi, Cloudformation, AWS CDK, or just Makefiles to deploy a cloud solution

Describe the solution you'd like
Do you think it would be possible to add an infrastructure as code script to deploy an autoscaling OngDB causal cluster on AWS? That would accelerate this community a lot because you could run an idempotent / modular / declarative template to make a cluster and get an API endpoint for your app

Describe alternatives you've considered
I gave up on Neo4j because of the GPL license, closed-source, pricing hidden behind NDA, no autoscaling on Aura

Additional context
Could use this:
https://www.terraform.io/docs/providers/aws/r/autoscaling_group.html

Here's a template which makes an autoscaling group with a load balancer:
https://github.com/terraform-aws-modules/terraform-aws-autoscaling/tree/master/examples/asg_elb

Another option would be to use Pulumi or ECS to code this infrastructure in a programming language rather than a template languate like YAML (cloudformation) or HCL (terraform). Could just make an autoscaling ECS cluster with a load balancer like this:

https://www.pulumi.com/docs/guides/crosswalk/aws/ecs/

Here's a CDK example which would generate a bajillion lines of Cloudformation to deploy ONGdb on AWS:

const loadBalancedEcsService = new ecsPatterns.ApplicationLoadBalancedEc2Service(stack, 'Service', {
  cluster,
  memoryLimitMiB: 1024,
  taskImageOptions: {
    image: ecs.ContainerImage.fromRegistry('test'),
    environment: {
      TEST_ENVIRONMENT_VARIABLE1: "test environment variable 1 value",
      TEST_ENVIRONMENT_VARIABLE2: "test environment variable 2 value"
    },
  },
  desiredCount: 2,
});

https://docs.aws.amazon.com/cdk/api/latest/docs/@aws-cdk_aws-ecs-patterns.ApplicationLoadBalancedEc2Service.html

here are a ton of examples of AWS CDK doing docker cluster services with load balancers, logging, networking etc

https://github.com/aws-samples/aws-cdk-examples/tree/master/typescript/ecs

TLDR: For this project to blow up, it needs to be easy to deploy an autoscaling / load balanced DB cluster and get an endpoint. If you write a document that says, "click here, type this, copy this here" it's subject to interpretation and will probably get screwed up, and it's slow. If you make Infrastructure as Code to deploy an autoscaling / load balanced causal cluster, then this project becomes 100x easier to get new developers and users, because they know they can deploy in a reproducible way with 1 line of code. If something goes wrong, they can easily re-deploy. If they need a dev cluster in their CI/CD pipeline, they can do that with 1 line and destroy it at the end to save money no problem.

I'm super bullish on infrastructure as code because it lets us automate the complicated setup process of cloud resources. Do you want to manually spend 1-2 hours deploying the database, or do you want to run 1 line of code?

Happy to help make this happen, let me know

Metrics sucking up disk space and no way to configure a retention policy or limit

I discovered a couple of VMs we run ongdb on using 15GB of disk space due to the size of the metrics csv files. I had to manually delete them to free up space. I couldn't find much information on how metrics are managed or if a retention policy could be set.

If deleting the files occasionally is what's required, I can deal with that but it would be nice if the system would limit usage like it does with log rotation. More over, is deleting the csv files save?

ONgDB Version: 1.0.4 (currently we intend to move to 1.0.5 soon)
Operating System: Alma Linux 8.something

Expected behavior

Disk usage is limited to a reasonable amount

Actual behavior

Disk usage is outsized for the size of the DB. e.g. 15GB

Status of Project Post Open Core Licensing Model

What is status of this project post Open Core Licensing Model?

I do see releases of v3.5.2 and v3.5.3 in last commit but it would be good to know status of this project and how change in Neo4j liceancing model changes things.

'Tried to copy more data into less' bug fixed in 3.5.4 is now back in 3.5.14

Guidelines

Please note that GitHub issues are only meant for bug reports/feature requests.
If you have questions on how to use Neo4j, please ask on StackOverflow instead of creating an issue here.

To help us understand your issue, please specify important details, primarily:

• ONgDB version: 3.5.14

• Operating system: Mac Big Sur 11.1

• Steps to reproduce
  Ran a query (in the browser) that works fine in Neo Enterprise v. 3.5.19, as well as with ONgDB 3.5.4, 3.5.11 and 3.5.12. However when I try with 3.5.14, I get the error message. The query contains a line with pattern comprehension, which seems to cause the issue:
  return head([(c)-[:HAS_GROUP]->(g) | g.GRP_LONG]) as Subarea

ONgDB clustering (Neo4j fork?)

Hi.

We are setting up an ONgDB cluster for high performance. Two questions arise here -
a. Is release 3.6.2 a candidate that is recommended or should we stick with 3.5.22 LTS instead.
b. When setting up clustering, which set of instructions should be followed from Neo4j operation guides, i.e. 3.x or 4.x set of instructions, since the settings are different for the two. The answer (probably) would be influenced by the Neo4j version the forks are from. Would you recommend following the Neo4j 3.5 set of instructions for the same (https://neo4j.com/docs/operations-manual/3.5/clustering/introduction/#causal-clustering-introduction-operational), or 4.x ?
We are open to using versions 3.6.2 or 3.5.22: Though 3.5.22 is certainly LTS.

Advice on this matter is highly appreciated.

Kind regards

When will the 4.0 version be released？

so，When will the 4.0 version be released？

Looking forward to the multi-database feature....

ongdb version 3.6.2 and the latest 1.0.0 release use third party libraries with high security vulnerabilities

we are using ongdb version 3.6.2. This release, and also the latest release 1.0.0, use third party libraries with high security vulnerabilities:

1. 'shiro-core-1.6.0' is marked with this high vulnerability:

   • CVE-2021-41303

   'shiro-core' need to be upgraded to version 'shiro-core:1.8.0'

2. 'netty-all-4.1.43.Final' is marked with these high vulnerabilities:

   • CVE-2020-7238
   • CVE-2020-11612
   • CVE-2019-20445
   • CVE-2021-37136
   • CVE-2021-37137
   • CVE-2019-20444

   'netty-all' need to be upgraded to version 'netty-all-4.1.73.Final'

3. 'netty-3.9.9.Final' is marked with this high vulnerability:

   • CVE-2019-20444

Questions in terms of enterprise version

Hi,

Thanks for having ongdb.

In terms of enterprise version, I have a question. As far as I know, neo4j has deleted the 'enterprise' code base starting from 3.5, whereas ongdb still maintains the 'enterprise' part, does it merge from the official neo4j code base prior to 3.5 ? Will ongdb adds new features to this part in the future ? (I am not diving into the code details yet, sorry for a quick ask)

Is it a problem to create multiple users?I created a user login failed! v-3.5.16

Use of mutation testing in ongdb - Help needed

Hello there!

My name is Ana. I noted that you use the mutation testing tool pit in the project.
I am a postdoctoral researcher at the University of Seville (Spain), and my colleagues and I are studying how mutation testing tools are used in practice. With this aim in mind, we have analysed over 3,500 public GitHub repositories using mutation testing tools, including yours! This work has recently been published in a journal paper available at https://link.springer.com/content/pdf/10.1007/s10664-022-10177-8.pdf.

To complete this study, we are asking for your help to understand better how mutation testing is used in practice, please! We would be extremely grateful if you could contribute to this study by answering a brief survey of 21 simple questions (no more than 6 minutes). This is the link to the questionnaire https://forms.gle/FvXNrimWAsJYC1zB9.

Drop me an e-mail if you have any questions or comments ([email protected]). Thank you very much in advance!!

Understanding why ONgDB uses AGPLv3

Hi,

I was wondering why does ONgDB use AGPLv3 for its enterprise features. Is it because the code it originated from (i.e Neo4j's enterprise code) was AGPLv3?

Thanks!

query logging is not working on enterprise

• Neo4j version: 3.5.4
• Operating system: Ubuntu 16.04
• API/Driver: none
• Steps to reproduce
• Expected behavior : query.log file collect the logs, with configuration of enabling query.log. set true (on conf/neo4j.conf)
• Actual behavior: not collecting any query, the file size of query.log is always 0

Additionally, include (as appropriate) log-files, stacktraces, and other debug output.

Steps to reproduce

1. download tarball on https://www.graphfoundation.org/projects/ongdb/

• file name: ongdb-enterprise-3.5.4-unix.tar.gz

2. set enable query logging on file, "conf/neo4j.conf" (remove '#' query.log~~= )
3. start neo4j

Note: Compare to enterprise, 1 month trial version of neo4j,
it works with same steps above.
Note: I tried this with all version of 3.4.0 source code, with maven compile, and run it but, ongDB enterprise version does not collect query.log.
"query.log" is only activated on enterprise model on neo4j.

Expected behavior

logs/query.log should be collecting the logs and changing of file size

Actual behavior

logs/query.log file size always 0.

Cypher query returns error in 3.5.19 , 3.5.22 and 3.5.26 while it was running in 3.5.4

this query

MATCH (n1)<--(n2)-->(n3)
WHERE n1 <> n3
WITH n2 limit 1
RETURN [(n2)-->(m) | id(m)][0]

returns an error on 3.5.19 , 3.5.22 and 3.5.26 while on 3.5.4 it returns an id.

Without the array index at the end, it runs well and returns the expected array of ids.

MATCH (n1)<--(n2)-->(n3)
WHERE n1 <> n3
WITH n2 limit 1
RETURN [(n2)-->(m) | id(m)]

FYI.. the corresponding Neo4j versions do not seem to suffer from this issue.

version 4.0 release date

is there any plan to release version 4.0 for ongdb

Compatibility with Neosemantics

Dear ONgDB People!

You are doing the right thing! I will support you anyway I can. Essential technology has to remain a common good.

My RDF-Project (an Open Data Project) is based on Blazegraph which is dead. So I like to migrate to another graph DB. Neo4J looks promising but only from a distance. So I finally ended up here.

The key requirement for my work is SHACL which is part of Neosemantics.

The current Version of Neosemantics 4.3 does not run with ongdb (ongdb-enterprise-1.0.0-beta01). It may run with this version but I may be to stupid to get it work. I am a Python and not a Java programmer.

What are the known working version combinations of ONgDB and Neosemantics?
And last but not least: Has anyone yet get SHACL up and run on ONgDB with Neosemantics?

Any help or pointers appreciated!

Cheers,
Volker

Roadmap for 4.x

Hi, I do see a branch for 4.x version that seems to be W.I.P.

Any idea when approximately 4.x is planned to be released?

Dockerhub images and tags for ongdb project

Hi guys,

All tags and images of ongdb is not available at dockerhub.com. Any idea what's happened?

Currently it´s not possible to run any container

Thanks

A query guard like this would be a good feature to add at some point. - Slack Feature Request

• Tony Ma Jan 14th at 9:11 AM

How do I disable certain queries?And available for all non-administrator accounts? eg. I have to disable this query.  MATCH (n) DELETE n

• bradnussbaum

I believe this can be done with a procedure that uses a pre-commit hook.

• bradnussbaum

But would need to be written custom.

• bradnussbaum

A query guard like this would be a good feature to add at some point.

• Tony Ma

Yes,It would be great to upgrade a smaller version(eg.3.5.23) and add this feature.

Add sample systemctl unit file, SELinux policy, and supporting files

My current work involves ONGDB under various Fedora Linux, including RHEL and CentOS. For this work, we need ONGDB running as a systemctl service. We've located example unit files, and have gotten it working, but on some boxes, only with SELinux disabled - for now - this obviously isn't the best long term (or even medium term) approach.

I plan to address this with:

1. A minimal unit file (just enough to get ONGBD running as a persistent service)
2. A minimal SELinux policy (just enough... I do SELinux development as part of my day job)
3. A minimal installation script (just enough to get the unit file into the right place, enable the service, and install the policy)

I am assuming that once I have this working, the project may entertain a PR that includes a systemctl sub-folder will all the right pieces?

Please advise,

Thanks,

P

Is this project dead?

There has been no activity since February of this year, leading me to the obvious - did you guys abandon this project?

I encountered a problem with 3.6.0.M1.The two nodes could not start properly.But 3.5.16 is ok.

I encountered a problem with 3.6.0.M1.The two nodes could not start properly.But 3.5.16 is ok.
node-1 neo4j.conf

dbms.connectors.default_listen_address=0.0.0.0
dbms.connectors.default_advertised_address=node-1
dbms.connector.bolt.enabled=true
dbms.connector.bolt.listen_address=:7687
dbms.connector.http.enabled=true
dbms.connector.http.listen_address=:7474
dbms.connector.https.enabled=true
dbms.connector.https.listen_address=:7473
dbms.mode=CORE
causal_clustering.minimum_core_cluster_size_at_formation=2
causal_clustering.minimum_core_cluster_size_at_runtime=2
causal_clustering.initial_discovery_members=node-1:5000,node-2:5001
causal_clustering.discovery_listen_address=:5000
dbms.jvm.additional=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005

node-2 neo4j.conf

dbms.connectors.default_listen_address=0.0.0.0
dbms.connectors.default_advertised_address=node-2
dbms.connector.bolt.enabled=true
dbms.connector.bolt.listen_address=:7687
dbms.connector.http.enabled=true
dbms.connector.http.listen_address=:7474
dbms.connector.https.enabled=true
dbms.connector.https.listen_address=:7473
dbms.mode=CORE
causal_clustering.minimum_core_cluster_size_at_formation=2
causal_clustering.minimum_core_cluster_size_at_runtime=2
causal_clustering.initial_discovery_members=node-1:5000,node-2:5001
causal_clustering.discovery_listen_address=:5001
dbms.jvm.additional=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005

error.log

2020-04-05 10:17:43.964+0000 INFO  Waiting for a total of 2 core members...
2020-04-05 10:17:56.855+0000 ERROR Failed to start Neo4j: Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase@6569dded' was successfully initialized, but failed to start. Please see the attached cause exception "Failed to join a cluster with members {clusterId=null, bootstrappable=true, coreMembers={MemberId{1b03f597}=CoreServerInfo{raftServer=node-2:7000, catchupServer=node-2:6000, clientConnectorAddresses=bolt://node-2:7687,http://node-2:7474,https://node-2:7473, groups=[], database=default, refuseToBeLeader=false}}}. Another member should have published a clusterId but none was detected. Please restart the cluster.". Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase@6569dded' was successfully initialized, but failed to start. Please see the attached cause exception "Failed to join a cluster with members {clusterId=null, bootstrappable=true, coreMembers={MemberId{1b03f597}=CoreServerInfo{raftServer=node-2:7000, catchupServer=node-2:6000, clientConnectorAddresses=bolt://node-2:7687,http://node-2:7474,https://node-2:7473, groups=[], database=default, refuseToBeLeader=false}}}. Another member should have published a clusterId but none was detected. Please restart the cluster.".
org.neo4j.server.ServerStartupException: Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase@6569dded' was successfully initialized, but failed to start. Please see the attached cause exception "Failed to join a cluster with members {clusterId=null, bootstrappable=true, coreMembers={MemberId{1b03f597}=CoreServerInfo{raftServer=node-2:7000, catchupServer=node-2:6000, clientConnectorAddresses=bolt://node-2:7687,http://node-2:7474,https://node-2:7473, groups=[], database=default, refuseToBeLeader=false}}}. Another member should have published a clusterId but none was detected. Please restart the cluster.".
	at org.neo4j.server.exception.ServerStartupErrors.translateToServerStartupError(ServerStartupErrors.java:45)
	at org.neo4j.server.AbstractNeoServer.start(AbstractNeoServer.java:187)
	at org.neo4j.server.ServerBootstrapper.start(ServerBootstrapper.java:124)
	at org.neo4j.server.ServerBootstrapper.start(ServerBootstrapper.java:91)
	at org.neo4j.server.enterprise.EnterpriseEntryPoint.main(EnterpriseEntryPoint.java:41)
Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.server.database.LifecycleManagingDatabase@6569dded' was successfully initialized, but failed to start. Please see the attached cause exception "Failed to join a cluster with members {clusterId=null, bootstrappable=true, coreMembers={MemberId{1b03f597}=CoreServerInfo{raftServer=node-2:7000, catchupServer=node-2:6000, clientConnectorAddresses=bolt://node-2:7687,http://node-2:7474,https://node-2:7473, groups=[], database=default, refuseToBeLeader=false}}}. Another member should have published a clusterId but none was detected. Please restart the cluster.".
	at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:473)
	at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:111)
	at org.neo4j.server.AbstractNeoServer.start(AbstractNeoServer.java:180)
	... 3 more
Caused by: java.lang.RuntimeException: Error starting org.neo4j.graphdb.facade.GraphDatabaseFacadeFactory, /home/ongdb/Desktop/ongdb-node-1/data/databases
	at org.neo4j.graphdb.facade.GraphDatabaseFacadeFactory.initFacade(GraphDatabaseFacadeFactory.java:232)
	at org.neo4j.causalclustering.core.OpenEnterpriseCoreGraphDatabase.<init>(OpenEnterpriseCoreGraphDatabase.java:52)
	at org.neo4j.server.enterprise.OpenEnterpriseGraphFactory.newGraphDatabase(OpenEnterpriseGraphFactory.java:43)
	at org.neo4j.server.database.LifecycleManagingDatabase.start(LifecycleManagingDatabase.java:90)
	at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:452)
	... 5 more
Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.causalclustering.core.state.CoreLife@53667cbe' was successfully initialized, but failed to start. Please see the attached cause exception "Failed to join a cluster with members {clusterId=null, bootstrappable=true, coreMembers={MemberId{1b03f597}=CoreServerInfo{raftServer=node-2:7000, catchupServer=node-2:6000, clientConnectorAddresses=bolt://node-2:7687,http://node-2:7474,https://node-2:7473, groups=[], database=default, refuseToBeLeader=false}}}. Another member should have published a clusterId but none was detected. Please restart the cluster.".
	at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:473)
	at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:111)
	at org.neo4j.graphdb.facade.GraphDatabaseFacadeFactory.initFacade(GraphDatabaseFacadeFactory.java:227)
	... 9 more
Caused by: java.util.concurrent.TimeoutException: Failed to join a cluster with members {clusterId=null, bootstrappable=true, coreMembers={MemberId{1b03f597}=CoreServerInfo{raftServer=node-2:7000, catchupServer=node-2:6000, clientConnectorAddresses=bolt://node-2:7687,http://node-2:7474,https://node-2:7473, groups=[], database=default, refuseToBeLeader=false}}}. Another member should have published a clusterId but none was detected. Please restart the cluster.
	at org.neo4j.causalclustering.identity.ClusterBinder.bindToCluster(ClusterBinder.java:177)
	at org.neo4j.causalclustering.core.state.CoreLife.start0(CoreLife.java:74)
	at org.neo4j.kernel.lifecycle.SafeLifecycle.transition(SafeLifecycle.java:124)
	at org.neo4j.kernel.lifecycle.SafeLifecycle.start(SafeLifecycle.java:138)
	at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:452)
	... 11 more
2020-04-05 10:17:56.858+0000 INFO  Neo4j Server shutdown initiated by request

Query fails with error and then starts to just hang from second time

Following as an simplified example of query that fails with an error as mentioned below. From second time, it just shows nothing.

CREATE (q:Q{id:'123'})
WITH q
OPTIONAL MATCH (e:E{id: '456'})
MERGE (e)<-[:TAGGED]-(q)
RETURN e,q;

ERROR Client triggered an unexpected error [Neo.DatabaseError.General.UnknownError]: Access to record Node[-1,used=false,rel=-1,prop=-1,labels=Inline(0x0:[]),light,secondaryUnitId=-1] went out of bounds of the page. The record size is 15 bytes, and the access was at offset -15 bytes into page 0, and the pages have a capacity of 8190 bytes. The mapped store file in question is xxxxxx/neostore.nodestore.db, reference 453e4da6-a9c7-4073-9a1f-25104b79a8e2.

This is happening on all OngDB versions.

Expected output: This query should fail softly as optional match is not found. It should not just get stuck and freeze/hang.

Support for GDS enterprise library

Hello every one.
Does Ongdb support for Neo4j GDS enterprise library?

neo4j-admin 3.5 backup does not explain it could not connect to server

Guidelines

To help us understand your issue, please specify important details, primarily:

• ONgDB version: 3.5.17
• Operating system: Linux (Ubuntu 18.04)
• API/Driver: (for example Cypher/Java API/Python driver vX.Y.Z)

Steps to reproduce

1. Do not run a ongdb server (or any other server) on 127.0.0.1:6462
2. Ask neo4j-admin to perform a backup from that address:

   ongdb_backup=$(mktemp -d)
   report_dir=$(mktemp -d)
   JAVA_HOME=$(oracle_jdk8) \
   neo4j-admin backup \
       --protocol=catchup \
       --from=127.0.0.1:6462 \
       --backup-dir=$ongdb_backup \
       --cc-report-dir=$report_dir \
       --name=backup; echo $?

Expected behavior

An error message indicating that no server responded from `127.0.0.1:6462`.
Bonus points for an exit code that distinguishes between "spoke to a server" and "couldn't speak to a server".

Actual behavior

```
The selected protocol `catchup` means that it is only compatible with causal clustering instances
command failed: Failed to run a backup using the available strategies.
1
```

Additionally, include (as appropriate) log-files, stacktraces, and other debug output.

• There are no log files generated -- this is part of the problem
• There are no stack traces generated -- this is part of the problem
• There is no debug output, and there isn't any obvious way to enable debug output -- this is part of the problem (version 4.0 supports a --verbose flag -- I'm not sure if it would help)

https://neo4j.com/docs/operations-manual/3.5/backup/performing/#backup-performing-command says that 1 means:

Backup failed.

This is correct, the backup failed.

It also isn't helpful. It'd be much more helpful if I could distinguish between "could not connect to server" and "I spoke to the server and things went bad". I'm fairly certain that the second case can happen. -- If not, the documentation should just say that 1 means "could not connect to server" -- and again, I highly doubt that's what it means.

Support for neosemantics

Guidelines

Please note that GitHub issues are only meant for bug reports/feature requests.
If you have questions on how to use ONgDB, please ask on StackOverflow instead of creating an issue here.

Feature request template

Is your feature request related to a problem? Please describe.
Looks like neosemantics (n10s) is not yet supported on the latest version of OngDB (version 3.6).

Describe the solution you'd like
Please consider implementing support for n10s in a future release of OngDB

ONgDB 3.5.22 and 3.6.2 Docker Images on Docker Hub.

ONgDB 3.5.22 and 3.6.2 Docker images on Docker Hub.

Could you please point me to the location to download Docker images for versions 3.5.22 and 3.6.2 please?
The docker images for the versions stated above were available at hub.docker.com .
I only see images tagged 1.0 and 1.0.0-alpha. (https://hub.docker.com/r/graphfoundation/ongdb/tags?page=1&ordering=last_updated)

These updates have of course been uploaded in the last 12 hours. Can you please confirm what is the status of the docker images for 3.6.2 and 3.5.22 please and where can these be found and downloaded.
We are a bit stuck in our progress and actually re-thinking our strategy on graph databases and any help will be much appreciated.

Regards
Faiz Usmani
(Architect and Dev @Nymi)

checkstyle 8.26 checkstyle/checkstyle.xml ruleset blocks building ongdb

The build fails (a lot)...

Neo4j Version: 3.5.15 -- 35e2c7d
Operating System: macOS 10.14.6

Steps to reproduce

brew tap AdoptOpenJDK/openjdk
brew cask install adoptopenjdk8-openj9
git clone ssh://[email protected]:graphfoundation/ongdb.git
cd ongdb
git checkout 3.5.15
export JAVA_HOME=/Library/Java/JavaVirtualMachines/adoptopenjdk-8-openj9.jdk/Contents/Home
mvn install
# hit https://github.com/neo4j/licensing-maven-plugin/pull/8
# apply patch to `neo4j/licensing-maven-plugin` and `mvn install`
mvn install

Expected behavior

working neo4j project.

Actual behavior

[INFO] --- maven-checkstyle-plugin:3.1.0:check (validate) @ neo4j-enterprise-kernel ---
[INFO] Starting audit...
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:1: File does not end with a newline. [NewlineAtEndOfFile]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:55:65: '{' at column 65 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:57:29: '{' at column 29 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:61:41: '{' at column 41 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:66:45: '(' is not followed by whitespace. [ParenPad]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:66:86: ')' is not preceded with whitespace. [ParenPad]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:66:88: '{' at column 88 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:71:27: '{' at column 27 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:75:27: '{' at column 27 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:79:46: '{' at column 46 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:84:28: '{' at column 28 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:89:30: '{' at column 30 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:94:42: '{' at column 42 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:99:44: '{' at column 44 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:104:34: '{' at column 34 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:109:36: '{' at column 36 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:114:26: '{' at column 26 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:119:36: '{' at column 36 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:124:36: '{' at column 36 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:129:54: '{' at column 54 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:134:38: '{' at column 38 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:139:26: '{' at column 26 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:144:36: '{' at column 36 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:149:36: '{' at column 36 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:154:29: '{' at column 29 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:159:46: '{' at column 46 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:166:45: '{' at column 45 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:173:53: '{' at column 53 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:178:35: '{' at column 35 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:183:35: '(' is not followed by whitespace. [ParenPad]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:183:49: ')' is not preceded with whitespace. [ParenPad]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:183:51: '{' at column 51 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:187:55: '{' at column 55 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:192:48: '{' at column 48 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:197:29: '{' at column 29 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:202:34: '{' at column 34 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:207:27: '{' at column 27 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:212:38: '(' is not followed by whitespace. [ParenPad]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:212:61: ')' is not preceded with whitespace. [ParenPad]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:212:63: '{' at column 63 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:216:35: '{' at column 35 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:221:36: '{' at column 36 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:226:33: '{' at column 33 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:231:35: '(' is not followed by whitespace. [ParenPad]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:231:59: ')' is not preceded with whitespace. [ParenPad]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:231:61: '{' at column 61 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:236:43: '{' at column 43 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:237:48: '(' is not followed by whitespace. [ParenPad]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:237:66: ')' is not preceded with whitespace. [ParenPad]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:241:63: '{' at column 63 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:242:48: '(' is not followed by whitespace. [ParenPad]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:242:66: ')' is not preceded with whitespace. [ParenPad]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:246:51: '{' at column 51 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:247:48: '(' is not followed by whitespace. [ParenPad]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:247:66: ')' is not preceded with whitespace. [ParenPad]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:251:28: '(' is not followed by whitespace. [ParenPad]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:251:57: ')' is not preceded with whitespace. [ParenPad]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:251:59: '{' at column 59 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:255:34: '{' at column 34 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:256:48: '(' is not followed by whitespace. [ParenPad]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:256:66: ')' is not preceded with whitespace. [ParenPad]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:260:30: '{' at column 30 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:261:48: '(' is not followed by whitespace. [ParenPad]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:261:66: ')' is not preceded with whitespace. [ParenPad]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:265:42: '{' at column 42 should be on a new line. [LeftCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/enterprise/builtinprocs/StubKernelTransaction.java:266: Two or more consecutive empty lines [RegexpMultiline]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/kernel/src/test/java/org/neo4j/kernel/monitoring/tracing/VerbosePageCacheTracerTest.java:130: Line is longer than 160 characters (found 171). [LineLength]
Audit done.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for ONgDB 3.5.15-SNAPSHOT:
[INFO]
[INFO] Neo4j - Build resources ............................ SUCCESS [  1.162 s]
[INFO] ONgDB .............................................. SUCCESS [ 17.943 s]
[INFO] Neo4j - Annotation Processors ...................... SUCCESS [  1.837 s]
[INFO] Zstandard .......................................... SUCCESS [  0.245 s]
[INFO] Neo4j - Common ..................................... SUCCESS [ 22.162 s]
[INFO] Neo4j - Resource interface ......................... SUCCESS [  2.939 s]
[INFO] Neo4j - Collections ................................ SUCCESS [ 13.819 s]
[INFO] Neo4j - Graph Database API ......................... SUCCESS [  7.978 s]
[INFO] Neo4j - Unsafe Access .............................. SUCCESS [  1.193 s]
[INFO] Neo4j - Concurrent ................................. SUCCESS [  4.005 s]
[INFO] Neo4j - IO ......................................... SUCCESS [04:17 min]
[INFO] Neo4j - Logging .................................... SUCCESS [  8.138 s]
[INFO] Neo4j - Configuration .............................. SUCCESS [  1.370 s]
[INFO] Neo4j - Procedure API .............................. SUCCESS [  4.937 s]
[INFO] Neo4j - Diagnostics ................................ SUCCESS [  0.185 s]
[INFO] Neo4j - Value ...................................... SUCCESS [  7.679 s]
[INFO] Neo4j - Random Value ............................... SUCCESS [  2.849 s]
[INFO] Neo4j - Kernel API ................................. SUCCESS [  3.872 s]
[INFO] Neo4j - CSV reading and parsing .................... SUCCESS [  5.923 s]
[INFO] Neo4j - Lucene Index Upgrade ....................... SUCCESS [  2.484 s]
[INFO] Neo4j - Native index ............................... SUCCESS [01:34 min]
[INFO] Neo4j - Native Spatial Index ....................... SUCCESS [01:42 min]
[INFO] Neo4j - SSL ........................................ SUCCESS [  4.878 s]
[INFO] Neo4j - Graph Database Kernel ...................... SUCCESS [05:42 min]
[INFO] Neo4j - Command Line ............................... SUCCESS [ 13.648 s]
[INFO] Neo4j - Lucene Index ............................... SUCCESS [ 40.429 s]
[INFO] Neo4j - Import Command Line Tool ................... SUCCESS [  1.766 s]
[INFO] Neo4j - JMX support ................................ SUCCESS [  7.530 s]
[INFO] Neo4j - Database Management System ................. SUCCESS [ 16.724 s]
[INFO] Neo4j - Graph Algorithms ........................... SUCCESS [  8.883 s]
[INFO] Neo4j - Code Generator ............................. SUCCESS [ 18.651 s]
[INFO] Neo4j - Legacy ..................................... SUCCESS [ 58.532 s]
[INFO] Neo4j - Community Cypher Build ..................... SUCCESS [  2.578 s]
[INFO] openCypher Front End Parent ........................ SUCCESS [  0.682 s]
[INFO] openCypher Utils ................................... SUCCESS [  7.329 s]
[INFO] openCypher Expressions ............................. SUCCESS [  3.182 s]
[INFO] openCypher AST for the Cypher Query Language ....... SUCCESS [ 15.555 s]
[INFO] openCypher Parser .................................. SUCCESS [ 28.130 s]
[INFO] openCypher Rewriting ............................... SUCCESS [ 15.058 s]
[INFO] openCypher Front End ............................... SUCCESS [ 25.205 s]
[INFO] Neo4j - Cypher Intermediate Representation ......... SUCCESS [  9.115 s]
[INFO] Neo4j - Cypher Logical Plans ....................... SUCCESS [ 11.506 s]
[INFO] Neo4j - Cypher Planner SPI ......................... SUCCESS [  1.209 s]
[INFO] Neo4j - Cypher Planner ............................. SUCCESS [02:05 min]
[INFO] Neo4j - Cypher Runtime Utilities ................... SUCCESS [ 14.098 s]
[INFO] Neo4j - Cypher Interpreted Runtime ................. SUCCESS [01:16 min]
[INFO] Neo4j - Cypher ..................................... SUCCESS [01:10 min]
[INFO] Neo4j - Security ................................... SUCCESS [  9.450 s]
[INFO] Neo4j - SLF4J Neo4j Binding ........................ SUCCESS [  2.552 s]
[INFO] Neo4j - Usage Data Collection ...................... SUCCESS [  4.852 s]
[INFO] Neo4j - Fulltext index ............................. SUCCESS [  1.817 s]
[INFO] Neo4j - Data Collector ............................. SUCCESS [  3.425 s]
[INFO] Neo4j - Bolt Protocol Version 1 .................... SUCCESS [ 35.450 s]
[INFO] Neo4j - Consistency Checker ........................ SUCCESS [ 10.814 s]
[INFO] Neo4j - Community .................................. SUCCESS [ 57.201 s]
[INFO] Neo4j - Community (Bill of Materials) .............. SUCCESS [  0.377 s]
[INFO] Neo4j - Server API ................................. SUCCESS [  4.495 s]
[INFO] Neo4j - Community Integration Tests ................ SUCCESS [  2.569 s]
[INFO] Neo4j - Community Integration Test Support ......... SUCCESS [ 17.611 s]
[INFO] Neo4j - Server ..................................... SUCCESS [04:13 min]
[INFO] Neo4j - Server Plugin Tests ........................ SUCCESS [ 19.176 s]
[INFO] Neo4j - Test Harness ............................... SUCCESS [ 58.739 s]
[INFO] Neo4j - Procedure Compiler Core .................... SUCCESS [ 12.073 s]
[INFO] Neo4j - Procedure Compiler Parent POM .............. SUCCESS [  0.080 s]
[INFO] Neo4j - Procedure Compiler Integration Tests ....... SUCCESS [ 25.690 s]
[INFO] Neo4j - Community Kernel Integration Tests ......... SUCCESS [08:45 min]
[INFO] Neo4j - Community Index Integration Tests .......... SUCCESS [08:06 min]
[INFO] Neo4j - Community Import Integration Tests ......... SUCCESS [01:15 min]
[INFO] Neo4j - Community DBMS Integration Tests ........... SUCCESS [ 21.354 s]
[INFO] Neo4j - Community Graph Algorithms Integration Tests SUCCESS [ 12.172 s]
[INFO] Neo4j - Community Consistency Checker Integration Tests SUCCESS [01:26 min]
[INFO] Neo4j - Community Bolt Integration Tests ........... SUCCESS [09:28 min]
[INFO] Neo4j - Community Generic Integration Tests ........ SUCCESS [01:10 min]
[INFO] Neo4j - Community Cypher Integration Tests ......... SUCCESS [13:44 min]
[INFO] Neo4j - Push To Cloud - Admin command .............. SUCCESS [  6.743 s]
[INFO] Neo4j - Cypher Specification Suite Tools ........... SUCCESS [  1.067 s]
[INFO] Neo4j - Cypher Acceptance .......................... SUCCESS [01:49 min]
[INFO] Neo4j - Cypher Compatibility Specification Suite ... SUCCESS [05:47 min]
[INFO] Neo4j - Cypher Expression Evaluator ................ SUCCESS [  3.093 s]
[INFO] Neo4j - Community Build ............................ SUCCESS [  5.364 s]
[INFO] ONgDB - Enterprise Graph Database Kernel Features .. FAILURE [  0.407 s]
[INFO] ONgDB - Enterprise Graph Database Auth Plugin API .. SKIPPED
[INFO] ONgDB - Enterprise Graph Database Security Features  SKIPPED
[INFO] ONgDB - Query Logging .............................. SKIPPED
[INFO] ONgDB - Communication Package ...................... SKIPPED
[INFO] ONgDB - Clustering Infrastructure .................. SKIPPED
[INFO] ONgDB - Graph DB Monitoring and Management tools ... SKIPPED
[INFO] ONgDB - Causal Clustering .......................... SKIPPED
[INFO] ONgDB - Backup Tool ................................ SKIPPED
[INFO] ONgDB - High Availability .......................... SKIPPED
[INFO] ONgDB - Metrics Kernel Extension ................... SKIPPED
[INFO] ONgDB - Enterprise ................................. SKIPPED
[INFO] ONgDB - Enterprise Cypher Build .................... SKIPPED
[INFO] ONgDB - Cypher Physical Planning ................... SKIPPED
[INFO] ONgDB - Compiled Expressions ....................... SKIPPED
[INFO] ONgDB - Cypher Slotted Runtime ..................... SKIPPED
[INFO] ONgDB - Cypher Morsel Runtime ...................... SKIPPED
[INFO] ONgDB - Enterprise Cypher .......................... SKIPPED
[INFO] ONgDB - Enterprise Server .......................... SKIPPED
[INFO] ONgDB - Enterprise Test Harness .................... SKIPPED
[INFO] ONgDB - Deferred Locks ............................. SKIPPED
[INFO] ONgDB - Procedure Compiler Enterprise tests ........ SKIPPED
[INFO] ONgDB - Cypher Acceptance, enterprise edition ...... SKIPPED
[INFO] ONgDB - Cypher Compatibility Specification Suite, enterprise edition SKIPPED
[INFO] ONgDB - Enterprise Build ........................... SKIPPED
[INFO] ONgDB - Integration Tests .......................... SKIPPED
[INFO] ONgDB - Stress Tests ............................... SKIPPED
[INFO] ONgDB - Low Level Tools ............................ SKIPPED
[INFO] Neo4j - Server Assembler ........................... SKIPPED
[INFO] Neo4j - Community Server Assembler ................. SKIPPED
[INFO] ONgDB - Server Assembler ........................... SKIPPED
[INFO] ONgDB - Packaging Build ............................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  01:25 h
[INFO] Finished at: 2020-03-03T18:27:16-05:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.1.0:check (validate) on project neo4j-enterprise-kernel: Failed during checkstyle execution: There are 67 errors reported by Checkstyle 8.26 with checkstyle/checkstyle.xml ruleset. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :neo4j-enterprise-kernel

apply fixes to make it happy, repeat mvn install:

[INFO] --- maven-checkstyle-plugin:3.1.0:check (validate) @ neo4j-com ---
[INFO] Starting audit...
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/com/src/test/java/org/neo4j/com/CommunicationIT.java:214:22: '}' at column 22 should be alone on a line. [RightCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/com/src/test/java/org/neo4j/com/CommunicationIT.java:233:22: '}' at column 22 should be alone on a line. [RightCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/com/src/test/java/org/neo4j/com/CommunicationIT.java:251:22: '}' at column 22 should be alone on a line. [RightCurly]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/com/src/test/java/org/neo4j/com/CommunicationIT.java:269:22: '}' at column 22 should be alone on a line. [RightCurly]

...

[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/causal-clustering/src/test/java/org/neo4j/causalclustering/scenarios/ClusterDiscoveryIT.java:134: Line is longer than 160 characters (found 172). [LineLength]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/causal-clustering/src/test/java/org/neo4j/causalclustering/scenarios/InstalledProtocolsProcedureIT.java:117: Line is longer than 160 characters (found 170). [LineLength]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/causal-clustering/src/test/java/org/neo4j/causalclustering/scenarios/BaseClusterOverviewIT.java:387: Line is longer than 160 characters (found 167). [LineLength]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/causal-clustering/src/test/java/org/neo4j/causalclustering/catchup/storecopy/StoreCopyRequestHandlerTest.java:241:34: '(' is not followed by whitespace. [ParenPad]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/causal-clustering/src/test/java/org/neo4j/causalclustering/catchup/storecopy/StoreCopyRequestHandlerTest.java:241:83: ')' is not preceded with whitespace. [ParenPad]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/causal-clustering/src/test/java/org/neo4j/causalclustering/catchup/storecopy/StoreCopyRequestHandlerTest.java:242:32: '{' at column 32 should be on a new line. [LeftCurly]

...

[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/enterprise/cypher/cypher/src/test/java/org/neo4j/test/EnterpriseTestGraphDatabaseFactory.java:1: File does not end with a newline. [NewlineAtEndOfFile]

...

[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/integrationtests/src/test/java/org/neo4j/procedure/ProcedureIT.java:244: Line is longer than 160 characters (found 165). [LineLength]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/integrationtests/src/test/java/org/neo4j/procedure/ProcedureIT.java:246: Line is longer than 160 characters (found 165). [LineLength]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/integrationtests/src/test/java/org/neo4j/procedure/ProcedureIT.java:263: Line is longer than 160 characters (found 165). [LineLength]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/integrationtests/src/test/java/org/neo4j/procedure/ProcedureIT.java:265: Line is longer than 160 characters (found 220). [LineLength]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/integrationtests/src/test/java/org/neo4j/procedure/ProcedureIT.java:282: Line is longer than 160 characters (found 165). [LineLength]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/integrationtests/src/test/java/org/neo4j/procedure/ProcedureIT.java:284: Line is longer than 160 characters (found 166). [LineLength]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/integrationtests/src/test/java/org/neo4j/procedure/ProcedureIT.java:1371: Line is longer than 160 characters (found 163). [LineLength]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/integrationtests/src/test/java/org/neo4j/TransactionTerminationIT.java:195: Two or more consecutive empty lines [RegexpMultiline]

...

[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/tools/src/test/java/org/neo4j/tools/dump/InconsistencyReportReaderTest.java:75: Line is longer than 160 characters (found 231). [LineLength]
[ERROR] /Users/jsoref/code/neo4j/neo4j-3.5/tools/src/test/java/org/neo4j/tools/org/neo4j/index/GBPTreePlayground.java:32: Using the '.*' form of import should be avoided - org.neo4j.index.internal.gbptree.*. [AvoidStarImport]

I'm trying to both get the build to pass and to some extent record the errors.

The alternative would be for someone to relax the checkstyle rules so that it doesn't trigger failure. But that's not something I understand well enough to do.

ONgDB not listening on 0.0.0.0:5000

I noticed that when I set the config option causal_clustering.discovery_listen_address=0.0.0.0:5000 or causal_clustering.discovery_listen_address=:5000 it actually listens on 127.0.0.1:5000.

ONgDB Version: 1.0.0
Operating System: Ubuntu 20.04.3 LTS
API: openjdk version "1.8.0_292"

Steps to reproduce

set causal_clustering.discovery_listen_address=0.0.0.0:5000 or causal_clustering.discovery_listen_address=:5000

run ongdb

Expected behavior

listen on 0.0.0.0:5000/tcp

Actual behavior

grep 5000 conf/ongdb.conf
causal_clustering.initial_discovery_members=localhost:5000,localhost:5001,localhost:5002
causal_clustering.discovery_listen_address=:5000

netstat -tpln | grep 5000
tcp6       0      0 127.0.0.1:5000          :::*                    LISTEN      3995227/java (edited)