Skip to content

About us

Apache Pinot is a realtime distributed OLAP datastore, which is used to deliver scalable real time analytics with low latency. It can ingest data from batch data sources (S3, HDFS, Azure Data Lake, Google Cloud Storage) as well as streaming sources (such as Kafka). Pinot is used extensively at LinkedIn and Uber to power many analytical applications such as Who Viewed My Profile, Ad Analytics, Talent Analytics, Uber Eats and many more serving 100k+ queries per second while ingesting 1Million+ events per second.

Pinot committers are active on slack. Click here to join our slack channel.
This meetup is for developers and users of Apache Pinot to share information on
• How to use Pinot 
• Internals of Pinot 
• Products built on top of Pinot

More info on Pinot
Apache Pinot Website

Apache Pinot Docs 
Blog posts

> • https://engineering.linkedin.com/blog/2019/03/pinot-joins-apache-incubator
> • https://engineering.linkedin.com/blog/2019/06/star-tree-index--powering-fast-aggregations-on-pinot
>
> • https://engineering.linkedin.com/blog/2019/auto-tuning-pinot
>
> • Pinot at Uber

Upcoming events

1

See all
  • Network event
    Beyond the Forklift: Unlocking Revenue-Critical Workloads on Iceberg

    Beyond the Forklift: Unlocking Revenue-Critical Workloads on Iceberg

    ·
    Online
    Online
    17 attendees from 10 groups

    To attend, register here.

    Apache Iceberg has become the open standard for modern data platforms, yet most adoptions approach migration as a forklift. Governance improves, storage is standardized, and BI workloads run reliably; but the most demanding analytics, the ones closest to revenue and customer experience, are rarely considered in scope for Iceberg.

    Those SLA-bound data products—embedded dashboards, fintech merchant cash flow views, surge pricing, fraud detection, incident response—don’t simply go away when Iceberg isn’t built to serve them. If the platform isn’t engineered for deterministic p95/p99 latency and high-concurrency guarantees, the requirement resurfaces elsewhere. What was intended to be a shared system of record becomes relegated to a feeder layer, pushing data into downstream systems where it is re-stored, re-governed, and re-queried outside of Iceberg.

    This session outlines a different model: Iceberg as the open system of record, paired with a purpose-built execution layer that enforces deterministic SLAs directly on Iceberg tables, eliminating shadow stacks and restoring architectural coherence for revenue-critical insights.

    • Photo of the user
    • Photo of the user
    • Photo of the user
    3 attendees from this group

Group links

Organizers

Members

2,047
See all
Photo of the user Kishore Gopalakrishna
Photo of the user Foo Lim
Photo of the user Hiren
Photo of the user Vardan Aroustamian
Photo of the user Gerald Wluka
Photo of the user K e l v i n
Photo of the user Randy Breunling
Photo of the user Sriram Baskaran
Photo of the user AKulkarni
Photo of the user Victor Chugunov
Photo of the user Alex Kin
Photo of the user Mark Chekhanovskiy

Find us also at