Routing context in URI #346
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lutovich
force-pushed
the
1.3-routing-ctx-uri
branch
from
93ec4cf to
8caedd8
Compare
lutovich
force-pushed
the
1.3-routing-ctx-uri
branch
from
8caedd8 to
8b15e13
Compare
Routing context is a map of string key-value pairs. It is send to the database when calling `dbms.cluster.routing.getRoutingTable` procedure as it's single argument. This is only supported by 3.2+ servers. Previously routing context was defined on the config. It is problematic because routing context in `bolt+routing` specific and thus makes no sense for single instance database. This commit makes routing context part of the `bolt+routing` URI. It lives in the query part of the URI as regular query parameters like: `bolt+routing://localhost:7687/?policy=my_policy®ion=china`. Clustering-specific configuration method is removed.
lutovich
force-pushed
the
1.3-routing-ctx-uri
branch
from
8b15e13 to
559db5a
Compare
|
LG, merging |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Routing context is a map of string key-value pairs. It is send to the database when calling
dbms.cluster.routing.getRoutingTableprocedure as it's single argument. This is only supported by 3.2+ servers.Previously routing context was defined on the config. It is problematic because routing context in
bolt+routingspecific and thus makes no sense for single instance database.This PR makes routing context part of the
bolt+routingURI. It lives in the query part of the URI as regular query parameters like:bolt+routing://localhost:7687/?policy=my_policy®ion=china.Clustering-specific configuration method is removed.