You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by dpitera <gi...@git.apache.org> on 2017/03/16 19:45:21 UTC
[GitHub] tinkerpop pull request #575: Dynamic graphs
GitHub user dpitera opened a pull request:
https://github.com/apache/tinkerpop/pull/575
Dynamic graphs
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dpitera/tinkerpop dynamic-graphs
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tinkerpop/pull/575.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #575
----
commit fc97a39c7306b7ab0a5ecd501780b1948e06cacc
Author: Benjamin Anderson <b...@banjiewen.net>
Date: 2016-08-20T05:33:16Z
Replace GraphManager with interface
This enabled settings-based customization of the GraphManager
implementation class, allowing implementors to customize the behavior of
the GraphManager.
commit de104b5625c1dc18687b11b505e3bc8b84e9f876
Author: dpitera <dp...@us.ibm.com>
Date: 2016-11-21T18:01:47Z
GraphManager support opening of specific graphs
This changeset allows an implementor to open a specific graph. One may
use this concept to implement a dynamic graph cache.
Furthermore, to ensure that rebindings work as intended, i.e. the list
of graphs returned to the HttpGremlinEndpointHandler, or "open graphs",
must include the to-be-rebound-graph. This changeset includes a change
to return these rebound graphs specifically.
Similar story as above for the WebSockets class, StandardOpProcessor.
Similar story for sessions, SessionOpProcessor.
Furthermore, the serializers at server boot only need to be aware of the
graphs defined in the settings object, so the relevant change here is in
AbstractChannelizer.
Furthermore:
To encourage a GraphManager implementation whose modification of the
Map<String, Graph> object aligns more closely with accepted "Getter and
Setter" design patterns, we update the adding of graphs to the
GraphManager Map by calling the new `addGraph(String, Graph)` rather
than publicly editting it with a call to `getGraphs().put(String,
Graph)`.
Also added `addTraversalSource(String, TraversalSource) for same
reasons.
Also, updated BasicGraphManager according to the new specifications.
commit c447dc3b8ffaf3a550f7344e1537cbcdd0056231
Author: dpitera <dp...@us.ibm.com>
Date: 2017-03-15T19:31:45Z
Allow for custom graph instantiations/closings
This allows an implementor to supply a custom openGraph function to
return a newly instantiated graph object, and similarly do the same to
close a graph object, while doing so through the graphManager for
reference tracking.
commit 08ca7bf6a9d188b92e8bb0e5d6900e039d68fae0
Author: dpitera <dp...@us.ibm.com>
Date: 2017-03-15T19:34:09Z
Update docs acc. to GraphManager changes
commit b2685174db88bd48cbf1899cd0f3cd4ec796266c
Author: dpitera <dp...@us.ibm.com>
Date: 2017-03-16T15:32:47Z
Update code according to PR comments/suggestions
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] tinkerpop pull request #575: Dynamic graphs
Posted by dpitera <gi...@git.apache.org>.
Github user dpitera closed the pull request at:
https://github.com/apache/tinkerpop/pull/575
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---