Skip to content

Refactor server error handling #105

@zhulik

Description

@zhulik

# Neptune presumably returns message as a JSON string of format
# {"detailedMessage":"",
# "requestId":"UUID",
# "code":"ConcurrentModificationException"}
# Currencly we simply search for substings to identify the exact error
# TODO: parse json and use `code` instead
VERTEX_ALREADY_EXISTS = "Vertex with id already exists:"
EDGE_ALREADY_EXISTS = "Edge with id already exists:"
CONCURRENT_VERTEX_INSERT_FAILED = "Failed to complete Insert operation for a Vertex due to conflicting concurrent"
CONCURRENT_EDGE_INSERT_FAILED = "Failed to complete Insert operation for an Edge due to conflicting concurrent"
CONCURRENCT_MODIFICATION_FAILED = "Failed to complete operation due to conflicting concurrent"

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions