Re: Apache pinot release 1.0.0 RC3 voting

[Seunghyun Lee]

   - Verified the signature
   - Verified hashes are the same
   - Verified that NOTICE/BINARY files exists
   - Verified that the binary release run without an issue
   - Verified that the source release was successfully built and I ran the
   quick start scripts.


+1 on the release. Thank you!

On Tue, Sep 12, 2023 at 3:03 AM saurabh dubey  wrote:

> Hi Pinot Community,
>
> This is a call for a vote to release Apache Pinot 1.0.0
>
> The release candidate:
> https://dist.apache.org/repos/dist/dev/pinot/apache-pinot-1.0.0-rc3/
>
> Git tag for this release:
> https://github.com/apache/pinot/tree/release-1.0.0-rc
>
> Git hash for this release:
> b297245f1c63245fc6023447b7d726f1adf16141
>
> The artifacts have been signed with key: F8ADC9FFC02081CB, which can be
> found in
> the following KEYS file.
> https://dist.apache.org/repos/dist/release/pinot/KEYS
>
> Release notes:
> https://github.com/apache/pinot/releases/tag/release-1.0.0-rc3
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachepinot-1056/
>
> Documentation on verifying a release candidate:
>
> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
>
> The vote will be open for at least 72 hours or until a necessary number of
> votes is reached.
>
> Please vote accordingly,
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> Apache Pinot team
>

CVE-2022-26112: Apache Pinot: Pinot query endpoint and the realtime ingestion layer has a vulnerability in unprotected environments due to a groovy function support

[Seunghyun Lee]

Description:

In 0.10.0 or older versions of Apache Pinot, Pinot query endpoint and
realtime ingestion layer has a vulnerability in unprotected environments
due to a groovy function support. In order to avoid this, we disabled the
groovy function support by default from Pinot release 0.11.0.

See https://docs.pinot.apache.org/basics/releases/0.11.0

Credit:

Apache Pinot would like to thank Haoruo Chen(chenhaoruo0...@gmail.com) for
reporting the issue


-
To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
For additional commands, e-mail: dev-h...@pinot.apache.org

Re: Apache Pinot™ Slack Workspace Rename

[Seunghyun Lee]

We should definitely recognize Startree's contribution to expanding the
Pinot community; however, it would have been nicer if we saw some
discussion happening within the community before this decision has been
made. As I mentioned in the above reply, the current Apache Pinot workspace
was created as part of the project incubation process when the code was
donated to the Apache Software Foundation from LinkedIn so I have thought
that the Pinot community has owned the workspace.

To move forward, I think that we should discuss and come up with the
migration plan before this renaming takes place. I briefly looked into the
ASF workspace (https://infra.apache.org/slack.html) and it looks that only
ppl with "@apache.org" email (committer, PMCs) will get the full access.
Apache Pinot community members who are not committers/PMCs will have issues
with joining discussion channels. Although there is a way to invite "single
channel guests" per-channel basis, I don't think that it's sufficient for
the existing use case of our Apache Pinot workspace.

Best,
Seunghyun

On Thu, May 26, 2022 at 6:04 PM Subbu Subramaniam
 wrote:

>
> [I am on vacation, so I just saw this thread]
>
> Thanks for conveying your intentions, Tim. I see that others in the
> community have weighed in as well, so the good thing is that our decision
> will be based on what the community agrees to.
>
> As others have pointed out, we must certainly acknowledge the work done by
> Startree in terms of building the community strength around pinot. Last I
> saw, there were around 2000 members in slack. In terms of community
> strength, therefore, the count is distributed across (perhaps) 100s of
> vendors and individual contributors.
>
> It seems to me that to take an action like this with just a few days
> notice is not the best.
>
> Definitey, +1 to having separate spaces for Startree customers and Apache
> pinot. How this should happen is TBD
>
> Thanks
>
>
> -Subbu
>  Pinot PMC
> --
> *From:* Tim Berglund 
> *Sent:* Wednesday, May 25, 2022 11:55 AM
> *To:* dev@pinot.apache.org 
> *Subject:* Apache Pinot™ Slack Workspace Rename
>
>
> Pinot Dev,
>
> I’m Tim Berglund. The barest intro of me: I run Developer Relations at
> StarTree. I wanted to go over a change I’m making to our Slack workspace so
> it is not a surprise to you and we have a chance to talk through any
> questions.
>
> On June 1, 2022, we will rename the Apache Pinot™ Slack Workspace to the
> StarTree Community Slack Workspace. Let me explain my thinking here.
>
> First, of the top ten lifetime contributors in this Slack, six are
> StarTree employees, accounting for about 80% of messages. I’m concerned by
> the StarTree-heavy presence in a workspace that borrows the Apache
> branding. It made sense to name the workspace “Apache Pinot” when Kishore
> first made it, but as its usage has evolved and will continue to evolve,
> keeping the Apache name is not appropriate. StarTree is committed to making
> Pinot famous—that’s my actual job, in fact—and to helping users of the
> open-source project be successful with it, but we need to keep the
> boundaries between the ASF and StarTree clearly defined. Renaming this
> Slack is an important part of that distinction, and something I’d rather do
> sooner than later.
>
> Second, the continued evolution of the workspace is sure to include
> channels to support StarTree’s cloud service and other community-licensed
> products we might release in the future. Our broad commitment to and
> investment in the support and advocacy for Apache Pinot will remain.
> Renaming of the Slack will not cause it to become a place for vendor sales
> pitches. (Indeed, those are forbidden, and sales people who come into Slack
> to sell will answer to me.)
>
> The Slack is home to many other community members who have no association
> with the ASF at all, and of course will continue to be an inclusive space
> open to anyone who wants to talk about Pinot. It’s our goal for it to
> continue to grow and thrive, and for StarTree to continue to invest heavily
> in it as a helpful and welcoming place.
>
> Warmly,
>
> Tim Berglund
>
> VP Developer Relations
> StarTree
>

Re: Apache Pinot™ Slack Workspace Rename

[Seunghyun Lee]

I also definitely agree that Startree has put a tremendous effort to grow
the ASF Pinot community slack channel and helping people for
troubleshooting/debug the issue.

On the other hand, the community slack channel was created as part of the
Apache incubation process and this workspace has always been regarded as
one of the community growth metrics for ASF Pinot.

As Sidd mentioned, a lot of ASF Pinot-related discussions are happening in
the slack channel (e.g. contributor/committer/pmc discussions, cross org
collaboration on the features etc). From what Tim is highlighting, I think
that maybe it is better to keep a separate workspace: one for Startree
customers and the other for only ASF Pinot users and contributors.

Best,
Seunghyun




On Wed, May 25, 2022 at 2:00 PM siddharth teotia 
wrote:

> Hi Tim,
>
> Thank you for sharing this.
>
> > StarTree is committed to making Pinot famous—that’s my actual job, in
> fact—and to helping users of the open-source project be successful with it,
> but we need to keep the boundaries between the ASF and StarTree clearly
> defined. Renaming this Slack is an important part of that distinction
>
> I understand where you are coming from and why you may want to keep
> distinction between ASF Pinot and Startree. However, I am not quite sure
> how renaming this is going to help with distinction because then all the
> ASF Pinot related conversations (between contributors / committers / PMCs
> for release, PR, issue etc discussion) will have to go through Startree
> workspace which may not be the correct place to do so because these
> discussions are orthogonal to Startree or any company using / contributing
> to ASF Pinot.
>
> This workspace was initially created to help grow the ASF Pinot community
> and have the related discussions there. I completely agree that Startree
> has done a great job in bringing more folks to the workspace, helping them
> on a day to day basis etc. However, renaming will actually blur the
> distinction to be honest.
>
> Shall we discuss this to see if there is any alternative to achieve this
> distinction ?
>
> Thanks
> Sidd
>
>
>
>
>
> On Wed, May 25, 2022 at 11:56 AM Tim Berglund 
> wrote:
>
>> Pinot Dev,
>>
>> I’m Tim Berglund. The barest intro of me: I run Developer Relations at
>> StarTree. I wanted to go over a change I’m making to our Slack workspace so
>> it is not a surprise to you and we have a chance to talk through any
>> questions.
>>
>> On June 1, 2022, we will rename the Apache Pinot™ Slack Workspace to the
>> StarTree Community Slack Workspace. Let me explain my thinking here.
>>
>> First, of the top ten lifetime contributors in this Slack, six are
>> StarTree employees, accounting for about 80% of messages. I’m concerned by
>> the StarTree-heavy presence in a workspace that borrows the Apache
>> branding. It made sense to name the workspace “Apache Pinot” when Kishore
>> first made it, but as its usage has evolved and will continue to evolve,
>> keeping the Apache name is not appropriate. StarTree is committed to making
>> Pinot famous—that’s my actual job, in fact—and to helping users of the
>> open-source project be successful with it, but we need to keep the
>> boundaries between the ASF and StarTree clearly defined. Renaming this
>> Slack is an important part of that distinction, and something I’d rather do
>> sooner than later.
>>
>> Second, the continued evolution of the workspace is sure to include
>> channels to support StarTree’s cloud service and other community-licensed
>> products we might release in the future. Our broad commitment to and
>> investment in the support and advocacy for Apache Pinot will remain.
>> Renaming of the Slack will not cause it to become a place for vendor sales
>> pitches. (Indeed, those are forbidden, and sales people who come into Slack
>> to sell will answer to me.)
>>
>> The Slack is home to many other community members who have no association
>> with the ASF at all, and of course will continue to be an inclusive space
>> open to anyone who wants to talk about Pinot. It’s our goal for it to
>> continue to grow and thrive, and for StarTree to continue to invest heavily
>> in it as a helpful and welcoming place.
>>
>> Warmly,
>>
>> Tim Berglund
>>
>> VP Developer Relations
>> StarTree
>>
>

Re: [VOTE] Apache Pinot 0.9.1 RC0

[Seunghyun Lee]

+1 (binding)

- verified sha512 hash
- verified signature
- verified git hash
- verified contents based on git commit hash & the downloaded source code
- verified LICENSE, NOTICE are correctly present
- ran quick start scripts

On Sun, Dec 12, 2021 at 5:00 PM Mayank Shrivastava 
wrote:

> +1 [binding]
>
> Verified build and quick-start.
>
> On Sat, Dec 11, 2021 at 10:29 PM Xiang Fu  wrote:
>
>> Hi Pinot Community,
>>
>> This is a call for a vote to release Apache Pinot 0.9.1.
>>
>> This release fixes the major issue of CVE-2021-44228
>>  and a major bug
>> fixing of pinot admin exit code issue
>> .
>>
>> The release candidate:
>> https://dist.apache.org/repos/dist/dev/pinot/apache-pinot-0.9.1-rc0
>>
>> Git tag for this release:
>> https://github.com/apache/pinot/tree/release-0.9.1-rc0
>>
>> Git hash for this release:
>> f8ec6f6f8eead03488d3f4d0b9501fc3c4232961
>>
>> The artifacts have been signed with the key: CDEDB21B862F6C66, which can
>> be found in the following KEYS file.
>> https://dist.apache.org/repos/dist/release/pinot/KEYS
>>
>> Release notes:
>> https://github.com/apache/pinot/releases/tag/release-0.9.1-rc0
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachepinot-1032
>>
>> Documentation on verifying a release candidate:
>>
>> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
>>
>> The vote will be open for at least 72 hours or until a necessary number
>> of votes is reached.
>>
>> Please vote accordingly,
>>
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove with the reason
>>
>> Thanks,
>> Apache Pinot team
>>
>

Re: [VOTE] Apache Pinot 0.9.0 RC0

[Seunghyun Lee]

+1

I have checked the following:

- Checked that signature/hash is correct
- Verified that Git hash is matching (compared the src release & hash
provided in the mail)
- LICENSE/BINARY file presents to both binary/src release
- Compiled and ran the Quick Demo on both Linux/MacOS using JDK 11





On Tue, Nov 16, 2021 at 3:25 PM Neha Pawar  wrote:

> +1
>
> Verified and lgtm
>
> Thanks,
> Neha Pawar
>
> 
>
>
> On Tue, Nov 16, 2021 at 12:44 PM Mayank Shrivastava 
> wrote:
>
>> +1 [binding]
>>
>> Verified using instructions at:
>> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
>>
>> Cheers,
>> Mayank
>>
>> On Fri, Nov 12, 2021 at 10:32 PM Xiang Fu  wrote:
>>
>>> Hi Pinot Community, This is a call for a vote to release Apache Pinot
>>> 0.9.0. The release candidate:
>>> https://dist.apache.org/repos/dist/dev/pinot/apache-pinot-0.9.0-rc0 Git
>>> tag for this release:
>>> https://github.com/apache/pinot/tree/release-0.9.0-rc0 Git hash for
>>> this release:
>>> cf8b84e8b0d6ab62374048de586ce7da21132906
>>> The artifacts have been signed with the key: CDEDB21B862F6C66, which
>>> can be found in
>>>  the following KEYS file.
>>> https://dist.apache.org/repos/dist/release/pinot/KEYS Release notes:
>>> https://github.com/apache/pinot/releases/tag/release-0.9.0-rc0 Staging
>>> repository:
>>> https://repository.apache.org/content/repositories/orgapachepinot-1031
>>> Documentation on verifying a release candidate:
>>> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
>>> The vote will be open for at least 72 hours or until a necessary number of
>>> votes is reached. Please vote accordingly, [ ] +1 approve [ ] +0 no opinion
>>> [ ] -1 disapprove with the reason Thanks, Apache Pinot team
>>>
>>

Re: [Announcement] Stop PQL support after 0.9.0 release, SQL only afterward

[Seunghyun Lee]

+1 on deprecating PQL


On Tue, Sep 14, 2021 at 10:17 AM Yupeng Fu  wrote:

> +1
>
>
>
> On Tue, Sep 14, 2021 at 9:50 AM Rong Rong  wrote:
>
>> +1 to deprecate PQL fully.
>>
>> Just to clarify:
>>
>> On Tue, Sep 14, 2021 at 1:51 AM Xiang Fu  wrote:
>>
>>> TL;DR, Pinot will remove PQL query endpoint and response format
>>> 
>>>  after
>>> 0.9.0 release, only SQL endpoint
>>> 
>>>  is
>>> supported afterward.
>>>
>>
>> >> does this mean we still support SQL endpoint? It seems to contradict
>> with the wording below:
>>
>> So we decide to remove the PQL query path and endpoint. If you are still
>>> on the PQL query path, please migrate to SQL endpoint:
>>> https://docs.pinot.apache.org/users/user-guide-query/querying-pinot
>>>
>>
>>
>> 2. Apache Pinot master branch will remove PQL support once the 0.9.0
>>> release is cut, and no PQL support from the 0.10.0 release.
>>>
>>
>> >> Shall we keep PQL codepath and annotate with @deprecated, then
>> officially remove it on 0.10.0? makes it easy if we decided to do a point
>> release.
>>
>>
>> --
>> Rong
>>
>
>
> --
> --Yupeng
>

[ANNOUNCE] Apache Pinot 0.8.0 released

[Seunghyun Lee]

Hello Community,

We are pleased to announce that Apache Pinot 0.8.0 is released!

Apache Pinot is a distributed columnar storage engine that can
ingest data in real-time and serve analytical queries at low latency.

The release can be downloaded at https://pinot.apache.org/download

The release note is available at
https://docs.pinot.apache.org/basics/releases/0.8.0

Additional resources -
Project website: https://pinot.apache.org
Getting started: https://docs.pinot.apache.org/getting-started
Pinot developer blogs: https://medium.com/apache-pinot-developer-blog
Intro to Pinot Video: https://www.youtube.com/watch?v=T70jTTYhYyM

Join Pinot Community -
Twitter: https://twitter.com/ApachePinot
Meetup: https://www.meetup.com/apache-pinot/
Slack channel: https://communityinviter.com/apps/apache-pinot/apache-pinot


Best Regards,
Apache Pinot Team

[RESULT][VOTE] Apache Pinot 0.8.0 RC0

[Seunghyun Lee]

Thanks to everyone for validating a release candidate. This vote is now
closed.

Apach Pinot 0.8.0 RC0 has passed with 4 +1 (binding), 2 +1 (non-binding)
votes
and no 0 or -1 votes.

Binding
+1 Xiaotian Jiang
+1 Xiang Fu
+1 Mayank Shrivastava
+1 Kishore Gopalakrishna

Non-binding
+1 Yupeng Fu
+1 Jialiang Li

Best,
Seunghyun

Re: [VOTE] Apache Pinot 0.8.0 RC0

[Seunghyun Lee]

@Yupeng,

I added partial upsert support to the release note. For the compilation
issue, I will wait for more people to validate to see if it's the real
issue.

Meanwhile, can you try to compile the code with more recent version of
maven?

Best,
Seunghyun

On Thu, Aug 12, 2021 at 3:11 PM Yupeng Fu  wrote:

> Also, in the release note, could you include the partial upsert support?
> It's an important feature added to upsert.
>
> Thanks,
>
> On Thu, Aug 12, 2021 at 3:10 PM Yupeng Fu  wrote:
>
>> Not sure if it's just me.  I got maven compilation failure with
>>
>> [WARNING] Error injecting:
>> org.apache.maven.artifact.installer.DefaultArtifactInstaller
>> com.google.inject.ProvisionException: Unable to provision, see the
>> following errors:
>>
>> 1) Error injecting: private org.eclipse.aether.spi.log.Logger
>> org.apache.maven.repository.internal.DefaultVersionRangeResolver.logger
>>   while locating
>> org.apache.maven.repository.internal.DefaultVersionRangeResolver
>>   while locating java.lang.Object annotated with *
>>   at org.eclipse.sisu.wire.LocatorWiring
>>   while locating org.eclipse.aether.impl.VersionRangeResolver
>> for parameter 2 at
>> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.(Unknown
>> Source)
>>   while locating
>> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector
>>   while locating java.lang.Object annotated with *
>>   at org.eclipse.sisu.wire.LocatorWiring
>>   while locating org.eclipse.aether.impl.DependencyCollector
>> for parameter 5 at
>> org.eclipse.aether.internal.impl.DefaultRepositorySystem.(Unknown
>> Source)
>>   while locating org.eclipse.aether.internal.impl.DefaultRepositorySystem
>>   while locating java.lang.Object annotated with *
>>   while locating
>> org.apache.maven.artifact.installer.DefaultArtifactInstaller
>> Caused by: java.lang.IllegalArgumentException: Can not set
>> org.eclipse.aether.spi.log.Logger field
>> org.apache.maven.repository.internal.DefaultVersionRangeResolver.logger to
>> org.eclipse.aether.internal.impl.slf4j.Slf4jLoggerFactory
>> at
>> java.base/jdk.internal.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldA
>> ...
>>
>> [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>> [ERROR] at
>> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>> [ERROR] at
>> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> [ERROR] at
>> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> [ERROR] at java.base/java.lang.reflect.Method.invoke(Method.java:566)
>> [ERROR] at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>> [ERROR] at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>> [ERROR] at
>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>> [ERROR] at
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>> [ERROR]
>> [ERROR] 4 errors
>> [ERROR] role: org.apache.maven.plugin.Mojo
>> [ERROR] roleHint:
>> org.apache.maven.plugins:maven-install-plugin:2.5.2:install
>> [ERROR] -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>>
>> On Thu, Aug 12, 2021 at 2:49 PM Xiaotian Jiang 
>> wrote:
>>
>>> +1
>>>
>>> Jackie
>>>
>>> On Wed, Aug 11, 2021 at 4:03 PM Seunghyun Lee  wrote:
>>>
>>>> Hi Pinot Community,
>>>>
>>>> This is a call for a vote to release Apache Pinot 0.8.0.
>>>>
>>>> The release candidate:
>>>> https://dist.apache.org/repos/dist/dev/pinot/apache-pinot-0.8.0-rc0
>>>>
>>>> Git tag for this release:
>>>> https://github.com/apache/pinot/tree/release-0.8.0-rc0
>>>>
>>>> Git hash for this release:
>>>> c4ceff06d21fc1c1b88469a8dbae742a4b609808
>>>>
>>>> The artifacts have been signed with key: 7199AF89, which can be found
>>>> in the following KEYS file.
>>>> https://dist.apache.org/repos/dist/release/pinot/KEYS
>>>>
>>>> Release notes:
>>>> https://github.com/apache/pinot/releases/tag/release-0.8.0-rc0
>>>>
>>>> Staging repository:
>>>> https://repository.apache.org/content/repositories/orgapachepinot-1030
>>>>
>>>> Documentation on verifying a release candidate:
>>>>
>>>> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
>>>>
>>>> The vote will be open for at least 72 hours or until a necessary number
>>>> of votes is reached.
>>>>
>>>> Please vote accordingly,
>>>>
>>>> [ ] +1 approve
>>>> [ ] +0 no opinion
>>>> [ ] -1 disapprove with the reason
>>>>
>>>> Thanks,
>>>> Apache Pinot team
>>>>
>>>
>>
>> --
>> --Yupeng
>>
>
>
> --
> --Yupeng
>

[VOTE] Apache Pinot 0.8.0 RC0

[Seunghyun Lee]

Hi Pinot Community,

This is a call for a vote to release Apache Pinot 0.8.0.

The release candidate:
https://dist.apache.org/repos/dist/dev/pinot/apache-pinot-0.8.0-rc0

Git tag for this release:
https://github.com/apache/pinot/tree/release-0.8.0-rc0

Git hash for this release:
c4ceff06d21fc1c1b88469a8dbae742a4b609808

The artifacts have been signed with key: 7199AF89, which can be found in
the following KEYS file.
https://dist.apache.org/repos/dist/release/pinot/KEYS

Release notes:
https://github.com/apache/pinot/releases/tag/release-0.8.0-rc0

Staging repository:
https://repository.apache.org/content/repositories/orgapachepinot-1030

Documentation on verifying a release candidate:
https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate

The vote will be open for at least 72 hours or until a necessary number of
votes is reached.

Please vote accordingly,

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Thanks,
Apache Pinot team

Re: Podling Pinot Report Reminder - June 2021

[Seunghyun Lee]

Dear Mentors,

Can we get the sign-off for the Podling Report?

The deadline is by the end of today.
https://cwiki.apache.org/confluence/display/INCUBATOR/June2021#pinot

Best,
Seunghyun

On Wed, Jun 2, 2021 at 9:46 PM  wrote:
>
> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 16 June 2021.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, June 02).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/June2021
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Note: The format of the report has changed to use markdown.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
> For additional commands, e-mail: dev-h...@pinot.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
For additional commands, e-mail: dev-h...@pinot.apache.org

Re: [VOTE] Apache Pinot graduation to a TLP

[Seunghyun Lee]

+1

Best,
Seunghyun

On Fri, Jun 4, 2021 at 10:14 AM Mayank Shrivastava 
wrote:

> +1
>
> Adding permalink of the dev discussion:
> https://lists.apache.org/thread.html/r6068cae91a474e86595cc02d90701501d22c08274216301facf935cc%40%3Cdev.pinot.apache.org%3E
> And carrying over the votes from the dev discussion:
>
> Mentors:
> +1 Felix Cheug
> +1 Kishore G
> +1 Olivier Lamy
> +1 Jim Jagielsky
>
> PPMC:
> +1 Mayank Shrivastava
> +1 Seunghyun Lee
> +1 Xiang Fu
> +1 Subbu Subramaniam
>
> Committers:
> +1 Yupeng Fu
>
> On Fri, Jun 4, 2021 at 10:00 AM Subbu Subramaniam 
> wrote:
>
>> +1
>>
>> -Subbu
>>
>> On 2021/06/04 16:55:14, Mayank Shrivastava  wrote:
>> > Hello all,
>> >
>> > As per our discussion on the dev mailing list
>> > <https://lists.apache.org/list.html?dev@pinot.apache.org>, I would
>> like to
>> > call a VOTE for Apache Pinot graduating as a top level Apache project.
>> >
>> > If this vote passes, the next step would be to submit the resolution
>> below
>> >
>> > to the Incubator PMC, who would vote on sending it on to the Apache
>> Board.
>> >
>> > Vote:
>> >
>> > [ ] +1 - Recommend graduation of Apache Pinot as a TLP
>> >
>> > [ ] -1 - Do not recommend the graduation of Apache Pinot because...
>> >
>> > The VOTE is open for a minimum of 72 hours.
>> >
>> > Establish the Apache Pinot Project
>> >
>> > WHEREAS, the Board of Directors deems it to be in the best interests of
>> the
>> > Foundation and consistent with the Foundation's purpose to establish a
>> > Project Management Committee charged with the creation and maintenance
>> of
>> > open-source software, for distribution at no charge to the public,
>> related
>> > to a distributed data integration framework that simplifies common
>> aspects
>> > of big data integration such as data ingestion, replication,
>> organization
>> > and lifecycle management for both streaming and batch data ecosystems.
>> >
>> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>> (PMC),
>> > to be known as the "Apache Pinot Project", be and hereby is established
>> > pursuant to Bylaws of the Foundation; and be it further
>> >
>> > RESOLVED, that the Apache Pinot Project be and hereby is responsible for
>> > the creation and maintenance of software related to distributed OLAP
>> data
>> > store to provide Real-time Analytics to power wide variety of analytical
>> > use case; and be it further
>> >
>> > RESOLVED, that the office of "Vice President, Apache Pinot" be and
>> hereby
>> > is created, the person holding such office to serve at the direction of
>> the
>> > Board of Directors as the chair of the Apache Pinot Project, and to have
>> > primary responsibility for management of the projects within the scope
>> of
>> > responsibility of the Apache Pinot Project; and be it further
>> >
>> > RESOLVED, that the persons listed immediately below be and hereby are
>> > appointed to serve as the initial members of the Apache Pinot Project:
>> >
>> >-
>> >
>> >Felix Cheung 
>> >-
>> >
>> >Jackie Jiang 
>> >-
>> >
>> >Jim Jagielski 
>> >-
>> >
>> >Kishore G 
>> >-
>> >
>> >Mayank Shrivastava 
>> >-
>> >
>> >Neha Pawar 
>> >-
>> >
>> >Olivier Lamy 
>> >-
>> >
>> >Seunghyun Lee 
>> >-
>> >
>> >Siddharth Teotia 
>> >-
>> >
>> >Subbu Subramaniam 
>> >-
>> >
>> >Xiang Fu 
>> >
>> >
>> >
>> >
>> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Kishore Gopalakrishna be
>> > appointed to the office of Vice President, Apache Pinot, to serve in
>> > accordance with and subject to the direction of the Board of Directors
>> and
>> > the Bylaws of the Foundation until death, resignation, retirement,
>> removal
>> > of disqualification, or until a successor is appointed; and be it
>> further
>> >
>> > RESOLVED, that the Apache Pinot Project be and hereby is tasked with the
>> > migration and rationalization of the Apache Incubator Pinot podling;
>> and be
>> > it further
>> >
>> > RESOLVED, that all responsibilities pertaining to the Apache Incubator
>> > Pinot podling encumbered upon the Apache Incubator PMC are hereafter
>> > discharged.
>> >
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
>> For additional commands, e-mail: dev-h...@pinot.apache.org
>>
>>

Updated the PR for fixing license issue

[Seunghyun Lee]

Hi all,

While we went through the release process for 0.7.1, we found that we
added unnecessary license packages to "LICENSE" file. So, we created
the issue (https://github.com/apache/incubator-pinot/issues/6785) and
this is being addressed in PR
(https://github.com/apache/incubator-pinot/pull/6944).

It would be great if we can get reviews from the community and mentors.

Best,
Seunghyun

-
To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
For additional commands, e-mail: dev-h...@pinot.apache.org

Review request for Apache Maturity Model Assessment for Pinot

[Seunghyun Lee]

Hi all,

I have finished the initial draft of Apache Maturity Model Assessment
document for Pinot. This document will be evaluated as part of our
graduation process.

https://cwiki.apache.org/confluence/display/PINOT/Apache+Maturity+Model+Assessment+for+Pinot

It would be great if we can get some reviews from the community.

Best,
Seunghyun

-
To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
For additional commands, e-mail: dev-h...@pinot.apache.org

Re: About cutting the 0.8.0 release (graduation release)

[Seunghyun Lee]

I think that it's probably good to go through the last incubating
release before we do the graduation to go through the clean-up and
final checks from IPMC.

On the other hand, I don't want to block the graduation process for
creating a new release if there is no special requirement for that.
The release process can take quite a while.

How other ppl think about creating the release before/after graduation?

Best,
Seunghyun


On Mon, May 10, 2021 at 12:25 PM kishore g  wrote:
>
> Thanks Seunghyun for starting this thread.
>
> There is no special requirement to have a graduation release. Graduation is a 
> separate process from release. It’s just that release process changes 
> slightly after the graduation.
>
> Do you want to do this release before or after graduation?
>
> On Mon, May 10, 2021 at 11:27 AM Subbu Subramaniam  
> wrote:
>>
>> Hopefully, everyone has been following the process of labelling PRs for 
>> release notes and noting any compatibility issues as well.
>>
>> If so, you should be able to get a list of commits (and PRs) and look for 
>> the labelled ones to answer the compatibility and release notes questions.
>>
>> I don't know of any other way than scanning the commit messages to come up 
>> with the major features or bug fixes list.
>>
>> -Subbu
>>
>> On 2021/05/10 18:04:41, Seunghyun Lee  wrote:
>> > Hi all,
>> >
>> > Given that we started to have a conversation about the graduation
>> > process, I would like to use this thread for discussing about 0.8.0
>> > release (graduation release).
>> >
>> > Some points that we need to discuss:
>> > - What are the major features that we would like to highlight?
>> > - Do we have any pending features that need to be part of 0.8.0 release?
>> > - Have we introduced any backward incompatibility?
>> >
>> > By the way, I would like to volunteer for creating the 0.8.0 release.
>> > Given that I set up the initial Apache release pipeline for Pinot and
>> > created the first 0.1.0 Pinot release, I think that I have enough
>> > context to clear some issues that got brought up during the last
>> > release process (e.g. LICENSE).
>> >
>> > Best,
>> > Seunghyun
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
>> > For additional commands, e-mail: dev-h...@pinot.apache.org
>> >
>> >
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
>> For additional commands, e-mail: dev-h...@pinot.apache.org
>>

-
To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
For additional commands, e-mail: dev-h...@pinot.apache.org

About cutting the 0.8.0 release (graduation release)

[Seunghyun Lee]

Hi all,

Given that we started to have a conversation about the graduation
process, I would like to use this thread for discussing about 0.8.0
release (graduation release).

Some points that we need to discuss:
- What are the major features that we would like to highlight?
- Do we have any pending features that need to be part of 0.8.0 release?
- Have we introduced any backward incompatibility?

By the way, I would like to volunteer for creating the 0.8.0 release.
Given that I set up the initial Apache release pipeline for Pinot and
created the first 0.1.0 Pinot release, I think that I have enough
context to clear some issues that got brought up during the last
release process (e.g. LICENSE).

Best,
Seunghyun

-
To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
For additional commands, e-mail: dev-h...@pinot.apache.org

Re: DISCUSS Pinot Graduation

[Seunghyun Lee]

+1 on initiating the graduation process. I also think that we have a
very strong community around the project.

Best,
Seunghyun

On Mon, May 10, 2021 at 9:51 AM Yupeng Fu  wrote:
>
> +1 on graduation readiness. Apache Pinot has a lot of accomplishments in the 
> past years on project maturity. It has a strong community and good adoption 
> in the industry.
>
> Best,
>
> On Sun, May 9, 2021 at 8:54 AM Mayank Shrivastava  
> wrote:
>>
>> +1 on initiating the discussion on readiness for graduation. Apache Pinot 
>> now has a very strong and healthy community around it, formalizing the 
>> graduation will only help further. If there are formalities remaining we 
>> will be happy to address them.
>>
>> Regards
>> Mayank
>>
>> On May 9, 2021, at 7:08 AM, kishore g  wrote:
>>
>> 
>>
>> Hello,
>>
>>
>> I would like to start a conversation about the readiness of Apache Pinot to 
>> graduate. We have come a long way since we incubated in Apache, with:
>>
>>
>> 7800+ contributions from 168 contributors
>>
>> 7 releases by various committers
>>
>> 6 new committers invited (all accepted)
>>
>> Apache website available at: https://pinot.apache.org
>>
>> Updated Apache Pinot (incubating) page
>>
>> Updated Roster Page
>>
>> Dev conversations at d...@pinot.incubator.org
>>
>> Diverse committers and PPMCs (from 7 companies / institutes)
>>
>> We have built a meritocratic and open collaborative progress (the Apache way)
>>
>> A strong community of 1200+ members in Apache Pinot Slack. All conversations 
>> emailed to dev@ in the form of a digest
>>
>>
>> Please let us know if there are remaining steps involved in completing the 
>> graduation process.
>>
>>
>> Thanks,
>>
>> Kishore G
>>
>>
>
>
> --
> --Yupeng

-
To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
For additional commands, e-mail: dev-h...@pinot.apache.org

Re: Mentor for Pinot

[Seunghyun Lee]

I think that having another mentor would help us to be better prepared
for graduation. We will be able to get extra checks/inputs before we
officially start to discuss the graduation in the incubator thread.

I personally support Owen's offer to become the mentor for Pinot.


Best,
Seunghyun

On Wed, Feb 17, 2021 at 4:51 AM Jim Jagielski  wrote:
>
> Personally, I see no issue w/ having another mentor and support Owen's offer.
>
> On Feb 16, 2021, at 2:35 PM, Owen O'Malley  wrote:
>
> Ok, looking at the various checks, Pinot has two people on the private list 
> that Apache doesn't recognize the email address:
>
> ssubraman...@linkedin.com (not recognised)
> jiha...@gmail.com Jihao Zhang jihao
>
> Subbu should update his ASF entry to include his LinkedIn email. Jihao is 
> currently a committer, so they should not be on the private list.
>
> .. Owen
>
> On Sat, Feb 13, 2021 at 1:38 AM kishore g  wrote:
>>
>> Hi Owen, Thanks for the offer. We are in good hands with Oliver who has 
>> helped me with Helix. We will let you know if we need additional help in the 
>> future
>>
>> Thanks,
>> Kishore G
>>
>> On Fri, Feb 12, 2021 at 4:51 PM Owen O'Malley  wrote:
>>>
>>> Now that Gobblin has graduated from Apache Incubator, I would like to 
>>> volunteer as a mentor for Pinot, if the project thinks that would help. I 
>>> have gone through the process several times of helping projects graduate 
>>> from Incubator. *smile*
>>>
>>> Let me know your thoughts,
>>>Owen
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
For additional commands, e-mail: dev-h...@pinot.apache.org

Re: [ANNOUNCE] Apache Pinot (incubating) 0.4.0 released

[Seunghyun Lee]

Congrats!

Haibo, thank you for driving this.

Best,
Seunghyun

On Sun, Jun 14, 2020 at 10:44 PM H  wrote:

> Hello community,
>
> We are pleased to announce that Apache Pinot (incubating) 0.4.0 is
> released!
>
> Apache Pinot (incubating) is a distributed columnar storage engine that can
> ingest data in realtime and serve analytical queries at low latency.
>
> The release can be downloaded at: https://pinot.apache.org/download
>
> The release note is available at:
> https://docs.pinot.apache.org/releases/0.4.0
>
> Additional resources -
> Project website: https://pinot.apache.org
> Getting started: https://docs.pinot.apache.org/getting-started
> Mailing list: dev@pinot.apache.org
> Slack channel: https://communityinviter.com/apps/apache-pinot/apache-pinot
> Twitter: https://twitter.com/ApachePinot
>
> Best Regards,
>
> Apache Pinot (incubating) Team
>

[Vote] Enabling html for Pinot related mailing lists

[Seunghyun Lee]

Hi all,

While I was working on setting up the daily digest from slack channels, I
found that the html rendering feature is turned off by default for Pinot
mailing list.

I tried to request to enable the feature from
https://issues.apache.org/jira/browse/INFRA-20423 and this needs the
project consensus.

I would like to start the vote for "enabling html for Pinot mailing lists".

Please vote accordingly:
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Thank you!
Seunghyun

Design document for segment merge process

[Seunghyun Lee]

Hi all,

I have written the design document for the segment merge. Please review the
document and any kind of feedback is welcome :)


https://docs.google.com/document/d/1-AKCfXNXdoNjFIvJ87wjWwFM_38gS0NCwFrIYjYsqp8/edit?usp=sharing

Best,
Seunghyun

About the binary files for source code release

[Seunghyun Lee]

Hi all,

One of the comments for 0.4.0-rc2 candidate was about binary files under
"/kubernetes" directory.

"""
./kubernetes/helm/pinot-0.2.0.tgz
./kubernetes/helm/pinot/charts/zookeeper-2.1.3.tgz
./kubernetes/helm/presto-0.2.0.tgz
"""

We can start to discuss on how to handle those. I extracted the files and
it's doesn't include any executable files. I would guess that those are
some configuration/ script files needed to launch zookeeper on Kubernetes.

❯ tar xvf zookeeper-2.1.3.tgz
x zookeeper/Chart.yaml
x zookeeper/values.yaml
x zookeeper/templates/NOTES.txt
x zookeeper/templates/_helpers.tpl
x zookeeper/templates/config-jmx-exporter.yaml
x zookeeper/templates/config-script.yaml
x zookeeper/templates/job-chroots.yaml
x zookeeper/templates/poddisruptionbudget.yaml
x zookeeper/templates/service-headless.yaml
x zookeeper/templates/service.yaml
x zookeeper/templates/servicemonitors.yaml
x zookeeper/templates/statefulset.yaml
x zookeeper/.helmignore
x zookeeper/OWNERS
x zookeeper/README.md

@Felix Cheung  What are the recommended way to
handle this? Remove it from source code release? If we want to include
those tgz files, what is the recommended way to handle them?

Best,
Seunghyun

Re: [VOTE] Apache Pinot (incubating) 0.4.0 RC2

[Seunghyun Lee]

+1

1. checked that the bundle contains "incubator"
2. verified signature and file checksum
3. verified git tag & commit
4. verified that DISCLAIMER, LICENSE, NOTICE files are present
5. verified that the source code compiles
6. ran the quick starter script and worked fine for both bin/src.

On Mon, Jun 8, 2020 at 2:05 PM Subbu Subramaniam 
wrote:

> +1
>
> The functionality works, but I do see exceptions from jersey when running
> quickstart programs.
>
> -Subbu
>
> On 2020/06/02 15:10:11, H  wrote:
> > Hi Pinot Community,
> >
> > This is a call for vote to the release Apache Pinot (incubating) version
> > 0.4.0
> >
> > The release candidate:
> >
> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.4.0-rc2
> >
> > Git tag for this release:
> > https://github.com/apache/incubator-pinot/tree/release-0.4.0-rc2
> >
> > Git hash for this release:
> > 8355d2e0e489a8d127f2e32793671fba505628a8
> >
> > The artifacts have been signed with key: 6CC169A6FC19C470, which can be
> > found in the following KEYS file.
> > https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS
> >
> > Release notes:
> > GitHub:
> > https://github.com/apache/incubator-pinot/releases/tag/release-0.4.0-rc2
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachepinot-1013
> >
> > Documentation on verifying a release candidate:
> >
> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
> >
> >
> > The vote will be open for at least 72 hours or until necessary number of
> > votes are reached.
> >
> > Please vote accordingly,
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Thanks,
> > Apache Pinot (incubating) team
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
> For additional commands, e-mail: dev-h...@pinot.apache.org
>
>

Re: Adding a new field in SegmentsValidationAndRetentionConfig for peer segment download

[Seunghyun Lee]

If the final goal is to make this as the server level configuration (and
remove the table level in the future), I recommend adding this config
inside of `StreamConfig` because it will be much easier to remove the
config from StreamConfig because it's a map.

As Subbu mentioned, we may need to put it in the table config if this
feature needs to work for both offline/realtime.

@Ting Is this feature will only be used for realtime?



On Mon, May 11, 2020 at 11:10 AM Subbu Subramaniam 
wrote:

> The goal of the config change in [arts other than StreamConfig is to
> ensure that the config can be used for offline segments as well, if for
> some reason download fails.
>
> However, a race condition can happen for offline segments that can be
> dangerous. If a segment has been updated with a newer version, and server A
> and B have old versions. Both of them get notified of the newer version.
> They may try to fetch the segment and fail, and eventually fetch from each
> other, and end up thinking that they have the newest version of the
> segment.There can be other variants of this as well, with restarts of
> server.
>
> I can think of some ways to fix this (e.g. in the segment update message,
> send the crc of the new version), but these have not been fully thought of.
> We need to vet these well before adopting these.
>
> I prefer option 1 since it introduces a single config.
>
> I would like to hear from @kishoreg and @npawar as well
>
> -Subbu
>
> On 2020/05/06 00:16:26, TING CHEN  wrote:
> > As part of the proposal
> > <
> https://cwiki.apache.org/confluence/display/PINOT/By-passing+deep-store+requirement+for+Realtime+segment+completion
> >
> > to bypass deep store for segment completion, I plan to add a new optional
> > string field *peerSegmentDownloadScheme* to
> > the SegmentsValidationAndRetentionConfig in the TableConfig. The value
> can
> > be *http* or *https*.
> >
> >1. SplitSegmentCommitter
> ><
> https://github.com/apache/incubator-pinot/blob/31c55afdb6a40f98189308ce6292587ead9d0dec/pinot-core/src/main/java/org/apache/pinot/core/data/manager/realtime/SplitSegmentCommitter.java
> >
> >will check this value. If it exists, the segment committer will be
> able to
> >finish segment commit successfully even if the upload to the segment
> store
> >fails. The committer will report a special marker to the controller
> about
> >the segment is available in peer servers.
> >2. When Pinot servers fail to download segments from the segment
> store,
> >they can also check this field's value. If it exists, it can download
> >segments from peer servers using either HTTP and HTTPS segment
> fetchers as
> >configured. (related PR
> > in review for
> how
> >to discover such servers.)
> >
> > Note this is a table level config. We will test the new download behavior
> > in realtime tables in incremental fashion. Once fully proven, this config
> > can be upgraded to server level config.
> >
> > Please let me know if you have any questions on this. Thanks @mcvsubbu
> for
> > coming up with the idea and offline discussions.
> >
> > Ting Chen
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
> For additional commands, e-mail: dev-h...@pinot.apache.org
>
>

Fwd: [MENTORS] https://www.apache.org/dist/ has been deprecated

[Seunghyun Lee]

@Xiang

Can you make the change when you update the download page for 0.3.0 release?

Best,
Seunghyun

-- Forwarded message -
From: Bertrand Delacretaz 
Date: Mon, Mar 9, 2020 at 3:18 AM
Subject: Re: [MENTORS] https://www.apache.org/dist/ has been deprecated
To: Incubator General 


Hi,

On Wed, Mar 4, 2020 at 10:15 AM Justin Mclean 
wrote:
> The new URL to use is https://downloads.apache.org. ...

FWIW, https://blogs.apache.org/infra/entry/more-secure-and-robust-downloads
has more info.

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Preparing for upcoming Pinot Release

[Seunghyun Lee]

@Xiang

You can refer to the following page for the release process.
https://cwiki.apache.org/confluence/display/PINOT/Creating+an+Apache+Release

Please let me know if you face any issue during the process.

Seunghyun

On Fri, Feb 28, 2020 at 12:39 AM Fu Xiang  wrote:

> We finally got all the pending commits reviewed and merged!
>
> The upcoming release(0.3.0) will be cut from current master branch commit (
> 9abf0a4b105d624ec310273c2bd7f52c1f3ce12a
> <
> https://github.com/apache/incubator-pinot/commit/9abf0a4b105d624ec310273c2bd7f52c1f3ce12a
> >)
> as of date: Wed Feb 27 16:09:51 PST 2020.
>
> The release notes is here:
> https://apache-pinot.gitbook.io/apache-pinot-cookbook/releases/0.3.0
>
> Please let me know if you have any questions.
>
> Best,
>
> Xiang
>
> Fu Xiang  于2020年2月18日周二 上午3:35写道：
>
> > Here is the draft
> > <
> https://docs.google.com/document/d/1zCY6KNma3WoHIju9Revp7JUlr4gtIYPPwu6xpJzlY3I/edit?usp=sharing
> >
> > for new release notes.
> >
> > All comments are welcome.
> >
> > Subbu Subramaniam  于2020年2月16日周日
> > 下午1:02写道：
> >
> >> The best way to communicate such major change in interface is by
> updating
> >> the major version number.
> >>
> >> We can say that the software has been restructured significantly to
> >> accommodate cloud readiness (blog coming up soon) and easy plug n play.
> >>
> >> Which was the objective of the re-factor anyway.
> >>
> >> What is the reaon NOT to call it 1.0?
> >>
> >> -Subbu
> >> 
> >> From: kishore g 
> >> Sent: Sunday, February 16, 2020 10:24 AM
> >> To: dev@pinot.apache.org 
> >> Subject: Re: Preparing for upcoming Pinot Release
> >>
> >> Hi Subbu,
> >>
> >> I am with you on significant changes to the package names and the need
> to
> >> recompile the code if anyone has the wrapper like LinkedIn. What do you
> >> think is the best way to communicate this without calling it 1.0.
> >>
> >> thanks,
> >> Kishore G
> >>
> >>
> >>
> >>
> >> On Sun, Feb 16, 2020 at 9:40 AM Subbu Subramaniam 
> >> wrote:
> >>
> >> > I disagree.
> >> >
> >> > In LinkedIn, we had to change our wrapper software significantly due
> to
> >> > the API (and package name) changes.
> >> >
> >> > Have you compiled the release notes? That should indicate the amount
> of
> >> > changes that went in.
> >> >
> >> > -Subbu
> >> >
> >> > On 2020/02/16 05:49:16, Fu Xiang  wrote:
> >> > > Regarding the version, I suggest to still call it 0.3.0 as the
> >> > > PluginManager is still backward compatible from users' perspective
> in
> >> PR:
> >> > >
> >>
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fincubator-pinot%2Fpull%2F5035data=02%7C01%7Cssubramaniam%40linkedin.com%7C7fd26a7da6454a3e9cea08d7b30d8d73%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637174743102251978sdata=o%2Fin2UJZYqX7gvCadZR4Bji4HhSQ1XQ0G8fUC7OkSc0%3Dreserved=0
> >> .
> >> > >
> >> > > We can leave 1.0.0 for something bigger later.
> >> > >
> >> > > On Thu, Feb 13, 2020 at 12:08 Subbu Subramaniam  >
> >> > wrote:
> >> > >
> >> > > > Thanks, @kishore g 
> >> > > > Please do send it out for a review when the docs are ready
> >> > > >
> >> > > > thanks
> >> > > >
> >> > > > -Subbu
> >> > > >
> >> > > >
> >> > > > On Thu, Feb 13, 2020 at 10:27 AM kishore g 
> >> > wrote:
> >> > > >
> >> > > > > @Siddharth Teotia  Lets get the text PR
> >> > merged.
> >> > > > > Will be good to release it as experimental and collect feedback.
> >> > > > >
> >> > > > > @Subbu Subramaniam  We have moved all the
> >> docs
> >> > from
> >> > > > > RTD to gitbook. I need to restructure a bit and it will be ready
> >> to
> >> > go by
> >> > > > > the time we make the release.
> >> > > > > Let's call out all the major changes in 1.0.0
> >> > > > >
> >> > > > > On Thu, Feb 13, 2020 at 9:59 AM Subbu Subramaniam <
> >> > mcvsu...@apache.org>
> >> > > > > wrote:
> >> > > > >
> >> > > > >> Hi Xiang,
> >> > > > >>
> >> > > > >> Thanks for taking on the release work.
> >> > > > >>
> >> > > > >> I suppose the version will be 1.0.0?
> >> > > > >>
> >> > > > >> Please make sure that:
> >> > > > >> 1. Either we are migrated fully to the new documentation, OR we
> >> have
> >> > > > >> documented all new features in the existing documentation. The
> >> > current
> >> > > > >> situation is that neither of these is true. It will be
> >> unfortunate
> >> > if we
> >> > > > >> make a release with documentation in two places, neither of
> >> which is
> >> > > > >> complete. I will be willing to help fix the doc issue. Please
> >> send
> >> > out
> >> > > > an
> >> > > > >> email to committers (or general) providing appropriate
> >> instructions,
> >> > > > and we
> >> > > > >> can have the community fix the documents before the release.
> >> > > > >> 2. The release notes lists all the incompatiblities introduced,
> >> and
> >> > > > >> migration plans, etc.  I know of at least one incompatibility.
> >> You
> >> > > > cannot
> >> > > > >> upgrade from 0.1 to 1.0 without going through 0.2, 

Re: Moving from RTD to Gitbook

[Seunghyun Lee]

When we officially move to Gitbook, we should do the following things:

1. Change the documentation pointer from pinot.apache.org webpage
2. remove doc files from main Pinot repo ( I believe that Gitbook is backed
by another git repo?)

Best,
Seunghyun

On Tue, Feb 18, 2020 at 4:26 PM kishore g  wrote:

> Hi,
>
> In the next release (should happen over the next couple of weeks), we will
> be moving out of ReadTheDocs to Gitbook. Going forward, please use GitBook
> while adding any documentation. We have moved all the content from RTD to
> GitBook. I am still working on re-organizing the contents and adding new
> content.
>
> Please let me know if you have any questions/comments.
>
> thanks,
> Kishore G
>

Re: [VOTE] Apache Pinot (incubating) 0.2.0 RC0

[Seunghyun Lee]

+1

1. Checked that the bundles contains "incubating"
2. Verified the signature and hash
3. Verified that the release source matches with the code from Github
4. Checked that the source can be compiled (used RHEL 7 linux)
5. Ran quick starter script to check the basic functionality


On Wed, Nov 13, 2019 at 1:25 PM Subbu Subramaniam 
wrote:

> Hi Seunghyun,
>
> Thanks for your vote.
>
> With respect to your suggestions:
> 1. 164D961B is still your key :-) I had sent a follow-up vote request with
> my correct key (B530034C).
> 2. I have also added the signature to the KEYS file now.
>
> thanks again
>
> -Subbu
>
> On Tue, Nov 12, 2019 at 1:52 PM Subbu Subramaniam 
> wrote:
>
> > Please disregard the earlier message. Here is the correct one
> >
> > Hi Pinot Community,
> >
> > This is a call for vote to the release Apache Pinot (incubating) version
> > 0.2.0.
> >
> > The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.2.0-rc0
> >
> > Git tag for this release:
> https://github.com/apache/incubator-pinot/tree/release-0.2.0-rc0
> > Git hash for this release:f8e1980c4160ac7fd2686d9edefab9ac0a825c5b
> >
> > The artifacts have been signed with key: B530034C, which can be
> > found in the following KEYS file.
> https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS
> >
> > Release notes:
> https://github.com/apache/incubator-pinot/releases/tag/release-0.2.0-rc0
> >
> > Staging repository:
> https://repository.apache.org/content/repositories/orgapachepinot-1003
> >
> > Documentation on verifying a release candidate:
> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
> >
> >
> > The vote will be open for at least 72 hours or until necessary number of
> > votes are reached.
> >
> > Please vote accordingly,
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Thanks,
> > Apache Pinot (incubating) team
> >
> >
>

Re: [VOTE] Apache Pinot (incubating) 0.2.0 RC0

[Seunghyun Lee]

+1

1. Checked that the bundles contains "incubating"
2. Verified the signature and hash
3. Verified that the release source matches with the code from Github
4. Checked that the source can be compiled (used RHEL 7 linux)
5. Ran quick starter script to check the basic functionality



Suggestion:

1. You mentioned that the artifact is signed with key
*44BA03AD164D961B. *Actually,
this is my key. You need to change it to yours, which is *164D961B.*
2. Let's actually add header information in
https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS If we
included the header information, we can easily check if key id mentioned in
the mail is valid. We cannot know if your key id (*164D961B*) is valid or
not by looking at KEYS file since we only added your actual key content.

e.g.
"""

pub   rsa2048 2019-02-01 [SC] [expires: 2021-01-31]
  FD534854D542FD474278B85344BA03AD164D961B
uid       [ultimate] Seunghyun Lee 
sig 344BA03AD164D961B 2019-02-01  Seunghyun Lee 
sub   rsa2048 2019-02-01 [E] [expires: 2021-01-31]
sig  44BA03AD164D961B 2019-02-01  Seunghyun Lee 

"""



On Wed, Nov 13, 2019 at 9:34 AM Mayank Shrivastava
 wrote:

> +1
> 
> From: Subbu Subramaniam 
> Sent: Tuesday, November 12, 2019 1:41 PM
> To: dev@pinot.apache.org 
> Subject: [VOTE] Apache Pinot (incubating) 0.2.0 RC0
>
> Hi Pinot Community,
>
> This is a call for vote to the release Apache Pinot (incubating) version
> 0.2.0.
>
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.2.0-rc0
>
> Git tag for this
> release:https://github.com/apache/incubator-pinot/tree/release-0.2.0-rc0
> Git hash for this release:f8e1980c4160ac7fd2686d9edefab9ac0a825c5b
>
> The artifacts have been signed with key: 44BA03AD164D961B, which can be
> found in the following KEYS
> file.https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS
>
> Release notes:
> https://github.com/apache/incubator-pinot/releases/tag/release-0.2.0-rc0
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachepinot-1003
>
> Documentation on verifying a release
> candidate:
> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
>
>
> The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
>
> Please vote accordingly,
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> Apache Pinot (incubating) team
>

Re: Contributor Permission Request

[Seunghyun Lee]

Hi leesf,

We don't have any specific contribution permission. You can always fork the
pinot github repo and file a pull request against the main repository.

Please refer to our contribution guideline document.
https://pinot.readthedocs.io/en/latest/contribution_guidelines.html

If you have any other question, please let us know!

Best,
Seunghyun


On Wed, Sep 4, 2019 at 1:09 AM leesf  wrote:

> Hi,
>
> I want to contribute to Apache pinot.
> Would you please give me the contributor permission?
> My JIRA ID is xleesf.
>

Fwd: Incubator report timeline August 2019

[Seunghyun Lee]

We need to report this time. Is anyone working on this?

-- Forwarded message -
From: Justin Mclean 
Date: Tue, Jul 23, 2019 at 8:53 PM
Subject: Re: Incubator report timeline August 2019
To: 


Hi,

Podlings expect to report this month:

Amaterasu
DataSketches
Doris
ECharts
Edgent
Heron
Livy
PageSpeed
Pinot
Ratis
S2Graph
SDAP
Tamay
Toree
Training
Tuweni

Thanks,
Justin

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Missing podling logos

[Seunghyun Lee]

It's updated automatically. Our logo is now available
http://www.apache.org/logos/?#pinot



On Wed, Jun 5, 2019 at 11:21 AM Seunghyun Lee  wrote:

> I have uploaded our logo to
> https://svn.apache.org/repos/asf/comdev/project-logos/originals/
>
> I followed the instruction from http://www.apache.org/logos/about.html
>
> Does this need some time to get propagated to the logo page?
>
> Seunghyun
>
> On Mon, Jun 3, 2019 at 11:04 PM Felix Cheung 
> wrote:
>
>> http://www.apache.org/logos/
>>
>> 
>> From: Subbu Subramaniam 
>> Sent: Monday, June 3, 2019 9:00 AM
>> To: dev@pinot.apache.org
>> Subject: Re: Missing podling logos
>>
>> Thanks for the reminder Felix.
>>
>> Where exactly do we add the logo? We do have one in this page:
>>
>> https://pinot.incubator.apache.org/
>>
>> thanks
>>
>> -Subbu
>> 
>> From: Felix Cheung 
>> Sent: Sunday, June 2, 2019 11:51 AM
>> To: dev@pinot.apache.org
>> Subject: Fwd: Missing podling logos
>>
>> Quick reminder...
>>
>> -- Forwarded message -
>> From: Justin Mclean 
>> Date: Sat, Jun 1, 2019 at 7:37 PM
>> Subject: Re: Missing podling logos
>> To: 
>>
>>
>> Hi,
>>
>> It’s good to see some podling have added their logos, but we’re still
>> missing a few.
>>
>> Missing logo are:
>> amaterasu
>> annotator
>> batchee
>> brpc
>> datasketches
>> dlab
>> flagon
>> gobblin
>> hudi
>> omid
>> pinot
>> s2graph
>> samoa
>> sdap
>> tuweni
>> tvm
>> weex
>> zipkin
>>
>> With some conferences coming up there's going to be stickers made and
>> we'll
>> need your logo there for that to happen.
>>
>> Thanks,
>> Justin
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>

Re: Missing podling logos

[Seunghyun Lee]

I have uploaded our logo to
https://svn.apache.org/repos/asf/comdev/project-logos/originals/

I followed the instruction from http://www.apache.org/logos/about.html

Does this need some time to get propagated to the logo page?

Seunghyun

On Mon, Jun 3, 2019 at 11:04 PM Felix Cheung 
wrote:

> http://www.apache.org/logos/
>
> 
> From: Subbu Subramaniam 
> Sent: Monday, June 3, 2019 9:00 AM
> To: dev@pinot.apache.org
> Subject: Re: Missing podling logos
>
> Thanks for the reminder Felix.
>
> Where exactly do we add the logo? We do have one in this page:
>
> https://pinot.incubator.apache.org/
>
> thanks
>
> -Subbu
> 
> From: Felix Cheung 
> Sent: Sunday, June 2, 2019 11:51 AM
> To: dev@pinot.apache.org
> Subject: Fwd: Missing podling logos
>
> Quick reminder...
>
> -- Forwarded message -
> From: Justin Mclean 
> Date: Sat, Jun 1, 2019 at 7:37 PM
> Subject: Re: Missing podling logos
> To: 
>
>
> Hi,
>
> It’s good to see some podling have added their logos, but we’re still
> missing a few.
>
> Missing logo are:
> amaterasu
> annotator
> batchee
> brpc
> datasketches
> dlab
> flagon
> gobblin
> hudi
> omid
> pinot
> s2graph
> samoa
> sdap
> tuweni
> tvm
> weex
> zipkin
>
> With some conferences coming up there's going to be stickers made and we'll
> need your logo there for that to happen.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

Fwd: Podling PPMC members and mentors not signed up to private lists

[Seunghyun Lee]

If you're PPMC of Pinot project, please sign up for podling private list.

-- Forwarded message -
From: Justin Mclean 
Date: Thu, May 9, 2019 at 9:33 PM
Subject: Podling PPMC members and mentors not signed up to private lists
To: 


Hi,

A number of podlings mentors and PPMC members are not signed up to their
podling private lists.

If you are a mentor of a project listed below can you please remind your
PPMC members to sign up to the private list and ensure that yourself or
other mentors are signed up to your podlings private list.

Important emails get sent to the podlings private email lists and as a PPMC
member you really need to be signed up to it so you don’t miss them. I know
there may be reasons for this not happening, as some people only use
lists.apache.org and there may be people who were on an initial PPMC that
didn’t get involved or your podling may just be starting out.

If your project is approaching graduation I’d especially suggest you try
and fix this.

The number of missing signups here may indicate that there’s an issue e.g.
It may be that mentors are not active or not all PPMC members are actively
involved or it could be just an on-boarding issue of new PPMC members for
the podling or an initial steppe step that was skipped. Whatever it is it
wold be good to see more mentors and PPMC members signed up.
- Amaterasu - One mentor not signed up to private list and no PPMC member
signed up [1]
- Annotator  - Two mentors not signed up  and one PPMC member not signed up
[2]
- Datasketches - Five PPMC members not signed up [6]
- Flagon - Two mentors not signed up and three PPMC members not signed up
[13]
- Hivemall - Two mentors not signed up [15]
- Iceberg - One mentor not signed dup and all PPMC not signed up [17]
- MXNet - Thirteen PPMC members not signed up. [22]
- Nemo - Seven PPMC members not signed up. [24]
- Openwisk - Six PPMC members not signed up [26]
- Piont - One mentor not signed up and ten PPMC members not signed up. [28]
- Ratis - One mentor and five PPMC members not signed up. [30]
- Soma - Two mentors not signed up. [33]
- SDAP - Two mentors not signed up and eight PPMC members not signed up,
[34]
- Spot - Thirteen PPMC members not signed up. [37]
- Taverna - Two mentors and five PPMC members not signed up. [40]
- Training - Five PPMC members not signed up. [43]
- Tuweni - Six PPMC members not signed up. [44]

These are less concerning, but it would be nice to see all mentors signed
up:
- BatchEE - One mentor not signed up and four PPMC members not signed up [3]
- Crail - Three PPMC not signed up [4]
- Dories - One mentor not signed up and one PMC member not signed up. [8]
- Druid - Four PPMC members not signed up [9]
- Dubbo - Four PPMC members not signed up [10]
- ECharts - Four PPMC members not signed up [11]
- Goblin - One mentor not signed up and two PPMC members not signed up. [14]
- Hudi - One mentor not signed up and one PPMC mentor not signed dup. [16]
- Livy - One mentor not signed up and one PPMC member not signed dup. [19]
- Omid - One mentor not signed up. [25]
- Superset - One mentor and one PPMc member not signed up. [38]
- Tamaya - One mentor and two PPMC members not signed up. [39]
- Tephra - One mentor and one PPMC member not signed up. [41]
- Shardingsphere - One mentor not signed up. [35]
- Singa - One mentor and one PPMC member not signed up. [36]
- Week - One mentor and one PPMC member not signed up. [45]
- Zipkin - One mentor and four PPMC members not signed up. [48]

And these podlings are missing a couple of PPMC members:
- Daffodil - One PPMC member not signed up [5]
- Dlab - One PPMC member not signed up [7]
- Edgent - One PPMC member not signed up [12]
- IoTDB - Four PPMC members not signed up [18]
- Marvin-AI - Three PPMC members not signed up [20]
- Milagro - Two PPMC members not signed dup. [21]
- Myriad - Two PPMC members not signed up [23]
- PageSpeed - Two PPMC members not signed up. [27]
- PonyMail - Three PPMC members not signed up. [29]
- Rya -Three PPMC members not signed up. [31]
- S2Graph - One PPMC member not signed up [32]
- Toree - Two PPMC members not signed up.[42]
- Tvm - One PPMC member not signed up. [45]
- Warble - Two PPMC members not signed up. [47]

Thanks,
Justin

1. https://whimsy.apache.org/roster/ppmc/amaterasu
2. https://whimsy.apache.org/roster/ppmc/annotator
3. https://whimsy.apache.org/roster/ppmc/batchee
4. https://whimsy.apache.org/roster/ppmc/crail
5. https://whimsy.apache.org/roster/ppmc/daffodil
6. https://whimsy.apache.org/roster/ppmc/datasketches
7.  https://whimsy.apache.org/roster/ppmc/dlab
8. https://whimsy.apache.org/roster/ppmc/doris
9. https://whimsy.apache.org/roster/ppmc/druid
10. https://whimsy.apache.org/roster/ppmc/dubbo
11. https://whimsy.apache.org/roster/ppmc/echarts
12. https://whimsy.apache.org/roster/ppmc/edgent
13. https://whimsy.apache.org/roster/ppmc/flagon
14. https://whimsy.apache.org/roster/ppmc/gobblin
15. https://whimsy.apache.org/roster/ppmc/hivemall
16. 

Re: Apache Pinot Dev,uSer, Committer mailing lists

[Seunghyun Lee]

For now, we are using github issues for tracking items. We are considering
whether to move to jira later.

I added the "beginner-task" label on github
https://github.com/apache/incubator-pinot/labels

We can start to use this.

Thank you for suggestion.

Best,
Seunghyun

On Thu, Apr 18, 2019 at 1:22 PM Sai Boorlagadda 
wrote:

> Shall I create these items as github issues? (Or Apache JIRA or whichever
> the team is using) and I want some one to help me in labelling ones that
> are "good-first-issues".
>
> Sai
>
> On Wed, Mar 27, 2019 at 10:54 AM Subbu Subramaniam <
> ssubraman...@linkedin.com> wrote:
>
> > Hi Sai,
> >
> > At the end of the document on realtime indexing, there are many items
> that
> > we are inviting contributions on.
> >
> >
> >
> https://cwiki.apache.org/confluence/display/PINOT/Consuming+and+Indexing+rows+in+Realtime#ConsumingandIndexingrowsinRealtime-ContributionsWelcome
> >
> > You may want to start with simpler items first.
> >
> > -Subbu
> > --
> > *From:* Sai Boorlagadda 
> > *Sent:* Tuesday, March 26, 2019 8:49 PM
> > *To:* dev@pinot.apache.org
> > *Subject:* Re: Apache Pinot Dev,uSer, Committer mailing lists
> >
> > I am also interested to get involved and contribute to the community.
> > Do we have a roadmap of things that we want to do?
> >
> > On Tue, Mar 26, 2019 at 5:00 PM Seunghyun Lee  wrote:
> >
> > > Hi Sujay,
> > >
> > > Welcome to Pinot community. Please let us know if you have any question
> > or
> > > you want to discuss on Pinot
> > >
> > > Best,
> > > Seunghyun
> > >
> > > On Sun, Mar 24, 2019 at 4:31 AM sujay hegde  >
> > > wrote:
> > >
> > > > Hi Apache Pinot,
> > > >
> > > > I am interested in Apache Pinot Dev, user and Committer communities.
> > > >
> > > >
> > > > Thanks and Regards,
> > > > Sujay
> > > >
> > >
> >
>

Re: Big Data Meetup @ LinkedIn tomorrow at 5:30pm

[Seunghyun Lee]

Hi Sai,

Thank you for the follow up. I think that the video is not yet available on
public.

@Sunitha, Can you update Sai on the videos?

Best,
Seunghyun

On Thu, Apr 18, 2019 at 1:19 PM Sai Boorlagadda 
wrote:

> Hello Seunghyun,
>
> Have the meet up videos are uploaded to some channel?
>
> Sai
>
> On Tue, Mar 26, 2019 at 9:40 PM Seunghyun Lee  wrote:
>
> > I think that it will probably be recorded. Let me double check on this
> > tomorrow and will get back to you.
> >
> > On Tue, Mar 26, 2019 at 9:16 PM Sai Boorlagadda <
> sai.boorlaga...@gmail.com
> > >
> > wrote:
> >
> > > Is this streamed or recorded?
> > >
> > > On Tue, Mar 26, 2019 at 9:08 PM Seunghyun Lee 
> wrote:
> > >
> > > > Hi all,
> > > >
> > > > I just found that we have advertised on the website but not in the
> > > mailing
> > > > list about the meetup happening tomorrow.
> > > >
> > > > LinkedIn is hosting a Big Data Meet Up(focused on Pinot and Presto)
> on
> > > Mar
> > > > 27 from 5:30PM - 9:00 PM. Come join us and learn about the different
> > OLAP
> > > > systems that are powering companies like LinkedIn, Facebook, Uber and
> > > > Slack.
> > > >
> > > > Please RSVP using the link below:
> > > >
> > > > https://superchargedolap.splashthat.com
> > > >
> > > > Best,
> > > > Seunghyun
> > > >
> > >
> >
>

Re: Big Data Meetup @ LinkedIn tomorrow at 5:30pm

[Seunghyun Lee]

I think that it will probably be recorded. Let me double check on this
tomorrow and will get back to you.

On Tue, Mar 26, 2019 at 9:16 PM Sai Boorlagadda 
wrote:

> Is this streamed or recorded?
>
> On Tue, Mar 26, 2019 at 9:08 PM Seunghyun Lee  wrote:
>
> > Hi all,
> >
> > I just found that we have advertised on the website but not in the
> mailing
> > list about the meetup happening tomorrow.
> >
> > LinkedIn is hosting a Big Data Meet Up(focused on Pinot and Presto) on
> Mar
> > 27 from 5:30PM - 9:00 PM. Come join us and learn about the different OLAP
> > systems that are powering companies like LinkedIn, Facebook, Uber and
> > Slack.
> >
> > Please RSVP using the link below:
> >
> > https://superchargedolap.splashthat.com
> >
> > Best,
> > Seunghyun
> >
>

Re: Apache Pinot Dev,uSer, Committer mailing lists

[Seunghyun Lee]

Thank you for your interest in contributing to Pinot!

I think that you can start to read documentation and get familiarized with
the code base. https://pinot.readthedocs.io/en/latest/dev_guide.html

Also, please join to slack channel using the below link.
https://join.slack.com/t/apache-pinot/shared_invite/enQtNDY4NDczOTYyNjk1LTExODVjY2QxYzBkMzJjNTk0ZGQ3NThiYTU2YzdlNjE0MWI5ZjUwYjI2ZTgxNjNiYWJiNmEzYjkxMTIzMzUxNTQ

In terms of the roadmap, some major features that we are currently working
are:
1. segment merge service
2. HCON based configs
3. distributed controllers

I think that other people can add more information about the roadmap. If
you have some ideas on new features, feel free to suggest and we can
discuss.

Also, if you happen to live in bay area, please join to the meetup
tomorrow. Most of contributors will be there :)
https://superchargedolap.splashthat.com

