hasura / hasura/graphql-engine

Support for read-only workloads

Open
#8,358 2 comments 0 reactions 0 assignees View on GitHub
k/enhancement
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

### Problem
We are trying to build a read-only graph api over azure synapse SQL serverless.
As opposed to all CRUD operations, we want to support read-only queries on our datasets.
Currently when we add MSSQL (azure synapse SQL serverless) as a new data source, we are seeing an error that "XACT_STATE" is not supported and the data source is not added.

![MicrosoftTeams-image](https://user-images.githubusercontent.com/2607112/160447925-b4c7b37a-4267-4216-9fb7-94e4fd341199.png)

My understanding is the dependency with "XACT_STATE" on MSSQL should be with write operations. (I might be wrong here!)

### Solution
Support for read-only workloads that do not have dependency on "XACT_STATE".

Contributor guide

Open the contributing guide

Research direction

Start by tracing MSSQL data-source setup and the path that raises the XACT_STATE error for Azure Synapse SQL serverless. Compare how read-only queries are handled with CRUD operations; done means a read-only Synapse source can be added and queried without requiring XACT_STATE.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, graphql, sql
Domain
api, database
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.