The next Presto TSC meeting will be next week, April 12^th at 9am Pacific/12pm Eastern time.

TSC meetings are open to the entire technical community, and are meant to be a forum to discuss technical direction, community concerns, and bring up new ideas.

If you’d like to bring up a topic for the TSC, please send a PR to the agenda here: https://github.com/prestodb/tsc/blob/master/meetings/2022-04-12.md

Tim

Hey folks, there were no agenda items today, so cancelling today’s meeting.  See you next month.

Tim

 The next Presto TSC meeting will be next week, Mar 8^nd at 9am Pacific/12pm Eastern time.

TSC meetings are open to the entire technical community, and are meant to be a forum to discuss technical direction, community concerns, and bring up new ideas.

If you’d like to bring up a topic for the TSC, please send a PR to the agenda here: https://github.com/prestodb/tsc/blob/master/meetings/2022-03-08.md

Tim

 The next Presto TSC meeting will be next week, Mar 8^nd at 9am Pacific/12pm Eastern time.

TSC meetings are open to the entire technical community, and are meant to be a forum to discuss technical direction, community concerns, and bring up new ideas.

If you’d like to bring up a topic for the TSC, please send a PR to the agenda here: https://github.com/prestodb/tsc/blob/master/meetings/2022-03-08.md

Tim

Hello all,

The election has concluded, and the new TSC consists of:

• Bin Fan
• James Sun
• Rebecca Schlussel
• Rongrong Zhong
• Tim Meehan
• Ying Su
• Zhenxiao Luo

Thanks everyone for submitting your nominations and participating in this election.

For this initial class, some term limits last until November of next year, and some extend until May of the following year.  We’ll determine who belongs to which term by random coin toss at our next TSC meeting, after which it will be added to the charter.

Thank you

Tim

Hello all,

Tl;dr: we’re now accepting nominations for the next TSC class.  Please see the TSC README to see instructions on how you can submit a nomination to the TSC.

To begin with, I wanted to make an announcement that tsc#68 has been merged.  Just to summarize, the main changes to the TSC were:

1. Most votes become lazy consensus votes.
2. New committers now are voted in by TSC members, not the broad set of committers.
3. TSC members now have term limits, with elections occurring every half year for roughly half the TSC.
4. The new TSC group will consist of a smaller pool of individuals (7, rather than the current group of 15).

The idea behind these changes were to reduce friction points from participation among committers and TSC members, namely: removing the high burden of voting required to vote in new committers, allowing for lazy consensus for most votes, and reducing the TSC size to make it a smaller, focused and more agile group.

With these changes being accepted and merged, the time has now come to vote in our next set of TSC members.

The process will work as follows:

1. Today, we start accepting nominations for TSC membership.  By current rules, TSC members must be committers.  The instructions are found on the README for the TSC, and have also been linked on the README for the main project.
2. Nominations close on Thursday, November 4^th, after which we’ll begin the process of voting via OpaVote.
3. Voting closes on Thursday, November 11^th, at which point we’ll have our new TSC class.

For details, please see the README above, and the TSC charter.

I’m looking forward for the upcoming TSC to help guide the technical project.

Tim

Hello all,

Tl;dr: we’re now accepting nominations for the next TSC class.  Please see the TSC README to see instructions on how you can submit a nomination to the TSC.

To begin with, I wanted to make an announcement that tsc#68 has been merged.  Just to summarize, the main changes to the TSC were:

1. Most votes become lazy consensus votes.
2. New committers now are voted in by TSC members, not the broad set of committers.
3. TSC members now have term limits, with elections occurring every half year for roughly half the TSC.
4. The new TSC group will consist of a smaller pool of individuals (7, rather than the current group of 15).

The idea behind these changes were to reduce friction points from participation among committers and TSC members, namely: removing the high burden of voting required to vote in new committers, allowing for lazy consensus for most votes, and reducing the TSC size to make it a smaller, focused and more agile group.

With these changes being accepted and merged, the time has now come to vote in our next set of TSC members.

The process will work as follows:

1. Today, we start accepting nominations for TSC membership.  By current rules, TSC members must be committers.  The instructions are found on the README for the TSC, and have also been linked on the README for the main project.
2. Nominations close on Thursday, November 4^th, after which we’ll begin the process of voting via OpaVote.
3. Voting closes on Thursday, November 11^th, at which point we’ll have our new TSC class.

For details, please see the README above, and the TSC charter.

I’m looking forward for the upcoming TSC to help guide the technical project.

Tim

Thanks for all the votes! We have reached the majority of the consensus now (9 affirmative ones out of 17 committers). Congrats @Arun Thirupathi on becoming a committer!

Thanks

James

Who is franchised to vote for committers

+1

Hi Presto committers,

I would like to nominate Arun Thirupathi (github ID: arunthirupathi) as a Presto committer. Arun has been contributing a lot to the Presto ORC reader and writer. He is now one of the few experts in the Presto community having a deep grasp of file formats.

