Skip to content

Default Connection ignores GRAPH_EXP_FETCH_REQUEST_TIMEOUT and GRAPH_EXP_NODE_EXPANSION_LIMIT #2291

Description

@kmcginnes

Description

The configuration reference documents GRAPH_EXP_FETCH_REQUEST_TIMEOUT and GRAPH_EXP_NODE_EXPANSION_LIMIT as Default Connection settings you can pass with --env or in config.json, and uses both in its examples. Setting either one has no effect.

process-environment.sh builds defaultConnection.json from a fixed list of keys (GRAPH_EXP_CONNECTION_URL, GRAPH_EXP_GRAPH_TYPE, GRAPH_EXP_SERVICE_TYPE, GRAPH_EXP_IAM, GRAPH_EXP_AWS_REGION, and GRAPH_EXP_USING_PROXY_SERVER on the unified image) and never reads or writes these two. The client's DefaultConnectionDataSchema in packages/graph-explorer/src/core/defaultConnection.ts accepts both keys and maps them to fetchTimeoutMs and nodeExpansionLimit, but since the file never contains them, the Default Connection always falls back to the 240000 ms timeout and no expansion limit.

The docs date from #1572. The script has had the same gap since before the unified image work.

Environment

  • OS: any (Docker image)
  • Browser: any
  • Graph Explorer Version: current main
  • Graph Database & Version: any

Steps to Reproduce

  1. Run the image with --env GRAPH_CONNECTION_URL=<db> --env GRAPH_EXP_FETCH_REQUEST_TIMEOUT=10000 --env GRAPH_EXP_NODE_EXPANSION_LIMIT=50, or put the same keys in config.json.
  2. Inspect the generated defaultConnection.json in the container, or open the Default Connection in the UI.
  3. Neither value is present. The connection uses the 240000 ms default and has no expansion limit.

Expected Behavior

Either the Default Connection picks up both values from --env and config.json, or the configuration reference stops listing them.

Two ways to resolve it:

  • Have process-environment.sh read both from config.json and the environment and write them into defaultConnection.json, with a startup scenario test for each.
  • Drop both from the variable list and the two examples in docs/references/configuration.md.

Related Issues

Related: #1670 (replace the shell scripts with TypeScript), #1674 (dynamic /defaultConnection route handler)

Important

Internal only — this issue is maintained by the core team and is not accepting external contributions.

Activity

  1. added
    connectionIssues related to database connection management or options
    needs-triageMaintainer needs to evaluate
    internalSignals that the team will work on this issue internally.
    dockerPull requests that update docker code
    on Sep 28, 2026
  2. added theissue type on Sep 28, 2026
  3. self-assigned this
    on Nov 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

connectionIssues related to database connection management or optionsdockerPull requests that update docker codeinternalSignals that the team will work on this issue internally.

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions