stackql / stackql/stackql-devel

[FEATURE] Add support for server side response pruning

Open
#19 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Feature Description
Ability to identify (by provider doc configuration) and use provider specific generic parameters for column projection and row filtering, to only bring back the columns (from the SELECT column list) and rows (filtered using non required parameters in the WHERE clause) to the client.

Also allow the client side LIMIT clause to be implemented on the request if available.

Example(s)

SELECT id, name FROM google.compute.instances
WHERE name LIKE 'stackql%'
LIMIT 2;

would equate to a request with the following standard query params:

?filter=name:stackql*&fields=items(id,name)&maxResults=2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the provider documentation configuration and request handling for SELECT column projection, WHERE row filtering, and LIMIT. Use the provided google.compute.instances example to define the expected filter, fields, and maxResults parameters; done means supported providers send equivalent server-side parameters while preserving client-visible query behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.