In Presto, Arun worked extensively on ORC support and is an expert in the columnar file formats. Arun also worked on Presto core and has contributed to multiple modules in Presto. Arun improves the code by constant refactoring, adding additional tests and improving the documentation of Presto. Arun has reviewed most changes to the columnar file format. Arun has reviewed changes from different contributors and provides quality feedback.

In addition, Arun is not new to open source. Arun was an active member of Voldemort, a distributed key/value store that was once popular.

In details, Arun has

• 48 commits
• 10K lines of addition and 4K lines of removal
• 30+ PR reviews and 140+ review comments

The major contributions include:

1. Rewrote the ORC dictionary writer to improve performance by 3X.
2. Improve the performance of queries that use Map functions like MAP_AGG, ELEMENT_AT by introducing lazy hash tables in Presto.
3. Improved the IO performance of Presto ORC reader and writer by introducing new layouts, configurable tail sizes.
4. Optimized the dictionary writer performance by using chunked memory, optimized data structure.
5. Fixed multiple bugs in presto-orc like support for stripes with 2 billion rows, IO errors are masked, Hive filter pushdown bugs.
6. Improved columnar statistics memory efficiency.
7. Simplified the presto-orc code by constant refactoring.
8. Maintaining/Upgrading dependency of presto like orc-protobuf, fastutil, hive-apache

Please reply to this email to vote.

Thanks

James

+1

Hi Presto committers,

I would like to nominate Arun Thirupathi (github ID: arunthirupathi) as a Presto committer. Arun has been contributing a lot to the Presto ORC reader and writer. He is now one of the few experts in the Presto community having a deep grasp of file formats.

In Presto, Arun worked extensively on ORC support and is an expert in the columnar file formats. Arun also worked on Presto core and has contributed to multiple modules in Presto. Arun improves the code by constant refactoring, adding additional tests and improving the documentation of Presto. Arun has reviewed most changes to the columnar file format. Arun has reviewed changes from different contributors and provides quality feedback.

In addition, Arun is not new to open source. Arun was an active member of Voldemort, a distributed key/value store that was once popular.

In details, Arun has

• 48 commits
• 10K lines of addition and 4K lines of removal
• 30+ PR reviews and 140+ review comments

The major contributions include:

1. Rewrote the ORC dictionary writer to improve performance by 3X.
2. Improve the performance of queries that use Map functions like MAP_AGG, ELEMENT_AT by introducing lazy hash tables in Presto.
3. Improved the IO performance of Presto ORC reader and writer by introducing new layouts, configurable tail sizes.
4. Optimized the dictionary writer performance by using chunked memory, optimized data structure.
5. Fixed multiple bugs in presto-orc like support for stripes with 2 billion rows, IO errors are masked, Hive filter pushdown bugs.
6. Improved columnar statistics memory efficiency.
7. Simplified the presto-orc code by constant refactoring.
8. Maintaining/Upgrading dependency of presto like orc-protobuf, fastutil, hive-apache

Please reply to this email to vote.

Thanks

James

Hi Presto committers,

I would like to nominate Arun Thirupathi (github ID: arunthirupathi) as a Presto committer. Arun has been contributing a lot to the Presto ORC reader and writer. He is now one of the few experts in the Presto community having a deep grasp of file formats.

In Presto, Arun worked extensively on ORC support and is an expert in the columnar file formats. Arun also worked on Presto core and has contributed to multiple modules in Presto. Arun improves the code by constant refactoring, adding additional tests and improving the documentation of Presto. Arun has reviewed most changes to the columnar file format. Arun has reviewed changes from different contributors and provides quality feedback.

In addition, Arun is not new to open source. Arun was an active member of Voldemort, a distributed key/value store that was once popular.

In details, Arun has

• 48 commits
• 10K lines of addition and 4K lines of removal
• 30+ PR reviews and 140+ review comments

The major contributions include:

1. Rewrote the ORC dictionary writer to improve performance by 3X.
2. Improve the performance of queries that use Map functions like MAP_AGG, ELEMENT_AT by introducing lazy hash tables in Presto.
3. Improved the IO performance of Presto ORC reader and writer by introducing new layouts, configurable tail sizes.
4. Optimized the dictionary writer performance by using chunked memory, optimized data structure.
5. Fixed multiple bugs in presto-orc like support for stripes with 2 billion rows, IO errors are masked, Hive filter pushdown bugs.
6. Improved columnar statistics memory efficiency.
7. Simplified the presto-orc code by constant refactoring.
8. Maintaining/Upgrading dependency of presto like orc-protobuf, fastutil, hive-apache

Please reply to this email to vote.

Thanks

James

The next Presto TSC meeting will be tomorrow, October 5^th at 9am Pacifc/12pm Eastern time.

TSC meetings are open to the entire technical community, and are meant to be a forum to discuss technical direction, community concerns, and bring up new ideas.

If you’d like to bring up a topic for the TSC, please send a PR to the agenda here: https://github.com/prestodb/tsc/blob/master/meetings/2021-10-05.md

Tim