Best,
Seunghyun


On Tue, Mar 26, 2019 at 8:50 PM Sai Boorlagadda 
wrote:

> I am also interested to get involved and contribute to the community.
> Do we have a roadmap of things that we want to do?
>
> On Tue, Mar 26, 2019 at 5:00 PM Seunghyun Lee  wrote:
>
> > Hi Sujay,
> >
> > Welcome to Pinot community. Please let us know if you have any question
> or
> > you want to discuss on Pinot
> >
> > Best,
> > Seunghyun
> >
> > On Sun, Mar 24, 2019 at 4:31 AM sujay hegde 
> > wrote:
> >
> > > Hi Apache Pinot,
> > >
> > > I am interested in Apache Pinot Dev, user and Committer communities.
> > >
> > >
> > > Thanks and Regards,
> > > Sujay
> > >
> >
>

Big Data Meetup @ LinkedIn tomorrow at 5:30pm

[Seunghyun Lee]

Hi all,

I just found that we have advertised on the website but not in the mailing
list about the meetup happening tomorrow.

LinkedIn is hosting a Big Data Meet Up(focused on Pinot and Presto) on Mar
27 from 5:30PM - 9:00 PM. Come join us and learn about the different OLAP
systems that are powering companies like LinkedIn, Facebook, Uber and Slack.

