Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
branch: pattern-expres…
Commits on Jun 5, 2012
  1. Started Pattern-documentation

    authored
  2. @jakewins

    Merge pull request #583 from systay/relate-with-arrays

    jakewins authored
    Fixes bug where RELATE fails to compare array properties
Commits on Jun 4, 2012
  1. @nawroth

    Merge pull request #572 from jakewins/icon-licenses

    nawroth authored
    Added license and attribution for icons used in webadmin.
Commits on Jun 1, 2012
  1. @jakewins
  2. @jakewins
  3. @jexp

    Merge pull request #562 from systay/pattern-parser

    jexp authored
    Refactored all of the pattern parsing into a single trait, improved error messages
  4. @jexp

    Merge pull request #577 from systay/count-w-no-rows

    jexp authored
    fixes issue #563: COUNT(*) does not return zero from empty result
Commits on May 31, 2012
  1. @simpsonjulian
  2. @tinwelint

    Merge pull request #575 from simpsonjulian/master

    tinwelint authored
    Move Bigger-tests back to Community
  3. @simpsonjulian
  4. @tinwelint
  5. @simpsonjulian
  6. @simpsonjulian
  7. @simpsonjulian
Commits on May 30, 2012
  1. @simpsonjulian
  2. @simpsonjulian

    Move bigger-tests back to community.

    simpsonjulian authored
    The tests that were extracted from this project are back.  What's
    different is that they are now Integration Tests running under the
    Maven Failsafe plugin, and are wired into the 'verify' phase.
    
    Integration Test filenames do not start with the word Test, but
    they do finish with the word IT.  That's how Maven tells them apart.
  3. @simpsonjulian

    Prevent Antrun plugin from failing at build time.

    simpsonjulian authored
    The Antrun plugin seems to need more of Ant than it thinks it does.
    By adding a dependency on the Ant launcher.jar, this intermittent
    error goes away.
  4. @tinwelint

    Fixed a headline level issue

    tinwelint authored
  5. Merge pull request #566 from tinwelint/traversal-fw-additions

    authored
    Additions and changes to the core traversal framework.
  6. @jexp

    Merge pull request #574 from systay/type_problems

    jexp authored
    fixes #573: Arithmetics operations have wrong type
  7. @tinwelint

    Additions and changes to the core traversal framework. Here's a summa…

    tinwelint authored
    …ry of the changes
    
    :Bidirectional traversals:
    The traversal framework has been about providing a starting point and a description of
    how to traverse the graph from that starting point as well as criterias to know
    what to look for and consider a match. In many scenarios both the start point and end
    point of the returned traversal paths are known and will benefit greatly from traversing
    from the two points and see where they meet in the middle. The benefit comes from that
    less relationships needs to be traversed to find the paths. A first version of this ability
    is now built in and such a traversal can be described with a BidirectionalTraversalDescription.
    
    :AllPaths/AllSimplePaths are now bidirectional:
    As a result of implementing bidirectional traversals in the framework the common "all paths"
    and "all simple paths" algorithms now uses that bidirectional feature to reduce the number of
    relationships needed to traverse to find the correct answer, and thus reducing time spent looking
    for them.
    
    :Multiple start nodes:
    A traversal can be given multiple starting points, as opposed to just a single starting point.
    This also applies to bidirectional traversal where multiple start points as well as multiple
    end points can be given.
    
    :PathExpander (RelationshipExpander for Paths):
    RelationshipExpander is good for implementing intelligent traversers which change behavior
    depending on where it is at the moment. The problem with RelationshipExpander is that it accepts
    a Node as argument and hence lacks the full Path information provided by the traversal.
    Therefore a PathExpander is added which accepts a Path as argument and can additionally get
    and modify traversal branch state for even more intelligent traversals.
    
    :TraversalBranch state:
    Each path that a traverser follows (which of course can branch off into new branches recursively)
    can get associated with a state which follows that particular branch as it expands further.
    A PathExpander can see this state and also change it for children branches. It's there to further
    allow for more intelligent PathExpander implementations.
    
    :Metadata about the traversal:
    Ever wondered how many relationships your traverser visited during the traversal?
    Traverser#metadata() provides useful information, currently only number of traversed relationships
    and number of returned paths.
    
    :Path got more useful methods:
    Paths are sometimes used for making decisions where to go next in a traversal (in for example
    a PathExpander). Path#reverseNodes() and Path#reverseRelationshis() was added because it's more
    often the case that it's the last part of a path that is interesting when making decisions.
    A reverse nodes/relationships call returns an iterable for each node/relationship, starting
    from the end of the path. It also allows for a cheaper implementation than Path#nodes() or
    Path#relationships().
    
    :Sort result from traversal:
    A utility sort() method was added to TraversalDescription for getting the returned paths sorted
    (given a Comparator). It will gather all result paths, sort them and return them sorted.
    
    :Traversals produce less garbage and holds less memory:
    Some memory and garbage considerations have been addressed so that each traversal takes less
    memory and is a little lighter on the garbage generation.
    
    Also deprecated Node#traverse and updated documentation regarding that
Commits on May 29, 2012
  1. @jakewins
  2. @jakewins

    Merge pull request #564 from systay/561

    jakewins authored
    fixes #561: RELATE doesn't work as expected with map-parameters
Commits on May 28, 2012
  1. @jexp

    Merge pull request #568 from systay/567

    jexp authored
    fixes #567: Parameter maps coming through REST are not parsed correctly
  2. Improved pattern error messages

    authored
Something went wrong with that request. Please try again.