hasura / hasura/graphql-engine

Subscription Execution Time Depending on Parameter Position

Open
#9,666 6 comments 0 reactions 0 assignees View on GitHub
k/bug
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

### Version Information

Server Version: `v2.4.0`
Database - PostgreSQL

### Environment
- In House ( AWS EC2 with Docker )

### What is the current behaviour?
Subscription is Taking a long time to execute a query while it's running fast when the position of some parameter in the query was exchanged, I am running Hasura on an EC2 Instance with Docker Container, I have tried deleting and recreating the Docker container thinking it can be an issue with the cache, but it's still showing the same issue.

### What is the expected behaviour?
Subscription Execution Time should not be dependent on How i place my parameters.

### Screenshots or Screencast

https://github.com/hasura/graphql-engine/assets/52407451/ceb6139a-a38b-4340-b5d4-87c9c6e58e10

### Keywords
- Subscription

Contributor guide

Open the contributing guide

Research direction

The issue provides no source file, test, query, or reproducible parameter set. Start by reproducing the subscription against PostgreSQL while changing only parameter order, then identify the execution path responsible and define done as equivalent execution time regardless of parameter position.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, postgresql
Domain
api, backend, cloud, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.