Deprecated API

Contents

• Deprecated Packages
• Deprecated Interfaces
• Deprecated Classes
• Deprecated Methods

Deprecated Packages

Package and Description
org.neo4j.graphmatching
org.neo4j.graphmatching.filter

Deprecated Interfaces

Interface and Description
org.neo4j.graphdb.Expander Deprecated because RelationshipExpander is deprecated. See PathExpander instead.
org.neo4j.graphmatching.filter.FilterExpression
org.neo4j.graphmatching.filter.FilterValueGetter
org.neo4j.graphdb.traversal.InitialStateFactory use InitialBranchState instead, which has got InitialBranchState.reverse() as well.
org.neo4j.graphdb.traversal.PruneEvaluator because of the introduction of Evaluator which combines PruneEvaluator and filtering (Predicate of Paths).
org.neo4j.graphdb.RelationshipExpander in favor or PathExpander. A RelationshipExpander can still be wrapped via StandardExpander.toPathExpander(RelationshipExpander) to act like a PathExpander.
org.neo4j.graphdb.ReturnableEvaluator because of the introduction of a new traversal framework, see more information at TraversalDescription and Traversal and the new traversal framework's equivalent Predicate.
org.neo4j.graphdb.StopEvaluator because of the introduction of a new traversal framework, see more information at TraversalDescription and Traversal and the new traversal framework's equivalent Evaluator.
org.neo4j.graphdb.Traverser because of an unnatural and too tight coupling with Node. Also because of the introduction of a new traversal framework and the usage of it. The new way of doing traversals is by creating a new TraversalDescription from GraphDatabaseService.traversalDescription(), add rules and behaviors to it and then calling TraversalDescription.traverse(Node...).
org.neo4j.graphmatching.ValueMatcher

Deprecated Classes

Class and Description
org.neo4j.graphmatching.filter.AbstractFilterExpression
org.neo4j.graphmatching.AbstractPatternObject
org.neo4j.graphmatching.ArrayPropertyUtil
org.neo4j.graphmatching.CommonValueMatchers
org.neo4j.graphmatching.filter.CompareExpression
org.neo4j.graphmatching.filter.FilterBinaryNode
org.neo4j.graphmatching.PatternElement
org.neo4j.graphmatching.PatternGroup
org.neo4j.graphmatching.PatternMatch
org.neo4j.graphmatching.PatternMatcher
org.neo4j.graphmatching.PatternNode
org.neo4j.graphmatching.PatternRelationship
org.neo4j.graphmatching.PatternUtil
org.neo4j.graphmatching.filter.RegexPattern

Deprecated Methods

Method and Description
org.neo4j.graphdb.factory.GraphDatabaseFactory.addKernelExtension(KernelExtensionFactory) Manipulating kernel extensions is deprecated and will be moved to internal components.
org.neo4j.graphdb.factory.GraphDatabaseFactory.addKernelExtensions(Iterable>) Manipulating kernel extensions is deprecated and will be moved to internal components.
org.neo4j.graphdb.Expander.addRelationsipFilter(Predicate) because of typo, use Expander.addRelationshipFilter(Predicate) instead
org.neo4j.graphdb.traversal.BidirectionalTraversalDescription.collisionPolicy(BranchCollisionPolicy) Please use BidirectionalTraversalDescription.collisionPolicy(BranchCollisionPolicy)
org.neo4j.graphdb.traversal.TraversalDescription.expand(PathExpander, InitialStateFactory) Because InitialStateFactory is deprecated
org.neo4j.graphdb.traversal.TraversalDescription.expand(RelationshipExpander) Because RelationshipExpander is deprecated
org.neo4j.graphdb.Transaction.finish() due to implementing AutoCloseable, where Transaction.close() is called automatically when used in try-with-resource statements.
org.neo4j.graphdb.GraphDatabaseService.getAllNodes() this operation can be found in GlobalGraphOperations instead.
org.neo4j.graphdb.factory.GraphDatabaseFactory.getCacheProviders() Manipulating cache providers is deprecated and will be moved to internal components.
org.neo4j.graphdb.factory.GraphDatabaseFactory.getKernelExtension() Manipulating kernel extensions is deprecated and will be moved to internal components.
org.neo4j.graphdb.GraphDatabaseService.getRelationshipTypes() this operation can be found in GlobalGraphOperations instead.
org.neo4j.graphdb.factory.GraphDatabaseFactory.getTransactionInterceptorProviders() Manipulating cache providers is deprecated and will be moved to internal components.
org.neo4j.graphdb.traversal.Evaluators.returnWhereEndNodeIs(Node...) use Evaluators.includeWhereEndNodeIs(Node...)
org.neo4j.graphdb.traversal.Evaluators.returnWhereLastRelationshipTypeIs(RelationshipType, RelationshipType...) use Evaluators.includeWhereLastRelationshipTypeIs(RelationshipType, RelationshipType...)
org.neo4j.graphdb.factory.GraphDatabaseFactory.setCacheProviders(Iterable) Manipulating cache providers is deprecated and will be moved to internal components.
org.neo4j.graphdb.factory.GraphDatabaseBuilder.setConfig(Map) Use setConfig with explicit Setting instead
org.neo4j.graphdb.factory.GraphDatabaseBuilder.setConfig(String, String) Use setConfig with explicit Setting instead
org.neo4j.graphdb.factory.GraphDatabaseFactory.setKernelExtensions(Iterable>) Manipulating kernel extensions is deprecated and will be moved to internal components.
org.neo4j.graphdb.Node.traverse(Traverser.Order, StopEvaluator, ReturnableEvaluator, Object...) because of an unnatural and too tight coupling with Node. Also because of the introduction of a new traversal framework. The new way of doing traversals is by creating a new TraversalDescription from Traversal.traversal(), add rules and behaviors to it and then calling TraversalDescription.traverse(Node...)
org.neo4j.graphdb.Node.traverse(Traverser.Order, StopEvaluator, ReturnableEvaluator, RelationshipType, Direction) because of an unnatural and too tight coupling with Node. Also because of the introduction of a new traversal framework. The new way of doing traversals is by creating a new TraversalDescription from Traversal.traversal(), add rules and behaviors to it and then calling TraversalDescription.traverse(Node...)
org.neo4j.graphdb.Node.traverse(Traverser.Order, StopEvaluator, ReturnableEvaluator, RelationshipType, Direction, RelationshipType, Direction) because of an unnatural and too tight coupling with Node. Also because of the introduction of a new traversal framework. The new way of doing traversals is by creating a new TraversalDescription from Traversal.traversal(), add rules and behaviors to it and then calling TraversalDescription.traverse(Node...)