generated from amazon-archives/__template_Apache-2.0
    
        
        - 
                Notifications
    
You must be signed in to change notification settings  - Fork 67
 
Open
Labels
connectionIssues related to database connection management or optionsIssues related to database connection management or options
Milestone
Description
Goals
- Allow user to override the assumed sparql path (hard coded to 
/sparqlcurrently) - Constrain options based on database provider
 - Clarify difference between Graph Explorer options and database specific options
 
Prototype
I propose introducing "Connection Type" as a new setting in connections. This allows us to tailor the UI to the specific database provider/type.
| Neptune DB | Neptune Analytics | Generic Gremlin | Generic SPARQL | 
|---|---|---|---|
![]()  | 
![]()  | 
![]()  | 
![]()  | 
Breakdown
Here we breakdown each section of the new connections UI with a description of what changed and why.
- Existing connections will default to Neptune DB (or Neptune Analytics if the service type is 
neptune-graph)- This will ensure compatibility with existing behavior
 
 - The IAM service type option goes away since it can be inferred from connection type
 - Neptune Analytics can only be openCypher
 - Neptune DB and Analytics will only require the base URL for the instance, the 
/sparql,/gremlin,/opencypherwill continue to be added automatically - Generic Gremlin and Generic SPARQL require the full URL for the database endpoint
 - Generic Gremlin and Generic SPARQL do not allow IAM auth to be configured
 - There is no "generic openCypher" because Graph Explorer only works with Neptune's flavor of openCypher
- Other providers have incompatible request and response shapes
 
 - Minimal changes to the logic behind the connection, mostly just UI changes
 
Metadata
Metadata
Assignees
Labels
connectionIssues related to database connection management or optionsIssues related to database connection management or options









