Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Proof of concept for SQL --> timescale consumer queries #696

Draft
wants to merge 1 commit into
base: beta
Choose a base branch
from

Conversation

jpmcb
Copy link
Member

@jpmcb jpmcb commented Mar 30, 2024

Description

This is a proof of concept, skunkworks project to show how we might offer a high level, enterprise offering with direct access to our timescale / time series data off GitHub

cc @bdougie

Note: there is alot of work to do real validation of queries. This would currently be open to all kinds of sql injection attacks.

What type of PR is this? (check all applicable)

  • πŸ• Feature
  • πŸ› Bug Fix
  • πŸ“ Documentation Update
  • 🎨 Style
  • πŸ§‘β€πŸ’» Code Refactor
  • πŸ”₯ Performance Improvements
  • βœ… Test
  • πŸ€– Build
  • πŸ” CI
  • πŸ“¦ Chore (Release)
  • ⏩ Revert

Related Tickets & Documents

N/a

Mobile & Desktop Screenshots/Recordings

Given a query in the API like:

Screenshot 2024-03-29 at 6 17 49 PM

This returns a list of data from the api like:

Screenshot 2024-03-29 at 6 18 32 PM

Steps to QA

Tier (staff will fill in)

  • Tier 1
  • Tier 2
  • Tier 3
  • Tier 4

[optional] Are there any post-deployment tasks we need to perform?

This is only a proof of concept. But gets the idea across. We'd want to guard this from public access while we iterate on it or drop it as one big feature.

[optional] What gif best describes this PR or how it makes you feel?

@jpmcb jpmcb requested a review from bdougie March 30, 2024 00:19
@jpmcb jpmcb marked this pull request as draft March 30, 2024 00:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant