Pinot is a distributed columnar storage engine that can ingest data in real-time and serve analytical queries at low latency. There are two modes of data ingestion - batch and/or realtime. Batch mode allows users to generate pinot segments externally using systems such as Hadoop. These segments can be uploaded into Pinot via simple curl calls. Pinot can ingest data in near real-time from streaming sources such as Kafka. Data ingested into Pinot is stored in a columnar format. Pinot provides a SQL like interface (PQL) that supports filters, aggregations, and group by operations. It does not support joins by design, in order to guarantee predictable latency. It leverages other Apache projects such as Zookeeper, Kafka, and Helix, along with many libraries from the ASF.
Pinot was open sourced by LinkedIn and hosted on GitHub. Majority of the development happens at LinkedIn with other contributions from Uber and Slack. We believe that being a part of Apache Software Foundation will improve the diversity and help form a strong community around the project.
LinkedIn submits this proposal to donate the code base to Apache Software Foundation. The code is already under Apache License 2.0. Code and the documentation are hosted on Github.
LinkedIn, similar to other companies, has many applications that provide rich real-time insights to members and customers (internal and external). The workload characteristics for these applications vary a lot. Some internal applications simply need ad-hoc query capabilities with sub-second to multiple seconds latency. But external site facing applications require strong SLA even very high workloads. Prior to Pinot, LinkedIn had multiple solutions depending on the workload generated by the application and this was inefficient. Pinot was developed to be the one single platform that addresses all classes of applications. Today at LinkedIn, Pinot powers more than 50 site facing products with workload ranging from few queries per second to 1000’s of queries per second while maintaining the 99th percentile latency which can be as low as few milliseconds. All internal dashboards at LinkedIn are powered by Pinot.
We believe that requirement to develop rich real-time analytic applications is applicable to other organizations. Both Pinot and the interested communities would benefit from this work being openly available.
Pinot is currently open sourced under the Apache License Version 2.0 and available at github.com/linkedin/pinot. All the development is done using GitHub Pull Requests. We cut releases on a weekly basis and deploy it at LinkedIn. mp-0.1.468 is the latest release tag that is deployed in production.
Following the Apache meritocracy model, we intend to build an open and diverse community around Pinot. We will encourage the community to contribute to discussion and codebase.
Pinot is currently used extensively at LinkedIn and Uber. Several companies have expressed interest in the project. We hope to extend the contributor base significantly by bringing Pinot into Apache.
Pinot was started by engineers at LinkedIn, and now has committers from Uber.
Apache is the most natural home for taking Pinot forward. Pinot leverages several existing Apache Projects such as Kafka, Helix, Zookeeper, and Avro. As Pinot gains adoption, we plan to add support for the ORC and Parquet formats, as well as adding integration with Yarn and Mesos.
The risk of the Pinot project being abandoned is minimal. The teams at LinkedIn and Uber are highly incentivized to continue development of Pinot as it is a critical part of their infrastructure.
Inexperience with Open Source
Post open sourcing, Pinot was completely developed on GitHub. All the current developers on Pinot are well aware of the open source development process. However, most of the developers are new to the Apache process. Kishore Gopalakrishna, one of the lead developers in Pinot, is VP and committer of the Apache Helix project.
The current core developers are all from LinkedIn and Uber. However, we hope to establish a developer community that includes contributors from several corporations and we are actively encouraging new contributors via the mailing lists and public presentations of Pinot.
Reliance on Salaried Developers
It is expected that Pinot development will occur on both salaried time and on volunteer time, after hours. The majority of initial committers are paid by their employer to contribute to this project. However, they are all passionate about the project, and we are confident that the project will continue even if no salaried developers contribute to the project. We are committed to recruiting additional committers including non-salaried developers.
Relationships with Other Apache Products
As mentioned earlier, Pinot uses several Apache Projects such as Kafka to ingest data in real-time, Zookeeper and Helix for cluster management. Pinot also uses Maven for build and release. We foresee adding support for the Parquet and ORC formats. Adding the ability to deploy on Yarn and Mesos clusters is another interesting project we might pursue.
An Excessive Fascination with the Apache Brand
While we respect the reputation of the Apache brand and have no doubts that it will attract contributors and users, we believe ASF is the right home for Pinot to foster a great community that will lead to a better outcome in the long term.
The current Pinot codebase is hosted on Github and licensed under the Apache License V2. The source tree is self contained and relies on Maven as its build and dependency resolution mechanism.
All dependencies in Pinot have licenses that are compatible with Apache License V2, except for the org.json library, which will be removed prior to Apache incubation. The list below summarizes the external dependencies of Pinot grouped by license and ASF license category.
Dependencies from the ASF Category A
Apache License 2.0
Dual license (Apache License 2.0 + LGPL 2.1), using under the Apache License
Dependencies from the ASF Category B
Dual license (CDDL 1.1 + GPL 2 w/ CPE), using under the CDDL
Dependencies from the ASF Category X
- org.json:json:20080701 (to be removed before Apache incubation)
- pinot-private (with moderated subscriptions)
A JIRA Issue tracker (PINOT)
The existing code already has unit and integration tests and we use travis to test the patch before committing it to master. We would like to have an instance of Jenkins to achieve similar functionality.
- Kishore Gopalakrishna
- Ravi Aringunram
- Jean-François Im
- Mayank Shrivastava
- Subbu Subramaniam
- Adwait Tumbde
- Xiaotian Jiang
- Jennifer Dai
- Seunghyun Lee
- Xiang Fu
- Dhaval Patel
- Neha Pawar
- Alex Pucher
- Yen-Jung Chang
Kishore Gopalakrishna (LinkedIn)
Ravi Aringunram (LinkedIn)
Jean-François Im (LinkedIn)
Mayank Shrivastava (LinkedIn)
Subbu Subramaniam (LinkedIn)
Adwait Tumbde (LinkedIn)
Xiaotian Jiang (LinkedIn)
Jennifer Dai (LinkedIn)
Seunghyun Lee (LinkedIn)
- Xiang Fu (Uber)
- Dhaval Patel (Uber)
Neha Pawar (LinkedIn)
Alex Pucher (LinkedIn)
Yen-Jung Chang (LinkedIn)
- Marcel Siegrist
Olivier Lamy < olamy at apache dot org>
Olivier Lamy <olamy at apache dot org>
Kishore Gopalakrishna < kishoreg at apache dot org>
Jim Jagielski <jim at apache dot org>
The Apache Incubator