Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
branch: shell-let
Commits on May 31, 2012
  1. intermediate

    authored
Commits on May 30, 2012
  1. @tinwelint

    Fixed a headline level issue

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

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

    Merge pull request #574 from systay/type_problems

    jexp authored
    fixes #573: Arithmetics operations have wrong type
  4. @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

    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
Commits on May 24, 2012
  1. Updated change logs

    authored
Commits on May 23, 2012
  1. @digitalstain
  2. @tinwelint

    Fixes issue #554 : Read-only shell server mode would fail commands wi…

    tinwelint authored
    …th classcast exception for AbstractGraphDatabase, solved by casting to GraphDatabaseAPI and have the read-only graphdatabase proxy class implement GraphDatabaseAPI
  3. @digitalstain

    Revert "Added a new kind of cache, a ClockCache that tries to mimic a…

    digitalstain authored
    …n LRU but with less synchronization."
    
    This reverts commit 31a3cc8.
    
    Broke bigger tests, have to revisit
  4. @digitalstain

    Updated changelogs

    digitalstain authored
  5. @jakewins

    Merge pull request #552 from systay/shell-transactions

    jakewins authored
    Transactions are suspended/resumed instead of hanging of the thread
  6. @nawroth

    Merge pull request #550 from peterneubauer/docs-formatting

    nawroth authored
    Formatting and docs without any classloader changes which broke the build
  7. Transactions are suspended/resumed instead of hanging of the thread

    authored
    Historically, shell commands did not start or close transactions. Every command
    was supposed to leave the shell in a clean state. To support having open
    transactions in the shell, the shell now does the housekeeping of transactions.
    Before commands get to run, transactions are resumed in, and after they have
    finished, transactions are suspended (removed from the thread).
  8. @peterneubauer

    adding changes

    peterneubauer authored
  9. @tinwelint

    Merge pull request #548 from digitalstain/nonblocking-index

    tinwelint authored
    Re-issued the previous PR (#539) since it was rightfully rejected
  10. @tinwelint

    Changes update for 9dcb6fd

    tinwelint authored
  11. @peterneubauer

    adjusting changes.txt

    peterneubauer authored
  12. @tinwelint

    --Third attempt, original attempt a1be819

    tinwelint authored
    --broke the build and got reverted by 014246e.
    
    Sessions now live on the server, which means it can hold any type of
    objects, not just Serializables. Needed for coming features, such as
    holding results from cypher queries.
    
    One drawback of this is that a clients session variables will be lost on
    reconnect to the server, however initial session variables (i.e. given
    when starting the client) will be re-set in the new session after a
    reconnect.
    
    Reverted to trying to find server connection in remote client constructor
    
    Bla
  13. @tinwelint

    Revert " --Second attempt, previous attempt a1be819"

    tinwelint authored
    My bad, hang on for next attempt.
    
    This reverts commit 49a6da5.
  14. @tinwelint

    --Second attempt, previous attempt a1be819

    tinwelint authored
     --broke the build and got reverted by
     --014246e540f65e1c0a5aede6245dff5fcd4cab10.
    
    Sessions now live on the server, which means it can hold any type of
    objects, not just Serializables. Needed for coming features, such as
    holding results from cypher queries.
    
    One drawback of this is that a clients session variables will be lost on
    reconnect to the server, however initial session variables (i.e. given
    when starting the client) will be re-set in the new session after a
    reconnect.
  15. @peterneubauer
  16. Broke the build.

    authored
    Revert "Sessions now live on the server, which means it can hold any type of"
    
    This reverts commit a1be819.
  17. Merge pull request #549 from tinwelint/server-side-shell-session

    authored
    Sessions now live on the server, which means it can hold any type of
  18. @tinwelint

    Sessions now live on the server, which means it can hold any type of

    tinwelint authored
    objects, not just Serializables. Needed for coming features, such as
    holding results from cypher queries.
    
    One drawback of this is that a clients session variables will be lost on
    reconnect to the server, however initial session variables (i.e. given
    when starting the client) will be re-set in the new session after a
    reconnect.
  19. @jimwebber

    merging

    jimwebber authored
  20. @jimwebber

    Fixed the doc bugs

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