Please RSVP using the link below:

https://superchargedolap.splashthat.com

Best,
Seunghyun

Re: Pinot VS Kafka Streams (or Spark SQL)

[Seunghyun Lee]

Hi Sai,

Thank you for the mail. Your understanding is correct.

Systems that you mentioned (Pinot, Kafka, Spark SQL) are built for
different purposes and they are all critical components when you need to
build the data analytics data pipeline.

Kafka is a pub-sub message delivering system that is usually used to build
the streaming data pipeline. Spark SQL is built to add SQL interface layer
on top of Spark. You can think it as one of offline OLAP query engines like
Hive or Presto that are used for computing complex ad-hoc queries over
large data.

Pinot aims to support "interactive" analytics use cases (e.g. dashboard,
site facing reporting - who's viewed my profile on LInkedIn) where latency
requirements are more strict than offline reporting use cases.

You mentioned that "I can write a consumer that processes events from a
stream and computes the needed analytic/metric and store it into a data
store to serve". This is basically what Pinot does (consuming data from a
stream, index it for serving, allow query interface)

Below links are some references that we have published to public. Please
let us know if you have any other question.

Best,
Seunghyun

cc.

LinkedIn Blog Posts
https://engineering.linkedin.com/analytics/real-time-analytics-massive-scale-pinot
https://engineering.linkedin.com/blog/2019/03/pinot-joins-apache-incubator

