panodata / panodata/omniload

Tiger Data

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

Nobody has claimed this yet.

connector pitch
Dominant language
Python
Stars
5
Forks
4
Avg merge
9h 49m
Merged PRs (30d)
55

Description

Pitch

Can the PostgreSQL destination be expanded to provide a Tiger Data-like querying experience by combining TimescaleDB with pg_textsearch and pgvectorscale, in a spirit that ingesting data will populate destination tables using relevant data types?

Contributor guide

No contributing guide indexed for this repository

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

No files, tests, or entry points are named. Start by locating the PostgreSQL destination and its table and data-type mapping logic, then review how TimescaleDB, pg_textsearch, and pgvectorscale could fit the existing ingestion flow. Done would mean a defined implementation that provides the requested querying experience and populates destination tables with relevant data types.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgresql, python
Domain
data-engineering, databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.