apache / apache/pinot

Pinot Long Term Data Store

Open
#7,229 42 comments 3 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
6.1k
Forks
1.5k
Avg merge
1d 21h
Merged PRs (30d)
189

Description

We have certain use-cases wherein we would like to move older data to cheap object stores like the S3 and store only the most recent data in Pinot. One such use-case is storing distributed trace data - Our query patterns show that more than 90% of the queries lie in the last 24 hours. Having said that, we have a retention period of 30 days. So in this case, we would like to keep only the last 24 hours worth of data in Pinot, and move the rest to a cheap store like the S3.

From what I concluded from our initial discussions, this would involve work on two fronts:

1. Moving older data from Pinot to the S3 (this already happens, mentioning it for completeness).
2. Pinot-Presto connector, so that it can query from both Pinot and the S3 based on the time span of the query.

Here is a rough sketch of the design we came up with in our discussion the other day (this is relevant to the distributed tracing example I gave above):

![Screenshot 2021-07-25 at 7 13 21 PM](https://user-images.githubusercontent.com/84911643/127535064-3d017d81-9d04-47a0-8a8a-ded9c29a1b22.png)

I have created this issue to get the discussion started.

Thanks!

Contributor guide

Open the contributing guide

Research direction

No files or tests are named. Start by reviewing the Pinot-Presto connector and the existing S3 data-movement path, then clarify how queries should combine recent Pinot data with older S3 data; done requires an agreed design and implementation scope.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, java
Domain
cloud, data-engineering, databases, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.