Slides
https://www.slideshare.net/jeanfrancoisim/intro-to-pinot-20160104
https://www.slideshare.net/seunghyunlee1460/pinot-realtime-olap-for-530-million-users-sigmod-2018-107394584

On Tue, Mar 26, 2019 at 3:46 PM Sai Boorlagadda 
wrote:

> Hello Devs,
>
> Is there any content or blog post to understand the difference between
> Pinot vs Kafka Streams (or Spark SQL)? At a high level after reading Pinot
> is actually bringing off-the-shelf components which otherwise data
> engineers have to write on top of KAFKA streams?
>
> I mean I can write a consumer that processes events from a stream and
> computes the needed analytic/metric and store it into a data store to
> serve. Though my application layer has to route the requests either to the
> streaming analytics datastore or batch analytics data store.
>
> So my understanding is Pinot abstracts these two things from the
> application. Is that correct?
> Sai
>

Re: Apache Pinot Dev,uSer, Committer mailing lists

[Seunghyun Lee]

Hi Sujay,

Welcome to Pinot community. Please let us know if you have any question or
you want to discuss on Pinot

Best,
Seunghyun

On Sun, Mar 24, 2019 at 4:31 AM sujay hegde 
wrote:

> Hi Apache Pinot,
>
> I am interested in Apache Pinot Dev, user and Committer communities.
>
>
> Thanks and Regards,
> Sujay
>

[ANNOUNCE] Apache Pinot (incubating) 0.1.0 released

[Seunghyun Lee]

Hello Pinot community,

We are pleased to announce that Apache Pinot (incubating) 0.1.0 is released!

The release can be downloaded at: https://pinot.apache.org/download

The release note is available at:
https://github.com/apache/incubator-pinot/releases

Best Regards,
Seunghyun

Fwd: Mentor sign off on reports due Tuesday March 12

[Seunghyun Lee]

Hi mentors,

Would you help us on signing off the March report?

It seems that the deadline is due Tuesday, March 12.

Best,
Seunghyun

-- Forwarded message -
From: Justin Mclean 
Date: Thu, Mar 7, 2019 at 2:48 PM
Subject: Mentor sign off on reports due Tuesday March 12
To: 


Hi,

A few days to go but currently we are missing signoff on these reports:
- Crail
- Druid
- Marvin-AI
- Myriad
- OpenWhisk
- Pinot
- Pony Mail
- Singa
- Tamaya

Congratulation to Omid, Tephra and Training for having all mentors sign off
the report.

Four codlings failed to report and will be asked to report next month. They
are:
- Iceberg
- Spot
- Taverna
- Warble

Thanks,
Justin



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Pinot Incubator PMC report for March 2019 has been updated

[Seunghyun Lee]

Hi all,

I have updated the incubator PMC report for Pinot for March 2019.
https://wiki.apache.org/incubator/March2019

Can someone go over the report and provide me a feedback?

Best,
Seunghyun

Re: [VOTE] Apache Pinot (incubating) 0.1.0 RC0

[Seunghyun Lee]

We plan to move forward by mid next week. We are currently working on some
extra validation of this release on our production cluster.

Best,
Seunghyun

On Fri, Feb 22, 2019 at 1:04 PM Felix Cheung 
wrote:

> Hi, what’s the next step on this?
>
>
> 
> From: Sunitha Beeram 
> Sent: Tuesday, February 19, 2019 5:11 PM
> To: Seunghyun Lee; dev@pinot.apache.org
> Subject: Re: [VOTE] Apache Pinot (incubating) 0.1.0 RC0
>
> +1
>
>
> Checked out the code on Linux and verified the steps. (Had a few wiki
> updates that I mentioned to Seunghyun Lee offline)
>
> 
> From: Subbu Subramaniam 
> Sent: Tuesday, February 19, 2019 4:12:28 PM
> To: Seunghyun Lee; dev@pinot.apache.org
> Subject: Re: [VOTE] Apache Pinot (incubating) 0.1.0 RC0
>
> +1 All checked out after the key was fixed.
>
> Some suggestions:
>
> * We should add verification for realtime also.
> * We should verify from binary distribution rather than the src that has
> been built? (not sure about this)
>
> Otherwise, lgtm
>
> -Subbu
> 
> From: Seunghyun Lee 
> Sent: Tuesday, February 19, 2019 1:54 PM
> To: dev@pinot.apache.org
> Subject: Re: [VOTE] Apache Pinot (incubating) 0.1.0 RC0
>
> By the way, there actually was an issue with KEYS file. I fixed that as
> well. Thanks for pointing it out :)
>
> Best,
> Seunghyun
>
>
> On Mon, Feb 18, 2019 at 9:43 PM Seunghyun Lee  wrote:
>
> > Hi Felix,
> >
> > Thanks for the detailed feedback. From the next release, I will make sure
> > to use 4096 bits key.
> >
> > I have modified the wiki page for those 2 points. Regarding importing
> KEYS
> > file, I have tried with my personal laptop and it works fine with it.
> >
> > Can other people comment on importing KEYS file while validating a
> release?
> >
> > Best,
> > Seunghyun
> >
> > On Fri, Feb 15, 2019 at 10:44 PM Felix Cheung  >
> > wrote:
> >
> >> +1
> >>
> >> All checked out - please see note on key and wiki.
> >> Thanks for putting this together.
> >>
> >> Note - ideally, signing key should be 4096 bits
> >> https://www.apache.org/dev/release-signing.html#note
> >> checked license headers
> >> compiled from source, ran tests, demo
> >> checked name includes incubating
> >> checked DISCLAIMER, LICENSE and NOTICE
> >> checked signature and hashes
> >> checked no unexpected binary files
> >>
> >>
> >> For some reason I wasn't able to import from KEYS file correctly:
> >>
> >> $ cat KEYS
> >> pub rsa2048 2019-02-01 [SC] [expires: 2021-01-31]
> >> FD534854D542FD474278B85344BA03AD164D961B
> >> uid [ultimate] Seunghyun Lee 
> >> sig 3 44BA03AD164D961B 2019-02-01 Seunghyun Lee 
> >> sub rsa2048 2019-02-01 [E] [expires: 2021-01-31]
> >> sig 44BA03AD164D961B 2019-02-01 Seunghyun Lee 
> >>
> >> -BEGIN PGP PUBLIC KEY BLOCK-
> >> ...
> >> -END PGP PUBLIC KEY BLOCK-
> >>
> >> $ gpg --import KEYS
> >> gpg: key 6E106A1A5681D67E: public key "Seunghyun Lee <
> sn...@linkedin.com>"
> >> imported
> >> gpg: Total number processed: 1
> >> gpg: imported: 1
> >>
> >> # Note - the wrong key is imported!
> >> # Whereas this works
> >>
> >> $ gpg --recv-keys FD534854D542FD474278B85344BA03AD164D961B
> >> gpg: key 44BA03AD164D961B: public key "Seunghyun Lee  >"
> >> imported
> >> gpg: Total number processed: 1
> >> gpg: imported: 1
> >>
> >>
> >> Note -
> >> about the wiki
> >>
> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
> >>
> >> 1. Download the release candidate
> >> - FYI this can also be done via http,
> >>
> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.1.0-rc0/apache-pinot-incubating-0.1.0-src.tar.gz
> >>
> >> 2. demo
> >> cd pinot-distribution/target/apache-pinot-incubating-x.x.x-bin
> >>
> >> seems like should be
> >> cd
> >>
> pinot-distribution/target/apache-pinot-incubating-0.1.0-bin/apache-pinot-incubating-0.1.0-bin
> >>
> >>
> >>
> >> 
> >> From: Seunghyun Lee 
> >> Sent: Thursday, February 14, 2019 10:46 PM
> >> To: dev@pinot.apache.org
> >> Subject: [VOTE] Apache Pinot (incubating) 0.1.0

Re: [VOTE] Apache Pinot (incubating) 0.1.0 RC0

[Seunghyun Lee]

By the way, there actually was an issue with KEYS file. I fixed that as
well. Thanks for pointing it out :)

Best,
Seunghyun


On Mon, Feb 18, 2019 at 9:43 PM Seunghyun Lee  wrote:

> Hi Felix,
>
> Thanks for the detailed feedback. From the next release, I will make sure
> to use 4096 bits key.
>
> I have modified the wiki page for those 2 points. Regarding importing KEYS
> file, I have tried with my personal laptop and it works fine with it.
>
> Can other people comment on importing KEYS file while validating a release?
>
> Best,
> Seunghyun
>
> On Fri, Feb 15, 2019 at 10:44 PM Felix Cheung 
> wrote:
>
>> +1
>>
>> All checked out - please see note on key and wiki.
>> Thanks for putting this together.
>>
>> Note - ideally, signing key should be 4096 bits
>> https://www.apache.org/dev/release-signing.html#note
>> checked license headers
>> compiled from source, ran tests, demo
>> checked name includes incubating
>> checked DISCLAIMER, LICENSE and NOTICE
>> checked signature and hashes
>> checked no unexpected binary files
>>
>>
>> For some reason I wasn't able to import from KEYS file correctly:
>>
>> $ cat KEYS
>> pub rsa2048 2019-02-01 [SC] [expires: 2021-01-31]
>> FD534854D542FD474278B85344BA03AD164D961B
>> uid [ultimate] Seunghyun Lee 
>> sig 3 44BA03AD164D961B 2019-02-01 Seunghyun Lee 
>> sub rsa2048 2019-02-01 [E] [expires: 2021-01-31]
>> sig 44BA03AD164D961B 2019-02-01 Seunghyun Lee 
>>
>> -BEGIN PGP PUBLIC KEY BLOCK-
>> ...
>> -END PGP PUBLIC KEY BLOCK-
>>
>> $ gpg --import KEYS
>> gpg: key 6E106A1A5681D67E: public key "Seunghyun Lee "
>> imported
>> gpg: Total number processed: 1
>> gpg: imported: 1
>>
>> # Note - the wrong key is imported!
>> # Whereas this works
>>
>> $ gpg --recv-keys FD534854D542FD474278B85344BA03AD164D961B
>> gpg: key 44BA03AD164D961B: public key "Seunghyun Lee "
>> imported
>> gpg: Total number processed: 1
>> gpg: imported: 1
>>
>>
>> Note -
>> about the wiki
>> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
>>
>> 1. Download the release candidate
>> - FYI this can also be done via http,
>> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.1.0-rc0/apache-pinot-incubating-0.1.0-src.tar.gz
>>
>> 2. demo
>> cd pinot-distribution/target/apache-pinot-incubating-x.x.x-bin
>>
>> seems like should be
>> cd
>> pinot-distribution/target/apache-pinot-incubating-0.1.0-bin/apache-pinot-incubating-0.1.0-bin
>>
>>
>>
>> 
>> From: Seunghyun Lee 
>> Sent: Thursday, February 14, 2019 10:46 PM
>> To: dev@pinot.apache.org
>> Subject: [VOTE] Apache Pinot (incubating) 0.1.0 RC0
>>
>> Hi Pinot Community,
>>
>> This is a call for vote to the release Apache Pinot (incubating) version
>> 0.1.0.
>>
>> The release candidate:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.1.0-rc0
>>
>> Git tag for this release:
>> https://github.com/apache/incubator-pinot/tree/release-0.1.0-rc0
>>
>> Git hash for this release:
>> bbf29dc6e0f23383948f0db66565ebbdf383dd0d
>>
>> The artifacts have been signed with key: 44BA03AD164D961B, which can be
>> found in the following KEYS file.
>> https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS
>>
>> Release notes:
>> https://github.com/apache/incubator-pinot/releases/tag/release-0.1.0-rc0
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachepinot-1002
>>
>> Documentation on verifying a release candidate:
>>
>> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
>>
>>
>> The vote will be open for at least 72 hours or until necessary number of
>> votes are reached.
>>
>> Please vote accordingly,
>>
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove with the reason
>>
>> Thanks,
>> Apache Pinot (incubating) team
>>
>

