Bump neo4j from 1.3.M03 to 3.5.0
Bumps neo4j from 1.3.M03 to 3.5.0.
Release notes
Sourced from neo4j's releases.
Release 3.3.0-beta01
Release Date: 09/14/2017
Neo4j 3.3.0-beta01 is the first beta release of the upcoming Neo4j 3.3.
Highlights
- Fusion index default for new indexes
- Introducing procedures for manual indexes
- Driver upgrade and small improvements to Neo4j Browser
- Detailed Changes and Docs
For the complete list of all changes, please see the changelog.
Look for 3.3 Developer manual here, and 3.3 Operations manual here.
Using pre-GA early access releases
Pre-GA releases of Neo4j are provided under our User Experience Improvement Program (UXIP), intended for evaluation purposes only. Use of this release implies acceptance of the UXIP terms, which include allowing passive reporting about usage. Of course, we would also love to hear active feedback about your experience.
3.2.0-alpha08
Kernel
- Overwriting property with same value no longer generates write command #9056
- More scalable index logging #9063
- Allow skip bad entries logging during import #9103
Cypher
- Improved cypher execution speed on variable length queries where only the distinct pairs of start and end node are of interest. One query to benefit would be
MATCH (a)-[*4..5]->(b) RETURN DISTINCT a, b. #9062- Allow more granular configuration of literals extraction #9093
- It is no longer possible to CREATE or DROP composite uniqueness constraints. To enforce composite uniqueness, we refer to the new NODE KEY constraint. #9135
- Use getDegree instead of expansion #9139
- Correct query type for procedures #9143
- Handle Ands with single value #9149
- Predicates on shortest path and optional match #9156
Packaging
- Removed
neo4j-shared.sh. Functionality is now included in all wrapper scripts directly #9083Security
- Added new role
Editorthat is allowed to read and write data but not allowed to create new tokens. #9081Causal Clustering
- Improve transaction streaming #9070
Tools
... (truncated)
Commits
- See full diff in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -
@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language -
@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language -
@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language -
@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.