Re: [VOTE] Apache Pinot (incubating) 0.1.0 RC0

[Seunghyun Lee]

Hi Felix,

Thanks for the detailed feedback. From the next release, I will make sure
to use 4096 bits key.

I have modified the wiki page for those 2 points. Regarding importing KEYS
file, I have tried with my personal laptop and it works fine with it.

Can other people comment on importing KEYS file while validating a release?

Best,
Seunghyun

On Fri, Feb 15, 2019 at 10:44 PM Felix Cheung 
wrote:

> +1
>
> All checked out - please see note on key and wiki.
> Thanks for putting this together.
>
> Note - ideally, signing key should be 4096 bits
> https://www.apache.org/dev/release-signing.html#note
> checked license headers
> compiled from source, ran tests, demo
> checked name includes incubating
> checked DISCLAIMER, LICENSE and NOTICE
> checked signature and hashes
> checked no unexpected binary files
>
>
> For some reason I wasn't able to import from KEYS file correctly:
>
> $ cat KEYS
> pub rsa2048 2019-02-01 [SC] [expires: 2021-01-31]
> FD534854D542FD474278B85344BA03AD164D961B
> uid [ultimate] Seunghyun Lee 
> sig 3 44BA03AD164D961B 2019-02-01 Seunghyun Lee 
> sub rsa2048 2019-02-01 [E] [expires: 2021-01-31]
> sig 44BA03AD164D961B 2019-02-01 Seunghyun Lee 
>
> -BEGIN PGP PUBLIC KEY BLOCK-
> ...
> -END PGP PUBLIC KEY BLOCK-
>
> $ gpg --import KEYS
> gpg: key 6E106A1A5681D67E: public key "Seunghyun Lee "
> imported
> gpg: Total number processed: 1
> gpg: imported: 1
>
> # Note - the wrong key is imported!
> # Whereas this works
>
> $ gpg --recv-keys FD534854D542FD474278B85344BA03AD164D961B
> gpg: key 44BA03AD164D961B: public key "Seunghyun Lee "
> imported
> gpg: Total number processed: 1
> gpg: imported: 1
>
>
> Note -
> about the wiki
> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
>
> 1. Download the release candidate
> - FYI this can also be done via http,
> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.1.0-rc0/apache-pinot-incubating-0.1.0-src.tar.gz
>
> 2. demo
> cd pinot-distribution/target/apache-pinot-incubating-x.x.x-bin
>
> seems like should be
> cd
> pinot-distribution/target/apache-pinot-incubating-0.1.0-bin/apache-pinot-incubating-0.1.0-bin
>
>
>
> 
> From: Seunghyun Lee 
> Sent: Thursday, February 14, 2019 10:46 PM
> To: dev@pinot.apache.org
> Subject: [VOTE] Apache Pinot (incubating) 0.1.0 RC0
>
> Hi Pinot Community,
>
> This is a call for vote to the release Apache Pinot (incubating) version
> 0.1.0.
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.1.0-rc0
>
> Git tag for this release:
> https://github.com/apache/incubator-pinot/tree/release-0.1.0-rc0
>
> Git hash for this release:
> bbf29dc6e0f23383948f0db66565ebbdf383dd0d
>
> The artifacts have been signed with key: 44BA03AD164D961B, which can be
> found in the following KEYS file.
> https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS
>
> Release notes:
> https://github.com/apache/incubator-pinot/releases/tag/release-0.1.0-rc0
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachepinot-1002
>
> Documentation on verifying a release candidate:
>
> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
>
>
> The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
>
> Please vote accordingly,
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> Apache Pinot (incubating) team
>

[VOTE] Apache Pinot (incubating) 0.1.0 RC0

[Seunghyun Lee]

Hi Pinot Community,

This is a call for vote to the release Apache Pinot (incubating) version
0.1.0.

The release candidate:
https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.1.0-rc0

Git tag for this release:
https://github.com/apache/incubator-pinot/tree/release-0.1.0-rc0

Git hash for this release:
bbf29dc6e0f23383948f0db66565ebbdf383dd0d

The artifacts have been signed with key: 44BA03AD164D961B, which can be
found in the following KEYS file.
https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS

Release notes:
https://github.com/apache/incubator-pinot/releases/tag/release-0.1.0-rc0

Staging repository:
https://repository.apache.org/content/repositories/orgapachepinot-1002

Documentation on verifying a release candidate:
https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate


The vote will be open for at least 72 hours or until necessary number of
votes are reached.

Please vote accordingly,

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Thanks,
Apache Pinot (incubating) team

Re: Can we blacklist the mails from GitBox for dev mailing list?

[Seunghyun Lee]

I somehow missed this. I filed the ticket to INFRA.
https://issues.apache.org/jira/browse/INFRA-17855

Best,
Seunghyun

On Sat, Feb 2, 2019 at 9:54 AM Felix Cheung 
wrote:

> This hasn’t changed, I think.
>
> Seunghyun, you can open a JIRA on INFRA to request that.
>
>
> ------
> *From:* Seunghyun Lee 
> *Sent:* Wednesday, January 30, 2019 10:25 PM
> *To:* Daniel Gruno
> *Cc:* us...@infra.apache.org; dev@pinot.apache.org
> *Subject:* Re: Can we blacklist the mails from GitBox for dev mailing
> list?
>
> We do have com...@pinot.apache.org, which is already getting a lot of
> mails
> for commits to the repository. How about moving it there?
>
> On Wed, Jan 30, 2019 at 10:12 PM Daniel Gruno 
> wrote:
>
> > On 1/31/19 7:04 AM, Seunghyun Lee wrote:
> > > Hi Apache infra team,
> > >
> > > I'm Seunghyun who's working on Pinot incubating project. We are getting
> > > a lot of spam mails from GitBox on all changes in Github and this makes
> > > the mail archive hard to find the useful discussion. Can we blacklist
> > > GitBox from sending mails to dev@pinot.apache.org
> > > <mailto:dev@pinot.apache.org>?
> >
> > No, but you could set up a new mailing list just for PRs/issues and have
> > it moved there.
> >
> > >
> > > Please refer tot he following mailing list.
> > > https://lists.apache.org/list.html?dev@pinot.apache.org
> > >
> > > Best,
> > > Seunghyun
> >
> >
>

Re: Failing on deploying artifacts

[Seunghyun Lee]

Hi Felix,

I actually was following the same documentation; however, I somehow missed
the very first step (filing the ticket for setting up the repository before
publishing)

Thank you!

Seunghyun

On Tue, Feb 12, 2019 at 8:54 PM Felix Cheung 
wrote:

> Also are you able to login to nexus yourself?
>
> http://repository.apache.org/
>
> I found easier as the place to find more info of the upload.
>
> And setup steps are documented here
> http://www.apache.org/dev/publishing-maven-artifacts.html
>
>
> 
> From: Felix Cheung 
> Sent: Tuesday, February 12, 2019 8:39 PM
> To: dev@pinot.apache.org; dev@pinot.apache.org
> Subject: Re: Failing on deploying artifacts
>
> Ah good. Is this documented as a step somewhere? (Just want to see if this
> needs to be clarified)
>
>
> 
> From: Seunghyun Lee 
> Sent: Tuesday, February 12, 2019 7:14 PM
> To: dev@pinot.apache.org
> Subject: Re: Failing on deploying artifacts
>
> This was because I haven't set up the access to nexus yet. I have filed the
> ticket to INFRA https://issues.apache.org/jira/browse/INFRA-17840
>
> Best,
> Seunghyun
>
> On Tue, Feb 12, 2019 at 6:10 PM Seunghyun Lee  wrote:
>
> > Hi mentors,
> >
> > I am trying to upload our artifacts to Nexus staging repository. I was
> > following the apache document. Have set up "~/.m2/settings.xml" file
> > correctly. Since the job fails after uploading the "pinot-0.1.0.pom"
> file,
> > I think that it's not the authentication issue.
> >
> > When I run "mvn release:perform", I get the following error:
> >
> > [INFO] [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @
> > pinot ---
> > [INFO] Uploading:
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/pinot/pinot/0.1.0/pinot-0.1.0.pom
> > [INFO] Progress (1): 2.0/45 kB
> > [INFO] Progress (1): 4.1/45 kB
> > [INFO] Progress (1): 6.1/45 kB
> > [INFO] Progress (1): 8.2/45 kB
> > [INFO]
> > 
> >
> > ~/workspace/pinot 0.1.0
> > [INFO] [INFO] Total time: 6.280 s
> > [INFO] [INFO] Finished at: 2019-02-12T18:05:20-08:00
> > [INFO] [INFO] Final Memory: 44M/1168M
> > [INFO] [INFO]
> > 
> > [INFO] [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
> (default-deploy)
> > on project pinot: Failed to deploy artifacts: Could not transfer artifact
> > org.apache.pinot:pinot:pom:0.1.0 from/to apache.releases.https (
> > https://repository.apache.org/service/local/staging/deploy/maven2):
> *Failed
> > to transfer file:
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/pinot/pinot/0.1.0/pinot-0.1.0.pom
> > <
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/pinot/pinot/0.1.0/pinot-0.1.0.pom
> >.
> > Return code is: 400, ReasonPhrase: Bad Request. *-> [Help 1]
> > [INFO] [ERROR]
> > [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven
> > with the -e switch.
> > [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug
> > logging.
> > [INFO] [ERROR]
> > [INFO] [ERROR] For more information about the errors and possible
> > solutions, please read the following articles:
> > [INFO] [ERROR] [Help 1]
> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> >
> > Is someone familiar with maven-release tool and have face about this
> > issue? I have spent hours on googling but haven't found the good solution
> > yet.
> >
> > Best,
> > Seunghyun
> >
>

Re: Failing on deploying artifacts

[Seunghyun Lee]

This was because I haven't set up the access to nexus yet. I have filed the
ticket to INFRA https://issues.apache.org/jira/browse/INFRA-17840

Best,
Seunghyun

On Tue, Feb 12, 2019 at 6:10 PM Seunghyun Lee  wrote:

> Hi mentors,
>
> I am trying to upload our artifacts to Nexus staging repository. I was
> following the apache document. Have set up "~/.m2/settings.xml" file
> correctly. Since the job fails after uploading the "pinot-0.1.0.pom" file,
> I think that it's not the authentication issue.
>
> When I run "mvn release:perform", I get the following error:
>
> [INFO] [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @
> pinot ---
> [INFO] Uploading:
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/pinot/pinot/0.1.0/pinot-0.1.0.pom
> [INFO] Progress (1): 2.0/45 kB
> [INFO] Progress (1): 4.1/45 kB
> [INFO] Progress (1): 6.1/45 kB
> [INFO] Progress (1): 8.2/45 kB
> [INFO]
> 
>
> ~/workspace/pinot 0.1.0
> [INFO] [INFO] Total time: 6.280 s
> [INFO] [INFO] Finished at: 2019-02-12T18:05:20-08:00
> [INFO] [INFO] Final Memory: 44M/1168M
> [INFO] [INFO]
> 
> [INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy)
> on project pinot: Failed to deploy artifacts: Could not transfer artifact
> org.apache.pinot:pinot:pom:0.1.0 from/to apache.releases.https (
> https://repository.apache.org/service/local/staging/deploy/maven2): *Failed
> to transfer file:
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/pinot/pinot/0.1.0/pinot-0.1.0.pom
> <https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/pinot/pinot/0.1.0/pinot-0.1.0.pom>.
> Return code is: 400, ReasonPhrase: Bad Request. *-> [Help 1]
> [INFO] [ERROR]
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven
> with the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug
> logging.
> [INFO] [ERROR]
> [INFO] [ERROR] For more information about the errors and possible
> solutions, please read the following articles:
> [INFO] [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>
> Is someone familiar with maven-release tool and have face about this
> issue? I have spent hours on googling but haven't found the good solution
> yet.
>
> Best,
> Seunghyun
>

Failing on deploying artifacts

[Seunghyun Lee]

Hi mentors,

I am trying to upload our artifacts to Nexus staging repository. I was
following the apache document. Have set up "~/.m2/settings.xml" file
correctly. Since the job fails after uploading the "pinot-0.1.0.pom" file,
I think that it's not the authentication issue.

When I run "mvn release:perform", I get the following error:

[INFO] [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ pinot
---
[INFO] Uploading:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/pinot/pinot/0.1.0/pinot-0.1.0.pom
[INFO] Progress (1): 2.0/45 kB
[INFO] Progress (1): 4.1/45 kB
[INFO] Progress (1): 6.1/45 kB
[INFO] Progress (1): 8.2/45 kB
[INFO]


~/workspace/pinot 0.1.0
[INFO] [INFO] Total time: 6.280 s
[INFO] [INFO] Finished at: 2019-02-12T18:05:20-08:00
[INFO] [INFO] Final Memory: 44M/1168M
[INFO] [INFO]

[INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy)
on project pinot: Failed to deploy artifacts: Could not transfer artifact
org.apache.pinot:pinot:pom:0.1.0 from/to apache.releases.https (
https://repository.apache.org/service/local/staging/deploy/maven2): *Failed
to transfer file:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/pinot/pinot/0.1.0/pinot-0.1.0.pom
.
Return code is: 400, ReasonPhrase: Bad Request. *-> [Help 1]
[INFO] [ERROR]
[INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[INFO] [ERROR] Re-run Maven using the -X switch to enable full debug
logging.
[INFO] [ERROR]
[INFO] [ERROR] For more information about the errors and possible
solutions, please read the following articles:
[INFO] [ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Is someone familiar with maven-release tool and have face about this issue?
I have spent hours on googling but haven't found the good solution yet.

Best,
Seunghyun

Re: [MENTORS] Unapproved releases

[Seunghyun Lee]

I removed those from github release page.

Best,
Seunghyun

On Fri, Feb 8, 2019 at 5:05 PM Seunghyun Lee  wrote:

> Sorry for this. I was trying out the maven-release plugin (first time to
> use this plugin) and this got automatically created. I will probably go
> with an option of doing it manually.
>
> I will clean up these.
>
> Best,
> Seunghyun
>
> On Fri, Feb 8, 2019 at 4:56 PM Felix Cheung 
> wrote:
>
>> I think this happens automatically by GitHub when a git tag is pushed?
>>
>>
>> 
>> From: kishore g 
>> Sent: Friday, February 8, 2019 3:34 PM
>> To: dev@pinot.apache.org
>> Subject: Re: [MENTORS] Unapproved releases
>>
>> Thanks Justin. I will take a look at it. Olivier, we might need your
>> expertise here.
>>
>> On Fri, Feb 8, 2019 at 2:24 PM Justin Mclean  wrote:
>>
>> > Hi,
>> >
>> > Sorry to bother you again, but It seems this is not sinking in. I can
>> see
>> > you have just marked a release candidate as a release here. [1] Mentors
>> can
>> > you please deal with this.
>> >
>> > Thanks,
>> > Justin
>> >
>> > 1. https://github.com/apache/incubator-pinot/releases
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
>> > For additional commands, e-mail: dev-h...@pinot.apache.org
>> >
>> >
>>
>

Re: [MENTORS] Unapproved releases

[Seunghyun Lee]

Sorry for this. I was trying out the maven-release plugin (first time to
use this plugin) and this got automatically created. I will probably go
with an option of doing it manually.

I will clean up these.

Best,
Seunghyun

On Fri, Feb 8, 2019 at 4:56 PM Felix Cheung 
wrote:

> I think this happens automatically by GitHub when a git tag is pushed?
>
>
> 
> From: kishore g 
> Sent: Friday, February 8, 2019 3:34 PM
> To: dev@pinot.apache.org
> Subject: Re: [MENTORS] Unapproved releases
>
> Thanks Justin. I will take a look at it. Olivier, we might need your
> expertise here.
>
> On Fri, Feb 8, 2019 at 2:24 PM Justin Mclean  wrote:
>
> > Hi,
> >
> > Sorry to bother you again, but It seems this is not sinking in. I can see
> > you have just marked a release candidate as a release here. [1] Mentors
> can
> > you please deal with this.
> >
> > Thanks,
> > Justin
> >
> > 1. https://github.com/apache/incubator-pinot/releases
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
> > For additional commands, e-mail: dev-h...@pinot.apache.org
> >
> >
>

Fwd: Mentor sign-off due next Tuesday (February 12th)

[Seunghyun Lee]

Dear Mentors,

Can we get the sign-offs for our podling reports? It seems that it's due
next Tuesday.

Best,
Seunghyun

-- Forwarded message -
From: Justin Mclean 
Date: Wed, Feb 6, 2019 at 2:44 PM
Subject: Mentor sign-off due next Tuesday (February 12th)
To: 


Hi,

Mentor sign-off of the podling reports is due next Tuesday.

So far these projects don’t have any sign-offs:
- BRPC (missing report)
- Doris
- ECharts
- Heron
- Pinot
- ShardingSphere
- Tamaya

Congratulations to SDAP where all mentors have signed off the report.

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: ASF Release process

[Seunghyun Lee]

Thank you for the reference!

After I go over the release process, I will come up with the similar
documentation for our project so that anyone who becomes the release
manager in the future can proceed.

Best,
Seunghyun

On Wed, Feb 6, 2019 at 11:14 AM Felix Cheung 
wrote:

> Sharing doc Chris has on the ASF release process
>
> http://plc4x.apache.org/developers/release.html
>
> Thanks Chris!
>

Re: Request for checking commits before creating a release candidate

[Seunghyun Lee]

Hi Felix,

I retried to build NOTICE file and get the same result for concatenated
NOTICE. I think that those are the part of old glassfish.jersey libraries.
If you confirm, I will go ahead of merging the pr.

Best,
Seunghyun

On Wed, Feb 6, 2019 at 10:08 AM Seunghyun Lee  wrote:

> I rebuilt NOTICE-binary file using the same approach and those were cut
> out. I will check that one more time and get back to you.
>
> Best,
> Seunghyun
>
> On Wed, Feb 6, 2019 at 12:46 AM Felix Cheung 
> wrote:
>
>> For #1 LG generally. What happened to the whole chunk of Apache ones
>> like Apache
>> Commons Net?
>>
>> #2 LGTM
>>
>> On Tue, Feb 5, 2019 at 9:59 PM Seunghyun Lee  wrote:
>>
>> > Hi Felix,
>> >
>> > Before we cut the release candidate, I have some remaining checks from
>> you.
>> >
>> > 1. Can you double check on the update for LICENSE-binary/NOTICE-binary
>> due
>> > to jersery version upgrade? (A lot of glassfish projects have been moved
>> > from CDDL to EPL 2.0.)
>> > https://github.com/apache/incubator-pinot/pull/3791
>> >
>> > 2. Can you also comment on my reply on the issue with removing
>> "*-binary"
>> > files/directories? (refer pinot-assembly.xml file)
>> > https://github.com/apache/incubator-pinot/pull/3772
>> >
>> > I really appreciate your help.
>> >
>> > Best,
>> > Seunghyun
>> >
>>
>

Re: Request for checking commits before creating a release candidate

[Seunghyun Lee]

I rebuilt NOTICE-binary file using the same approach and those were cut
out. I will check that one more time and get back to you.

Best,
Seunghyun

On Wed, Feb 6, 2019 at 12:46 AM Felix Cheung  wrote:

> For #1 LG generally. What happened to the whole chunk of Apache ones
> like Apache
> Commons Net?
>
> #2 LGTM
>
> On Tue, Feb 5, 2019 at 9:59 PM Seunghyun Lee  wrote:
>
> > Hi Felix,
> >
> > Before we cut the release candidate, I have some remaining checks from
> you.
> >
> > 1. Can you double check on the update for LICENSE-binary/NOTICE-binary
> due
> > to jersery version upgrade? (A lot of glassfish projects have been moved
> > from CDDL to EPL 2.0.)
> > https://github.com/apache/incubator-pinot/pull/3791
> >
> > 2. Can you also comment on my reply on the issue with removing "*-binary"
> > files/directories? (refer pinot-assembly.xml file)
> > https://github.com/apache/incubator-pinot/pull/3772
> >
> > I really appreciate your help.
> >
> > Best,
> > Seunghyun
> >
>

Request for checking commits before creating a release candidate

[Seunghyun Lee]

Hi Felix,

Before we cut the release candidate, I have some remaining checks from you.

1. Can you double check on the update for LICENSE-binary/NOTICE-binary due
to jersery version upgrade? (A lot of glassfish projects have been moved
from CDDL to EPL 2.0.)
https://github.com/apache/incubator-pinot/pull/3791

2. Can you also comment on my reply on the issue with removing "*-binary"
files/directories? (refer pinot-assembly.xml file)
https://github.com/apache/incubator-pinot/pull/3772

I really appreciate your help.

Best,
Seunghyun

Re: Requesting a review for updating license & notice information

[Seunghyun Lee]

Thank you for the update. So, I think that we have 2 options.

1. Copy all licenses directly to "LICENSE" file.
2. Copy all licenses to "/licenses" and add a pointer to LICENSE file.

In that case, I think the current pr should be good enough (I also
separated out LICENSE-binary and NOTICE-binary).
For a source code release, we plan to include the original LICENSE, NOTICE
while we will include LICENSE-binary, NOTICE-binary for binary release.

@Felix @Kishore Can you go over the finalized pr when you find the time?
Again, I really appreciate for your help.
https://github.com/apache/incubator-pinot/pull/3722

Best,
Seunghyun


On Wed, Jan 23, 2019 at 10:31 PM Felix Cheung 
wrote:

> Actually I’m going to retract the whole thing I said.
>
> Seems like it should carry it under license for:
>
> https://github.com/apache/spark/commit/bf4199e261c3c8dd2970e2a154c97b46fb339f02
>
> 
> From: Felix Cheung 
> Sent: Wednesday, January 23, 2019 9:20 PM
> To: dev@pinot.apache.org; dev@pinot.apache.org
> Subject: Re: Requesting a review for updating license & notice information
>
> Hi - I believe it’s ok not to include standard passive license too. I
> think I could some pointer on that in the PR where we discussed.
>
>
> 
> From: kishore g 
> Sent: Wednesday, January 23, 2019 9:18 PM
> To: dev@pinot.apache.org
> Subject: Re: Requesting a review for updating license & notice information
>
> I think that should work. Olivier, do you see any issues with that?
>
> On Wed, Jan 23, 2019 at 5:51 PM Seunghyun Lee  wrote:
>
> > Hi Felix and Kishore,
> >
> > Can you guys confirm that if I can remove copied license files for MIT,
> BSD
> > based on http://www.apache.org/dev/licensing-howto.html#permissive-deps
> ?
> >
> > My understanding from the above document is that for MIT, BSD
> dependencies,
> > it is sufficient to add pointers in LICENSE file.
> >
> > However, I'm a bit confused given that the example actually points the
> full
> > license
> >
> > This product bundles SuperWidget 1.2.3, which is available under a
> > "3-clause BSD" license. For details, see *deps/superwidget/.*
> >
> >
> > As long as we don't violate the license issue, I can go ahead of removing
> > copied license files in "/licenses" for MIT, BSD related libaries.
> >
> > Best,
> > Seunghyun
> >
> > On Fri, Jan 18, 2019 at 9:53 PM Felix Cheung 
> > wrote:
> >
> > > Thanks for doing that and sending this note.
> > >
> > > I will help check today.
> > >
> > >
> > >
> > > 
> > > From: Seunghyun Lee 
> > > Sent: Friday, January 18, 2019 3:42 PM
> > > To: dev@pinot.apache.org
> > > Subject: Requesting a review for updating license & notice information
> > >
> > > Hi Mentors,
> > >
> > > I have recently tracked down all dependencies that we bundle for our
> > > distribution and came up with license, notice files for Pinot project.
> I
> > > followed Apache Spark's approach since it provides the detailed
> > > documentation on how to build license, notice files.
> > >
> > > Can someone look into the following pull request so that we can have
> some
> > > initial feedbacks before we start to work on the release process?
> > > https://github.com/apache/incubator-pinot/pull/3722
> > >
> > > Best,
> > > Seunghyun
> > >
> >
>

Re: Requesting a review for updating license & notice information

[Seunghyun Lee]

Hi Felix and Kishore,

Can you guys confirm that if I can remove copied license files for MIT, BSD
based on http://www.apache.org/dev/licensing-howto.html#permissive-deps ?

My understanding from the above document is that for MIT, BSD dependencies,
it is sufficient to add pointers in LICENSE file.

However, I'm a bit confused given that the example actually points the full
license

This product bundles SuperWidget 1.2.3, which is available under a
"3-clause BSD" license.  For details, see *deps/superwidget/.*


As long as we don't violate the license issue, I can go ahead of removing
copied license files in "/licenses" for MIT, BSD related libaries.

Best,
Seunghyun

On Fri, Jan 18, 2019 at 9:53 PM Felix Cheung 
wrote:

> Thanks for doing that and sending this note.
>
> I will help check today.
>
>
>
> ________
> From: Seunghyun Lee 
> Sent: Friday, January 18, 2019 3:42 PM
> To: dev@pinot.apache.org
> Subject: Requesting a review for updating license & notice information
>
> Hi Mentors,
>
> I have recently tracked down all dependencies that we bundle for our
> distribution and came up with license, notice files for Pinot project. I
> followed Apache Spark's approach since it provides the detailed
> documentation on how to build license, notice files.
>
> Can someone look into the following pull request so that we can have some
> initial feedbacks before we start to work on the release process?
> https://github.com/apache/incubator-pinot/pull/3722
>
> Best,
> Seunghyun
>