Re: [VOTE] Apache Pinot 1.1.0 RC1

[Mayank Shrivastava]

+1 (binding)

> On Mar 16, 2024, at 9:38 AM, Subbu Subramaniam  wrote:
> 
> +1 (binding)
> 
> -Subbu Subramaniam
> Apache PMC
> 
>> On 2024/03/07 04:03:58 Vivek Iyer Vaidyanathan Iyer wrote:
>> Hi Pinot Community,
>> 
>> This is a call for a vote to release Apache Pinot 1.1.0
>> 
>> The release candidate:
>> https://dist.apache.org/repos/dist/dev/pinot/apache-pinot-1.1.0-rc1/
>> 
>> Git tag for this release:
>> https://github.com/apache/pinot/tree/release-1.1.0-rc1
>> 
>> Git hash for this release:
>> c2606742bbc4b15cff857eb0ffe7ec878ff181bb
>> 
>> The artifact has been signed with key: 1D2B6F73AEA25682, 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.1.0-rc1
>> 
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachepinot-1061/
>> 
>> 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
>> 
> 
> -
> 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: Apache pinot release 1.0.0 RC3 voting

[Mayank Shrivastava]

+1 [binding]

> On Sep 12, 2023, at 6:04 PM, Subbu Subramaniam  wrote:
> 
> Verified
> 
> +1 [Binding]
> 
> -Subbu Subramaniam
>  Apache Pinot PMC
> 
>> On 2023/09/12 10:02:26 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
>> 
> 
> -
> 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 0.12.1 RC0

[Mayank Shrivastava]

+1

On Thu, Mar 2, 2023 at 6:49 PM Abhishek Sharma 
wrote:

> +1
>
> On Thu, Mar 2, 2023 at 8:01 PM Fu Xiang  wrote:
>
>> +1
>>
>>
>> On Thu, Mar 2, 2023 at 4:57 PM Xiaotian Jiang 
>> wrote:
>>
>>> +1
>>>
>>> On Mon, Feb 27, 2023 at 10:24 PM Rong Rong  wrote:
>>>
 Hi Pinot Community,

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

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

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

 Git hash for this release:
 6e235a4ec2a16006337da04e118a435b5bb8f6d8

 The artifacts have been signed with key: 0F912E9BA55E4F6E, 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.12.1-rc0

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

 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

>>> --
>> Xiang Fu
>>
>

Re: [VOTE] Apache Pinot 0.12.0 RC0

[Mayank Shrivastava]

+1 (binding)

On Mon, Jan 23, 2023 at 3:52 PM Subbu Subramaniam
 wrote:

> +1 (binding)
>
> Verified on Centos Linux 7.9.2009
>
> -Subbu
> --
> *From:* Xiang Fu 
> *Sent:* Friday, January 20, 2023 3:18 PM
> *To:* Xiang Fu 
> *Cc:* dev@pinot.apache.org 
> *Subject:* Re: [VOTE] Apache Pinot 0.12.0 RC0
>
> Ping.
>
> On Dec 29, 2022, at 01:26, Xiang Fu  wrote:
>
> Hi Pinot Community,
>
> This is a call for a vote to release Apache Pinot 0.12.0.
>
> The release candidate:
> https://dist.apache.org/repos/dist/dev/pinot/apache-pinot-0.12.0-rc0
> 
>
> Git tag for this release:
> https://github.com/apache/pinot/tree/release-0.12.0-rc0
> 
>
> Git hash for this release:
> 118f5e065cb258c171d97a586183759fbc61e2bf
>
> The artifacts have been signed with key: 2237FC430E97D026, 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.12.0-rc0
> 
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachepinot-1043
> 
>
> 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.11.0 RC1

[Mayank Shrivastava]

+1

> On Sep 4, 2022, at 6:29 PM, Xiaotian Jiang  wrote:
> 
> 
> +1
> 
>> On Sun, Sep 4, 2022 at 18:57 Xiang Fu  wrote:
>> Hi Pinot Community,
>> 
>> This is a call for a vote to release Apache Pinot 0.11.0.
>> 
>> The release candidate:
>> https://dist.apache.org/repos/dist/dev/pinot/apache-pinot-0.11.0-rc1/
>> 
>> Git tag for this release:
>> https://github.com/apache/pinot/tree/release-0.11.0-rc1
>> 
>> Git hash for this release:
>> 1b4d6b6b0a27422c1552ea1a936ad145056f7033
>> 
>> The artifact has been signed with key: 2237FC430E97D026, 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.11.0-rc1
>> 
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachepinot-1040
>> 
>> 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.11.0 RC0

[Mayank Shrivastava]

+1

> On Sep 1, 2022, at 10:21 PM, Neha Pawar  wrote:
> 
> 
> +1.
> Validated as per steps in 
> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
>  .
> 
> Thanks,
> Neha Pawar
> 
> 
> 
>> On Thu, Sep 1, 2022 at 4:26 PM Xiang Fu  wrote:
>> Hi Pinot Community,
>> 
>> This is a call for a vote to release Apache Pinot 0.11.0.
>> 
>> The release candidate:
>> https://dist.apache.org/repos/dist/dev/pinot/apache-pinot-0.11.0-rc0/
>> 
>> Git tag for this release:
>> https://github.com/apache/pinot/tree/release-0.11.0-rc0
>> 
>> Git hash for this release:
>> 3d66f604e72eebbc940aeae89dfe5f9d9bbb6fc0
>> 
>> The artifact has been signed with key: 9079294B, 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.11.0-rc0
>> 
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachepinot-1039
>> 
>> 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: pinot-controller NPM security issues

[Mayank Shrivastava]

Thanks for the clarification, PJ. We will follow up on the GH issue.

Best
Mayank

> On Apr 11, 2022, at 2:53 PM, PJ Fanning  wrote:
> 
> Thanks Mayank. I do some work with the ASF Security team. Issues relating to 
> problematic dependencies are only regarded as private if there is a POC that 
> shows the issue has a direct impact on the project in question. This is not 
> the case here.
> 
> All the same, it is bad for the reputation of the ASF and its projects to 
> have projects that release with lib dependencies that have publicly known 
> vulnerabilities. `npm audit fix` will fix quite a few - it just takes someone 
> with experience verifying the UI afterwards. I am not a Pinot user so I feel 
> unqualified to do this bit. I would appeal to the Pinot community for someone 
> to update the dependencies to having malicious users come along and exploit 
> these issues.
> 
>> On 2022/04/07 13:28:06 Mayank Shrivastava wrote:
>> Hi PJ,
>> Thanks for reaching out and flagging these security issues. Seems like ASF
>> does have a security guidelines
>> <https://www.apache.org/security/committers.html>, one of which suggests to
>> not expose the insecurity via GH issue/jira or direct PR. I do see that you
>> have mentioned the security issue in the GH issue, do you mind changing the
>> description to accommodate for the same? Or let me know if I am
>> misinterpreting the guidelines.
>> 
>> Thanks again for flagging the issue, we will discuss internally and
>> follow-up soon.
>> 
>> Best Regards,
>> Mayank
>> 
>>> On Wed, Apr 6, 2022 at 7:25 AM PJ Fanning  wrote:
>>> 
>>> Hi everyone,
>>> I raised an issue about multiple insecure NPMs that are used in
>>> pinot-controller.
>>> 
>>> https://github.com/apache/pinot/issues/8476
>>> 
>>> I'm not a UI expert and not really a Pinot user, I'm just an ASF
>>> member looking to get teams to upgrade their dependencies to improve
>>> security.
>>> 
>>> Would any of the Pinot contributors be in a position to try upgrades?
>>> 
>>> This command can often do a lot of the work:
>>> npm audit fix
>>> 
>>> Regards,
>>> PJ
>>> 
>>> -
>>> 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

Re: pinot-controller NPM security issues

[Mayank Shrivastava]

Hi PJ,
Thanks for reaching out and flagging these security issues. Seems like ASF
does have a security guidelines
, one of which suggests to
not expose the insecurity via GH issue/jira or direct PR. I do see that you
have mentioned the security issue in the GH issue, do you mind changing the
description to accommodate for the same? Or let me know if I am
misinterpreting the guidelines.

Thanks again for flagging the issue, we will discuss internally and
follow-up soon.

Best Regards,
Mayank

On Wed, Apr 6, 2022 at 7:25 AM PJ Fanning  wrote:

> Hi everyone,
> I raised an issue about multiple insecure NPMs that are used in
> pinot-controller.
>
> https://github.com/apache/pinot/issues/8476
>
> I'm not a UI expert and not really a Pinot user, I'm just an ASF
> member looking to get teams to upgrade their dependencies to improve
> security.
>
> Would any of the Pinot contributors be in a position to try upgrades?
>
> This command can often do a lot of the work:
> npm audit fix
>
> Regards,
> PJ
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
> For additional commands, e-mail: dev-h...@pinot.apache.org
>
>

Re: [VOTE] Apache Pinot 0.9.3 RC0

[Mayank Shrivastava]

+1

> On Dec 24, 2021, at 3:22 AM, Richard Startin  
> wrote:
> 
> 
> +1
> 
>> On Fri, Dec 24, 2021 at 10:17 AM Atri Sharma  wrote:
>> +1
>> 
>>> On Fri, 24 Dec 2021, 15:41 Xiang Fu,  wrote:
>>> Hi Pinot Community,
>>> 
>>> This is a call for a vote to release Apache Pinot 0.9.3.
>>> 
>>> This is a bug fixing release contains:
>>> - Upgrade log4j to 2.17.0 to address CVE-2021-45105 (#7933)
>>> 
>>> The release candidate:
>>> https://dist.apache.org/repos/dist/dev/pinot/apache-pinot-0.9.3-rc0
>>> 
>>> Git tag for this release:
>>> https://github.com/apache/pinot/tree/release-0.9.3-rc0
>>> 
>>> Git hash for this release:
>>> e23f213cf0d16b1e9e086174d734a4db868542cb
>>> 
>>> 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.3-rc0
>>> 
>>> Staging repository:
>>> https://repository.apache.org/content/repositories/orgapachepinot-1034
>>> 
>>> 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.2 RC0

[Mayank Shrivastava]

+1

On Tue, Dec 14, 2021 at 9:53 PM Jialiang Li  wrote:

> +1
>
> On 2021/12/15 05:43:45 Atri Sharma wrote:
> > +1
> >
> > On Wed, Dec 15, 2021 at 11:10 AM Xiang Fu 
> wrote:
> > >
> > > Hi Pinot Community,
> > >
> > > This is a call for a vote to release Apache Pinot 0.9.2.
> > >
> > > This is a bug fixing release contains:
> > > - Upgrade log4j to 2.16.0 to fix CVE-2021-45046 (#7903)
> > > - Upgrade swagger-ui to 3.23.11 to fix CVE-2019-17495 (#7902)
> > > - Fix the bug that RealtimeToOfflineTask failed to progress with large
> time bucket gaps (#7814).
> > >
> > > The release candidate:
> > > https://dist.apache.org/repos/dist/dev/pinot/apache-pinot-0.9.2-rc0
> > >
> > > Git tag for this release:
> > > https://github.com/apache/pinot/tree/release-0.9.2-rc0
> > >
> > > Git hash for this release:
> > > 3e5e5aca07ad796d453add80a2b2b1bf1d654cf1
> > >
> > > 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.2-rc0
> > >
> > > Staging repository:
> > > https://repository.apache.org/content/repositories/orgapachepinot-1033
> > >
> > > 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
> >
> > --
> > Regards,
> >
> > Atri
> > Apache Concerted
> >
> > -
> > 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 0.9.1 RC0

[Mayank Shrivastava]

+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

[Mayank Shrivastava]

+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

[Mayank Shrivastava]

+1 
Thanks for driving this Xiang.

Regards
Mayank 

> On Sep 14, 2021, at 1:51 AM, Xiang Fu  wrote:
> 
> 
> Dear Community,
> 
> TL;DR, Pinot will remove PQL query endpoint and response format after 0.9.0 
> release, only SQL endpoint is supported afterward.
> 
> Apache Pinot has been supporting the Calcite SQL query endpoint from 0.3.0 
> (Mar 2020) and deprecating the PQL query endpoint for more than a year.
> 
> Now we are seeing more obstacles to maintain two code paths for PQL & SQL for 
> adding new functionalities, query optimization, behavior handling, etc.
> 
> 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
> 
> 
> Current timeline is driven by the next Apache Pinot release:
> 
> 1. Apache Pinot 0.9.0 release (ETA Release date: Oct/Nov 2021) is the last 
> official Pinot release that supports PQL.
> 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.
> 
> 
> Best,
> 
> Xiang Fu

Re: [VOTE] Apache Pinot 0.8.0 RC0

[Mayank Shrivastava]

+1 [binding]

On Fri, Aug 13, 2021 at 1:30 PM Yupeng Fu  wrote:

> +1
>
> On Thu, Aug 12, 2021 at 6:53 PM Xiang Fu  wrote:
>
>> +1
>>
>> I’m using maven 3.6.2 and validated both jdk8/11.
>>
>>
>> On Aug 12, 2021, at 4:53 PM, Yupeng Fu  wrote:
>>
>> Thanks for updating the notes.
>>
>> I upgraded maven from 3.3 to 3.8, and I can successfully build the
>> release.
>>
>> Thanks,
>>
>> On Thu, Aug 12, 2021 at 4:20 PM Seunghyun Lee  wrote:
>>
>>> @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:
>>> 

[RESULT][VOTE] Graduate Apache Pinot as TLP

[Mayank Shrivastava]

Hi,
The voting for graduating Apache Pinot as a TLP is now closed. The results
of voting are listed below.

Binding votes: 13 +1 votes, no 0 or -1 votes.
Non binding: 12 +1 notes, no 0 or -1 votes

The thread can be found here

.

Please let us know the next steps in the graduating process.

Thanks,
Mayank

[VOTE] Graduate Apache Pinot as TLP

[Mayank Shrivastava]

Dear Incubator Community,

We have discussed Apache Pinot Podling graduation in the general@incubator
DISCUSS thread [1], and addressed all the questions and concerns brought up
in the thread. Please refer to [1] for details on the questions and
concerns brought up, as well as their resolutions. With no objections
brought up in the discussion, we would like to proceed with the voting
process.

Here is the official vote for graduating Apache Pinot project as TLP.

Please provide your in the following options:

[ ] +1 - Recommend graduation of Apache Pinot as a TLP

[ ]  0 - I don't feel strongly about it, but don't object

[ ] -1 - Do not recommend the graduation of Apache Pinot because…

The VOTE will remain open for at least 72 hours.

To summarize a few of the community's achievements:


   -

   7800+ contributions from 168 contributors
   -

   7 releases by various release managers
   -

   6 new committers and 2 new PPMCs invited (all accepted)
   -

   Diverse committers and PPMCs (from 7 companies/institutes)
   -

   Apache website setup [4]
   -

   Dev conversations at dev@pinot.apache.org
   -

   Assessed ourselves against the Apache Project maturity matrix [5]
   -

   We have built a meritocratic and open collaborative process (the Apache
   way)



=

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.


[1] general@Incubator Discuss thread
<https://lists.apache.org/thread.html/r4421bf9517dc522a564e7453c2c87dddbf39019737dd143de57d2f49%40%3Cgeneral.incubator.apache.org%3E>

[2] Community Discussion for Graduation
<https://lists.apache.org/thread.html/r6068cae91a474e86595cc02d90701501d22c08274216301facf935cc%40%3Cdev.pinot.apache.org%3E>

[3] Voting Thread
<https://lists.apache.org/thread.html/r9ca0b2ccc9b0fbdbee6a09aaf06b36ffd3a20e9cc1b810cdbe7c65d6%40%3Cdev.pinot.apache.org%3E>

[4] Voting Result
<https://lists.apache.org/thread.html/rc371ca50ce8ff2d6c0b068165195526cfdbd08d915105573e17042d2%40%3Cdev.pinot.apache.org%3E>

[5] https://pinot.incubator.apache.org/
[6] Maturity Model Assessment
<https://cwiki.apache.org/confluence/display/PINOT/Apache+Maturity+Model+Assessment+for+Pinot>

Re: [DISCUSS] Graduate Apache Pinot (Incubating) as a TLP

[Mayank Shrivastava]

Hello Justin, Sheng & IPMC
Thanks so much for reviewing our proposal and your questions and
suggestions. Please find our response below, and let us know if you have
any questions, and suggest next steps.

Decision process for PMC: We follow discussion + voting protocol for adding
new PMCs. We would like to keep the process of adding new PMC members
separate from the graduation process, and go over the discussion and voting
process on a case by case basis.


VP candidate: The VP candidate was proposed aspart of the voting process
for graduation [1], and was accepted in the voting.

We checked with Jackie on him not being part of private@, and found that he
had issues in the past subscribing to the list. He is one of the top
contributors for the project [2], and is now subscribed to the private@
mailing list.

Jihao Zhang confirms that they have unsubscribed from the private@ mailing
list.

Presto references to Pinot have been replaced by Apache Pinot [3]. We do
not own the Presto project, so cannot control other references such as
Cassandra, etc.

Licensing issues have been resolved [4] [5].

Added disclaimer in the main page to indicate that Presto and TE are not
part of ASF[6][7]

Confirmed that documentation on ThirdEye is still correct [8].

There are no links pointing to [9] from the main page. The correct link
should be [10]. Is there a place where this link needs to be removed from?

[1] Graduation Voting Thread


[2] Jackie’s Apache Pinot commits 

[3] Presto branding issue PR 

[4] Licensing Github Issue


[5] PR for fixing Licensing Issue


[6] Apache Pinot main page 

[7] PR adding the disclaimer about Presto/TE not part of ASF


[8] TE Doc Page 

[9] Broken TE link pointed out by Justin

[10] Correct TE repo link 

On Sat, Jun 12, 2021 at 12:24 AM Justin Mclean 
wrote:

> Hi,
>
> Thanks for putting that information together, everything look goods, but I
> have a couple of queries.
>
> From your PMC I noticed one person Jackie Jiang has not sign up to the
> private list and has not sent a single mail to the dev or private lists.
> Have you asked them if they want to be on the PMC?  It might also be a good
> idea to discuss adding some of your existing committers to the new PMC as
> well. They can be added in teh normal way after graduation as well. I also
> noticed there one person who perhaps should not be subscribed to your
> private list (Jihao Zhang).
>
> I also notice that you have links on the front page to seem to point to
> non-ASF software? Presto and ThirdEye. ThirdEye from memory is not
> compatible with the Apache license so I’m not sure that the project should
> be promoting this on their front page and where they are include big
> disclaimers warning people about this. Is this documentation still correct,
> [6] I notice this no longer works [7]
>
> The Presto documentation looks to have a few branding issue that need to
> be corrected [3]. Is the PPMC aware of this and doing something about it? I
> can see some other branding issues with the presto webpage [4][5] (and
> other pages) and Apache projects with Pinot and Hive, Hadoop, Cassandra,
> Spark, Kafka and Druid. There might be others.
>
> Has this license issue been fixed? [1] I can see the issue is still open
> [2]
>
> Thanks,
> Justin
>
> 1.
> https://lists.apache.org/thread.html/rb2bc93448636e3238f72654426ecce232b46c73ed1447b9c47a1d49e%40%3Cgeneral.incubator.apache.org%3E
> 2. https://github.com/apache/incubator-pinot/issues/6785
> 3. https://prestodb.io/docs/current/connector/pinot.html
> 4. https://prestodb.io
> 5. https://prestodb.io/faq.html
> 6. https://docs.pinot.apache.org/integrations/thirdeye
> 7. https://github.com/apache/incubator-pinot/tree/master/thirdeye
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[DISCUSS] Graduate Apache Pinot (Incubating) as a TLP

[Mayank Shrivastava]

Hi all,

After a discussion with the community [1], voting [2], and a positive vote
result [3],

we believe Apache Pinot (Incubating) is ready for graduation to a TLP,

and we'd like to bring it up in discussion with the IPMC.

To list a few of the community's achievements:


   -

   7800+ contributions from 168 contributors
   -

   7 releases by various release managers
   -

   6 new committers and 2 new PPMCs invited (all accepted)
   -

   Diverse committers and PPMCs (from 7 companies/institutes)
   -

   Apache website setup [4]
   -

   Dev conversations at dev@pinot.apache.org
   -

   Assessed ourselves against the Apache Project maturity matrix [5]
   -

   We have built a meritocratic and open collaborative process (the Apache
   way)


[1] Community Discussion for Graduation
<https://lists.apache.org/thread.html/r6068cae91a474e86595cc02d90701501d22c08274216301facf935cc%40%3Cdev.pinot.apache.org%3E>

[2] Voting Thread
<https://lists.apache.org/thread.html/r9ca0b2ccc9b0fbdbee6a09aaf06b36ffd3a20e9cc1b810cdbe7c65d6%40%3Cdev.pinot.apache.org%3E>

[3] Voting Result
<https://lists.apache.org/thread.html/rc371ca50ce8ff2d6c0b068165195526cfdbd08d915105573e17042d2%40%3Cdev.pinot.apache.org%3E>

[4] https://pinot.incubator.apache.org/

[5] Maturity Model Assessment
<https://cwiki.apache.org/confluence/display/PINOT/Apache+Maturity+Model+Assessment+for+Pinot>

Please see the proposed board resolution below and let us know what you

think.

The discussion will remain open for at least 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.


---


Thanks,
Mayank

[Result] [VOTE] Apache Pinot graduation to a TLP

[Mayank Shrivastava]

Hello all,
The voting is now closed and has passed with six +1 bindings (additions two
+1 from discussion
<https://lists.apache.org/thread.html/r6068cae91a474e86595cc02d90701501d22c08274216301facf935cc%40%3Cdev.pinot.apache.org%3E>
carry-over, two non-binding +1, no 0 or -1 votes.

Binding: Six +1 (additional two +1 from discussion carryover)
kishoreg
mayanks
jim
mcvsubbu
siddteotia
snlee

(carryover +1 from discussion)
felix
olamy

No 0 or -1 binding votes

Non binding: three +1
yupeng
tingchen
jlli

No 0 or -1 non-binding votes

Thanks,
Mayank, on behalf of the Apache Pinot (Incubating) Community

On Tue, Jun 8, 2021 at 6:09 PM Jialiang Li  wrote:

> +1
>
> On 2021/06/04 17:58:47, TING CHEN  wrote:
> > +1
> >
> > On Fri, Jun 4, 2021 at 10:25 AM siddharth teotia <
> siddharthteo...@gmail.com>
> > wrote:
> >
> > > +1
> > >
> > > On Fri, Jun 4, 2021 at 10:21 AM Yupeng Fu  wrote:
> > >
> > >> +1
> > >>
> > >> On Fri, Jun 4, 2021 at 10:20 AM Seunghyun Lee 
> wrote:
> > >>
> > >>> +1
> > >>>
> > >>> Best,
> > >>> Seunghyun
> > >>>
> > >>> On Fri, Jun 4, 2021 at 10:14 AM Mayank Shrivastava <
> maya...@apache.org>
> > >>> 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 <
> mcvsu...@apache.org>
> > >>>> 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
> > >>>>> aspe

Re: [VOTE] Apache Pinot graduation to a TLP

[Mayank Shrivastava]

+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
>
>

[VOTE] Apache Pinot graduation to a TLP

[Mayank Shrivastava]

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.

Re: DISCUSS Pinot Graduation

[Mayank Shrivastava]

Thank you mentors and devs. I will start the voting process. 

Regards
Mayank 

> On Jun 2, 2021, at 7:27 AM, Jim Jagielski  wrote:
> 
> Agreed. +1!
> 
>> On Jun 1, 2021, at 11:58 PM, Olivier Lamy  wrote:
>> 
>> Good job guys!
>> definitely +1 to open vote (be ready as this will generate some comments and 
>> more paperwork :) )
>> 
>> 
>> On Wed, 2 Jun 2021 at 03:14, Mayank Shrivastava  wrote:
>>> Mentors,
>>> Gentle ping, are we good to open a vote for Pinot's graduation? We have 
>>> addressed all the issues brought up by Felix.
>>> 
>>> Regards,
>>> Mayank
>>> 
>>> On Sat, May 22, 2021 at 9:44 PM Mayank Shrivastava  
>>> wrote:
>>>> Gentle ping to mentors to guide us with graduation discussion. We have 
>>>> addressed the comments raised by Felix in the thread earlier. Also 
>>>> requesting comments from Oliver and Jim.
>>>> Thanks for your help.
>>>> 
>>>> Regards,
>>>> Mayank
>>>> 
>>>> On Mon, May 17, 2021 at 5:38 PM Mayank Shrivastava  
>>>> wrote:
>>>>> Thanks Felix, for your valuable inputs. We have updated the project page 
>>>>> and also added the maturity model. Please let us know if there are other 
>>>>> things we should address.
>>>>> 
>>>>> 1. Project Page
>>>>> 2. Maturity Model
>>>>> 
>>>>> On Sun, May 16, 2021 at 1:57 PM Felix Cheung  
>>>>> wrote:
>>>>>> Agreed it is not a blocker per se, but I figure it will raise some 
>>>>>> questions if more board/podling reports are missed.
>>>>>> 
>>>>>> Maybe worthwhile to setup forwarding from dev@ to slack.
>>>>>> 
>>>>>> 
>>>>>> From: kishore g 
>>>>>> Sent: Saturday, May 15, 2021 6:53 PM
>>>>>> To: dev@pinot.apache.org
>>>>>> Cc: Mayank Shrivastava; j...@apache.org; ol...@apache.org
>>>>>> Subject: Re: DISCUSS Pinot Graduation
>>>>>>  
>>>>>> I agree with you on traffic on dev. We tried to move few discussions to 
>>>>>> dev@ but entire community is active on the slack channel and prefer 
>>>>>> discussion on GitHub issues. We push everything to dev@ so folks on ML 
>>>>>> have all the information.
>>>>>> 
>>>>>> We have < 100 on @dev vs ~1300 on slack. Trying to push slack members to 
>>>>>> join dev did not work in the past and I doubt it will work now. We will 
>>>>>> continue to make sure all discussions on slack are sent as digest to 
>>>>>> dev. 
>>>>>> 
>>>>>> We have mentioned this in our reports last year and we did not hear any 
>>>>>> objections from the board.
>>>>>> 
>>>>>> 
>>>>>> Thanks,
>>>>>> Kishore G
>>>>>> 
>>>>>> On Fri, May 14, 2021 at 8:38 PM Felix Cheung  
>>>>>> wrote:
>>>>>>> Generally it looks good, I’ve checked clutch report, website checks 
>>>>>>> etc, but a few reminders and areas to pay attention to:
>>>>>>> 
>>>>>>> - dev@ traffic is very or almost zero? I realize the community is 
>>>>>>> active on slack and summary is sent to dev@ everyday, but some traffic 
>>>>>>> there will be good...
>>>>>>> 
>>>>>>> - ... because people will miss stuff. The podling report reminder was 
>>>>>>> sent there and Pinot just missed this month’s podling report. Let’s 
>>>>>>> make sure the month is out promptly next month
>>>>>>> 
>>>>>>> - pls make sure the incubation status is updated 
>>>>>>> http://incubator.apache.org/projects/pinot - for instance either the 
>>>>>>> committer list is not sorted or the last date is wrong (should not be 
>>>>>>> 2020). The rest of the page can use updating too. Also many sections 
>>>>>>> there have placeholder content, pls fill them in.
>>>>>>> 
>>>>>>> - also as suggested, please take the maturity model, fill it in and 
>>>>>>> share with dev@ anything identified - project maturity model (as a 
>>>>>>> guide)
>&g

Re: DISCUSS Pinot Graduation

[Mayank Shrivastava]

Mentors,
Gentle ping, are we good to open a vote for Pinot's graduation? We have
addressed all the issues brought up by Felix.

Regards,
Mayank

On Sat, May 22, 2021 at 9:44 PM Mayank Shrivastava 
wrote:

> Gentle ping to mentors to guide us with graduation discussion. We have
> addressed the comments raised by Felix in the thread earlier. Also
> requesting comments from Oliver and Jim.
> Thanks for your help.
>
> Regards,
> Mayank
>
> On Mon, May 17, 2021 at 5:38 PM Mayank Shrivastava 
> wrote:
>
>> Thanks Felix, for your valuable inputs. We have updated the project page
>> and also added the maturity model. Please let us know if there are other
>> things we should address.
>>
>> 1. Project Page <https://incubator.apache.org/projects/pinot.html>
>> 2. Maturity Model
>> <https://cwiki.apache.org/confluence/display/PINOT/Apache+Maturity+Model+Assessment+for+Pinot>
>>
>> On Sun, May 16, 2021 at 1:57 PM Felix Cheung 
>> wrote:
>>
>>> Agreed it is not a blocker per se, but I figure it will raise some
>>> questions if more board/podling reports are missed.
>>>
>>> Maybe worthwhile to setup forwarding from dev@ to slack.
>>>
>>>
>>> --
>>> *From:* kishore g 
>>> *Sent:* Saturday, May 15, 2021 6:53 PM
>>> *To:* dev@pinot.apache.org
>>> *Cc:* Mayank Shrivastava; j...@apache.org; ol...@apache.org
>>> *Subject:* Re: DISCUSS Pinot Graduation
>>>
>>> I agree with you on traffic on dev. We tried to move few discussions to
>>> dev@ but entire community is active on the slack channel and prefer
>>> discussion on GitHub issues. We push everything to dev@ so folks on ML
>>> have all the information.
>>>
>>> We have < 100 on @dev vs ~1300 on slack. Trying to push slack members to
>>> join dev did not work in the past and I doubt it will work now. We will
>>> continue to make sure all discussions on slack are sent as digest to dev.
>>>
>>> We have mentioned this in our reports last year and we did not hear any
>>> objections from the board.
>>>
>>>
>>> Thanks,
>>> Kishore G
>>>
>>> On Fri, May 14, 2021 at 8:38 PM Felix Cheung 
>>> wrote:
>>>
>>>> Generally it looks good, I’ve checked clutch report, website checks
>>>> etc, but a few reminders and areas to pay attention to:
>>>>
>>>> - dev@ traffic is very or almost zero? I realize the community is
>>>> active on slack and summary is sent to dev@ everyday, but some traffic
>>>> there will be good...
>>>>
>>>> - ... because people will miss stuff. The podling report reminder was
>>>> sent there and Pinot just missed this month’s podling report. Let’s make
>>>> sure the month is out promptly next month
>>>>
>>>> - pls make sure the incubation status is updated
>>>> http://incubator.apache.org/projects/pinot - for instance either the
>>>> committer list is not sorted or the last date is wrong (should not be
>>>> 2020). The rest of the page can use updating too. Also many sections there
>>>> have placeholder content, pls fill them in.
>>>>
>>>> - also as suggested, please take the maturity model, fill it in and
>>>> share with dev@ anything identified - project maturity model (as a
>>>> guide)
>>>>
>>>> https://community.apache.org/apache-way/apache-project-maturity-model.html
>>>>
>>>>
>>>>
>>>> On Fri, May 14, 2021 at 3:13 PM Mayank Shrivastava 
>>>> wrote:
>>>>
>>>>> Mentors - Felix, Olivier, Jim,
>>>>> Wondering what your thoughts on are for proposing Pinot's graduation.
>>>>> We have addressed all the issues that have been brought up in the past. If
>>>>> there are other steps to be taken, please let us know and we can also take
>>>>> care of those as well. Looking forward to your suggestions and support.
>>>>>
>>>>> Regards,
>>>>> Mayank
>>>>>
>>>>> On Mon, May 10, 2021 at 12:54 PM Fu Xiang 
>>>>> wrote:
>>>>>
>>>>>> +1! Glad to see we've accomplished a lot and the community is pretty
>>>>>> strong and healthy!
>>>>>>
>>>>>> On Mon, May 10, 2021 at 11:23 AM Subbu Subramaniam <
>>>>>> mcvsu...@apache.org> wrote:
>>>>>&

Re: DISCUSS Pinot Graduation

[Mayank Shrivastava]

Gentle ping to mentors to guide us with graduation discussion. We have
addressed the comments raised by Felix in the thread earlier. Also
requesting comments from Oliver and Jim.
Thanks for your help.

Regards,
Mayank

On Mon, May 17, 2021 at 5:38 PM Mayank Shrivastava 
wrote:

> Thanks Felix, for your valuable inputs. We have updated the project page
> and also added the maturity model. Please let us know if there are other
> things we should address.
>
> 1. Project Page <https://incubator.apache.org/projects/pinot.html>
> 2. Maturity Model
> <https://cwiki.apache.org/confluence/display/PINOT/Apache+Maturity+Model+Assessment+for+Pinot>
>
> On Sun, May 16, 2021 at 1:57 PM Felix Cheung 
> wrote:
>
>> Agreed it is not a blocker per se, but I figure it will raise some
>> questions if more board/podling reports are missed.
>>
>> Maybe worthwhile to setup forwarding from dev@ to slack.
>>
>>
>> --
>> *From:* kishore g 
>> *Sent:* Saturday, May 15, 2021 6:53 PM
>> *To:* dev@pinot.apache.org
>> *Cc:* Mayank Shrivastava; j...@apache.org; ol...@apache.org
>> *Subject:* Re: DISCUSS Pinot Graduation
>>
>> I agree with you on traffic on dev. We tried to move few discussions to
>> dev@ but entire community is active on the slack channel and prefer
>> discussion on GitHub issues. We push everything to dev@ so folks on ML
>> have all the information.
>>
>> We have < 100 on @dev vs ~1300 on slack. Trying to push slack members to
>> join dev did not work in the past and I doubt it will work now. We will
>> continue to make sure all discussions on slack are sent as digest to dev.
>>
>> We have mentioned this in our reports last year and we did not hear any
>> objections from the board.
>>
>>
>> Thanks,
>> Kishore G
>>
>> On Fri, May 14, 2021 at 8:38 PM Felix Cheung 
>> wrote:
>>
>>> Generally it looks good, I’ve checked clutch report, website checks etc,
>>> but a few reminders and areas to pay attention to:
>>>
>>> - dev@ traffic is very or almost zero? I realize the community is
>>> active on slack and summary is sent to dev@ everyday, but some traffic
>>> there will be good...
>>>
>>> - ... because people will miss stuff. The podling report reminder was
>>> sent there and Pinot just missed this month’s podling report. Let’s make
>>> sure the month is out promptly next month
>>>
>>> - pls make sure the incubation status is updated
>>> http://incubator.apache.org/projects/pinot - for instance either the
>>> committer list is not sorted or the last date is wrong (should not be
>>> 2020). The rest of the page can use updating too. Also many sections there
>>> have placeholder content, pls fill them in.
>>>
>>> - also as suggested, please take the maturity model, fill it in and
>>> share with dev@ anything identified - project maturity model (as a
>>> guide)
>>>
>>> https://community.apache.org/apache-way/apache-project-maturity-model.html
>>>
>>>
>>>
>>> On Fri, May 14, 2021 at 3:13 PM Mayank Shrivastava 
>>> wrote:
>>>
>>>> Mentors - Felix, Olivier, Jim,
>>>> Wondering what your thoughts on are for proposing Pinot's graduation.
>>>> We have addressed all the issues that have been brought up in the past. If
>>>> there are other steps to be taken, please let us know and we can also take
>>>> care of those as well. Looking forward to your suggestions and support.
>>>>
>>>> Regards,
>>>> Mayank
>>>>
>>>> On Mon, May 10, 2021 at 12:54 PM Fu Xiang  wrote:
>>>>
>>>>> +1! Glad to see we've accomplished a lot and the community is pretty
>>>>> strong and healthy!
>>>>>
>>>>> On Mon, May 10, 2021 at 11:23 AM Subbu Subramaniam <
>>>>> mcvsu...@apache.org> wrote:
>>>>>
>>>>>> +1
>>>>>>
>>>>>> Let us know how we can help with the graduation, and if there are any
>>>>>> pending items to be resolved.
>>>>>>
>>>>>> -Subbu
>>>>>>
>>>>>> On 2021/05/09 14:07:45, 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

Re: DISCUSS Pinot Graduation

[Mayank Shrivastava]

Thanks Felix, for your valuable inputs. We have updated the project page
and also added the maturity model. Please let us know if there are other
things we should address.

1. Project Page <https://incubator.apache.org/projects/pinot.html>
2. Maturity Model
<https://cwiki.apache.org/confluence/display/PINOT/Apache+Maturity+Model+Assessment+for+Pinot>

On Sun, May 16, 2021 at 1:57 PM Felix Cheung 
wrote:

> Agreed it is not a blocker per se, but I figure it will raise some
> questions if more board/podling reports are missed.
>
> Maybe worthwhile to setup forwarding from dev@ to slack.
>
>
> --
> *From:* kishore g 
> *Sent:* Saturday, May 15, 2021 6:53 PM
> *To:* dev@pinot.apache.org
> *Cc:* Mayank Shrivastava; j...@apache.org; ol...@apache.org
> *Subject:* Re: DISCUSS Pinot Graduation
>
> I agree with you on traffic on dev. We tried to move few discussions to
> dev@ but entire community is active on the slack channel and prefer
> discussion on GitHub issues. We push everything to dev@ so folks on ML
> have all the information.
>
> We have < 100 on @dev vs ~1300 on slack. Trying to push slack members to
> join dev did not work in the past and I doubt it will work now. We will
> continue to make sure all discussions on slack are sent as digest to dev.
>
> We have mentioned this in our reports last year and we did not hear any
> objections from the board.
>
>
> Thanks,
> Kishore G
>
> On Fri, May 14, 2021 at 8:38 PM Felix Cheung 
> wrote:
>
>> Generally it looks good, I’ve checked clutch report, website checks etc,
>> but a few reminders and areas to pay attention to:
>>
>> - dev@ traffic is very or almost zero? I realize the community is active
>> on slack and summary is sent to dev@ everyday, but some traffic there
>> will be good...
>>
>> - ... because people will miss stuff. The podling report reminder was
>> sent there and Pinot just missed this month’s podling report. Let’s make
>> sure the month is out promptly next month
>>
>> - pls make sure the incubation status is updated
>> http://incubator.apache.org/projects/pinot - for instance either the
>> committer list is not sorted or the last date is wrong (should not be
>> 2020). The rest of the page can use updating too. Also many sections there
>> have placeholder content, pls fill them in.
>>
>> - also as suggested, please take the maturity model, fill it in and share
>> with dev@ anything identified - project maturity model (as a guide)
>> https://community.apache.org/apache-way/apache-project-maturity-model.html
>>
>>
>>
>> On Fri, May 14, 2021 at 3:13 PM Mayank Shrivastava 
>> wrote:
>>
>>> Mentors - Felix, Olivier, Jim,
>>> Wondering what your thoughts on are for proposing Pinot's graduation. We
>>> have addressed all the issues that have been brought up in the past. If
>>> there are other steps to be taken, please let us know and we can also take
>>> care of those as well. Looking forward to your suggestions and support.
>>>
>>> Regards,
>>> Mayank
>>>
>>> On Mon, May 10, 2021 at 12:54 PM Fu Xiang  wrote:
>>>
>>>> +1! Glad to see we've accomplished a lot and the community is pretty
>>>> strong and healthy!
>>>>
>>>> On Mon, May 10, 2021 at 11:23 AM Subbu Subramaniam 
>>>> wrote:
>>>>
>>>>> +1
>>>>>
>>>>> Let us know how we can help with the graduation, and if there are any
>>>>> pending items to be resolved.
>>>>>
>>>>> -Subbu
>>>>>
>>>>> On 2021/05/09 14:07:45, 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
>>>>> >-
>

Re: DISCUSS Pinot Graduation

[Mayank Shrivastava]

Mentors - Felix, Olivier, Jim,
Wondering what your thoughts on are for proposing Pinot's graduation. We
have addressed all the issues that have been brought up in the past. If
there are other steps to be taken, please let us know and we can also take
care of those as well. Looking forward to your suggestions and support.

Regards,
Mayank

On Mon, May 10, 2021 at 12:54 PM Fu Xiang  wrote:

> +1! Glad to see we've accomplished a lot and the community is pretty
> strong and healthy!
>
> On Mon, May 10, 2021 at 11:23 AM Subbu Subramaniam 
> wrote:
>
>> +1
>>
>> Let us know how we can help with the graduation, and if there are any
>> pending items to be resolved.
>>
>> -Subbu
>>
>> On 2021/05/09 14:07:45, 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
>> >
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
>> For additional commands, e-mail: dev-h...@pinot.apache.org
>>
>>
>
> --
> Xiang Fu
>

Re: DISCUSS Pinot Graduation

[Mayank Shrivastava]

+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
> 

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

[Mayank Shrivastava]

+1

On Wed, Apr 7, 2021 at 3:09 PM Xiaotian Jiang  wrote:

> +1
>
> On Wed, Apr 7, 2021 at 2:56 PM Fu Xiang  wrote:
>
>> Hi Pinot Community,
>>
>> This is a call for a vote to release Apache Pinot (incubating) version
>> 0.7.1.
>>
>> The release candidate:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.7.1-rc0/
>>
>> Git tag for this release:
>> https://github.com/apache/incubator-pinot/tree/release-0.7.1-rc0
>>
>> Git hash for this release:
>> *e22be7c3a39e840321d3658e7505f21768b228d6*
>>
>> The artifacts have been signed with key: *CDEDB21B862F6C66*, 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.7.1-rc0
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachepinot-1025
>>
>> 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 the 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.7.0 RC1

[Mayank Shrivastava]

+1

> On Mar 10, 2021, at 5:27 PM, Yupeng Fu  wrote:
> 
> 
> I think there was some data transfer issue. Now the files are available.
> 
>  wget 
> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.7.0-rc1/apache-pinot-incubating-0.7.0-bin.tar.gz.sha512
> --2021-03-10 17:26:03--  
> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.7.0-rc1/apache-pinot-incubating-0.7.0-bin.tar.gz.sha512
> Resolving dist.apache.org (dist.apache.org)... 13.90.137.153
> Connecting to dist.apache.org (dist.apache.org)|13.90.137.153|:443... 
> connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 128 [text/plain]
> Saving to: ‘apache-pinot-incubating-0.7.0-bin.tar.gz.sha512’
> 
> apache-pinot-incubating-0.7.0-bin.tar. 
> 100%[>]
>  128  --.-KB/sin 0s
> 
> 2021-03-10 17:26:03 (15.3 MB/s) - 
> ‘apache-pinot-incubating-0.7.0-bin.tar.gz.sha512’ saved [128/128]
> 
>> On Wed, Mar 10, 2021 at 3:49 PM Mayank Shrivastava  
>> wrote:
>> I get the following error with wget:
>> 
>> wget 
>> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-$VERSION-rc$RC/apache-pinot-incubating-$VERSION-bin.tar.gz.sha512
>> --2021-03-10 15:47:25--  
>> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.7.0-rc1/apache-pinot-incubating-0.7.0-bin.tar.gz.sha512
>> Resolving dist.apache.org (dist.apache.org)... 13.90.137.153
>> Connecting to dist.apache.org (dist.apache.org)|13.90.137.153|:443... 
>> connected.
>> HTTP request sent, awaiting response... 404 Not Found
>> 2021-03-10 15:47:25 ERROR 404: Not Found.
>> 
>>> On Wed, Mar 10, 2021 at 3:00 PM Yupeng Fu  wrote:
>>> Hi Pinot Community,
>>> 
>>> This is a call for vote to the release Apache Pinot (incubating) version
>>> 0.7.0.
>>> 
>>> The release candidate:
>>> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.7.0-rc1/
>>>  
>>> 
>>> Git tag for this release:
>>> https://github.com/apache/incubator-pinot/tree/release-0.7.0-rc1
>>> 
>>> Git hash for this release:
>>> a18dc60dca09bd2a1d33a8bc6b787d7ceb8e1749
>>> 
>>> The artifacts have been signed with key: F41AB2B856C6C29D, 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.7.0-rc1
>>> 
>>> Staging repository:
>>> https://repository.apache.org/content/repositories/orgapachepinot-1024
>>> 
>>> 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 the necessary number of
>>> votes are reached.
>>> 
>>> Please vote accordingly,
>>> 
>>> [ ] +1 approve
>>> [ ] +0 no opinion
>>> [ ] -1 disapprove with the reason
>>> 
>>> Thanks,
>>> Apache Pinot (incubating) team
>>> 
>>> -- 
>>> --Yupeng
> 
> 
> -- 
> --Yupeng

Re: [VOTE] Apache Pinot (incubating) 0.7.0 RC1

[Mayank Shrivastava]

I get the following error with wget:

wget
https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-$VERSION-rc$RC/apache-pinot-incubating-$VERSION-bin.tar.gz.sha512

--2021-03-10 15:47:25--
https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.7.0-rc1/apache-pinot-incubating-0.7.0-bin.tar.gz.sha512

Resolving dist.apache.org (dist.apache.org)... 13.90.137.153

Connecting to dist.apache.org (dist.apache.org)|13.90.137.153|:443...
connected.

HTTP request sent, awaiting response... 404 Not Found

2021-03-10 15:47:25 ERROR 404: Not Found.

On Wed, Mar 10, 2021 at 3:00 PM Yupeng Fu  wrote:

> Hi Pinot Community,
>
> This is a call for vote to the release Apache Pinot (incubating) version
> 0.7.0.
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.7.0-rc1/
>
>
> Git tag for this release:
> 
> https://github.com/apache/incubator-pinot/tree/release-0.7.0-rc1
>
> Git hash for this release:
> a18dc60dca09bd2a1d33a8bc6b787d7ceb8e1749
>
> The artifacts have been signed with key: F41AB2B856C6C29D, 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.7.0-rc1
>
> Staging repository:
> 
> https://repository.apache.org/content/repositories/orgapachepinot-1024
>
> 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 the necessary number
> of
> votes are reached.
>
> Please vote accordingly,
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> Apache Pinot (incubating) team
>
> --
> --Yupeng
>

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

[Mayank Shrivastava]

+1

Verified as per the steps listed.

> On Mar 5, 2021, at 9:28 AM, Yupeng Fu  wrote:
> 
> 
> Hi Pinot Community,
> 
> This is a call for vote to the release Apache Pinot (incubating) version
> 0.7.0.
> 
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.7.0-rc0/
> 
> Git tag for this release:
> https://github.com/apache/incubator-pinot/tree/release-0.7.0-rc0
> 
> Git hash for this release:
> 157bd569303bbab60d79dbd36ba68089d1ee651f
> 
> The artifacts have been signed with key: F41AB2B856C6C29D, 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.7.0-rc0
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachepinot-1023
> 
> 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 the necessary number of
> votes are reached.
> 
> Please vote accordingly,
> 
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
> 
> Thanks,
> Apache Pinot (incubating) team
> 
> -- 
> --Yupeng

Re: Move thirdeye out from Pinot repo

[Mayank Shrivastava]

Thanks Xiang, for helping with this move.

Regards
Mayank

> On Feb 22, 2021, at 8:56 PM, Fu Xiang  wrote:
> 
> 
> Hi team,
> 
> As part of the Pinot 0.7.0 release effort, we will move the thirdeye project 
> out from the Pinot repo.
> 
> The new repo for thirdeye will be located at 
> https://github.com/project-thirdeye/thirdeye.
> 
> In order to keep all the commit history, I'm going to clone the entire Pinot 
> repo there and delete all Pinot stuff and move thirdeye directory to root 
> level along with the readme.
> 
> @thirdeye-dev, Please also ping me with your GitHub id, so I can add you to 
> project-thirdeye organization.
> 
> I plan to finish this by tomorrow,  Please let me know if you have any 
> questions.
> 
> -- 
> Xiang Fu

Re: Removing PQL endpoint

[Mayank Shrivastava]

Yupeng, From what I understand we are targeting graduation this quarter, with 
1.0. Does that work for Uber?

Cheers
Mayank

> On Feb 19, 2021, at 9:10 PM, Yupeng Fu  wrote:
> 
> 
> Sidd, from this year we release off the master every a few weeks and don't 
> wait for the next Pinot release.
> 
> +1 to Kishore's suggestion. It's a common practice for Apache projects to 
> deprecate a feature and remove it in the next major version. 
> 
> Yupeng
> 
> 
> 
>> On Fri, Feb 19, 2021 at 7:30 PM kishore g  wrote:
>> Let’s deprecate it in 0.7.0 and remove it when we go to 1.0 and graduate 
>> 
>>> On Fri, Feb 19, 2021 at 6:29 PM siddharth teotia 
>>>  wrote:
>>> Hi Ting, Yupeng
>>> 
>>> PQL endpoint removal won't affect any existing deployments (using PQL) 
>>> unless they upgrade to the new version of Pinot not having PQL endpoints. I 
>>> am not sure how the deployment and release model is at Uber. Do you go from 
>>> one Apache release to another or have some daily/weekly deployment of the 
>>> latest build from Pinot master ? Maybe you can explore not upgrading to the 
>>> next Pinot release until June 2021 when PQL to SQL migration is completed 
>>> in Uber. If this is not possible, we can explore deprecating and disabling 
>>> the endpoint. Keeping the PQL endpoint for long might just increase PQL 
>>> usage. 
>>> 
>>> Thanks
>>> Sidd
>>> 
 On Fri, Feb 19, 2021 at 6:18 PM Ujwala Tulshigiri 
  wrote:
 Yes. This Prestodb PR was merged in release 0.239. However, we are 
 internally using v0.231 and working on upgrading to the latest release 
 0.247.

Re: Removing PQL endpoint

[Mayank Shrivastava]

Thanks Xiang.

Hi Ting,
Will this PR help expedite the move to SQL at Uber?

Cheers,
Mayank

> On Feb 19, 2021, at 5:41 PM, Xiang Fu  wrote:
> 

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

Re: Removing PQL endpoint

[Mayank Shrivastava]

I remember checking with Uber team a while back (forget if Haibo or Yupeng), I 
was told that Uber uses Presto to query Pinot, so it should not matter?

Regards,
Mayank

From: Yupeng Fu 
Sent: Friday, February 19, 2021 3:33 PM
To: dev@pinot.apache.org 
Cc: Ujwala Tulshigiri ; Girish Baliga ; 
Yupeng Fu 
Subject: Re: Removing PQL endpoint

+1 to what Ting suggested. The Presto to SQL migration from Uber side still 
needs a few more months.

Alternatively, could we have a config to disable (and deprecate) the endpoint 
first, with the default value disabled? So the endpoint removal can be done 
together with the PQL cleanup.

Thanks,

On Fri, Feb 19, 2021 at 3:13 PM TING CHEN  wrote:
Hi Sidd,
Uber still uses PQL extensively with a few hundred tables and dozens of use 
cases. It takes us time to move out of PQL. End of Feb is too tight for us to 
complete the migration process. Can you postpone the removal of the query 
endpoints at least to the end of June so that we can complete the migration?

Thanks,
Ting

On Thu, Feb 18, 2021 at 4:06 PM Siddharth Teotia  
wrote:
Hi All,

It's been a while since Pinot has moved to SQL compliant syntax and semantics. 
Calcite SQL compiler has allowed us to move to standard SQL syntax and we will 
continue to leverage it for parsing, compiling and optimizing queries as more 
complex query functionality is added.

However, with legacy PQL code existing, we need to put double effort when 
adding new query functionality to ensure it works for both PQL and SQL. It 
hurts dev productivity. Since SQL is the path forward, we need to start 
removing PQL from Pinot codebase.

Please see this issue created in August last year 
https://github.com/apache/incubator-pinot/issues/5807
 proposing deprecation of PQL.

As a first step, we would be removing the PQL query endpoint on broker (/query) 
and controller (/pql) by end of Feb. This will ensure that users can't use PQL 
to query Pinot. The follow-up cleanup of PQL from the engine (parser, execution 
engine) will be a subsequent task.

Please let us know if you have any questions.

Thanks
Sidd


--
--Yupeng

Re: Podling Pinot Report Reminder - February 2021

[Mayank Shrivastava]

Done.

On Sun, Jan 31, 2021 at 5:18 PM Mayank Shrivastava 
wrote:

> Yes, will do.
>
> On Jan 31, 2021, at 2:14 PM, kishore g  wrote:
>
> 
> Mayank can you please help with this..
>
> On Sun, Jan 31, 2021 at 1:59 PM Felix Cheung 
> wrote:
>
>> Reminder
>>
>>
>> --
>> *From:* jmcl...@apache.org 
>> *Sent:* Wednesday, January 20, 2021 10:20:06 PM
>> *To:* d...@pinot.incubator.apache.org 
>> *Subject:* Podling Pinot Report Reminder - February 2021
>>
>> 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, 17 February 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, February 03).
>>
>> 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/February2021
>>
>> 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
>>
>>

Re: Podling Pinot Report Reminder - February 2021

[Mayank Shrivastava]

Yes, will do.

> On Jan 31, 2021, at 2:14 PM, kishore g  wrote:
> 
> 
> Mayank can you please help with this..
> 
>> On Sun, Jan 31, 2021 at 1:59 PM Felix Cheung  
>> wrote:
>> Reminder
>> 
>> 
>> From: jmcl...@apache.org 
>> Sent: Wednesday, January 20, 2021 10:20:06 PM
>> To: d...@pinot.incubator.apache.org 
>> Subject: Podling Pinot Report Reminder - February 2021
>>  
>> 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, 17 February 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, February 03).
>> 
>> 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/February2021
>> 
>> 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
>> 

Re: [VOTE] Apache Pinot (incubating) 0.6.0 RC1

[Mayank Shrivastava]

+1

Verified using steps described at:
https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate


On Thu, Nov 5, 2020 at 3:48 PM Jialiang Li  wrote:

> Hi Pinot Community,
>
> This is a call for vote to the release Apache Pinot (incubating) version
> 0.6.0.
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.6.0-rc1
>
> Git tag for this release:
> https://github.com/apache/incubator-pinot/tree/release-0.6.0-rc1
>
> Git hash for this release:
> bb646baceafcd9b849a1ecdec7a11203c7027e21
>
> The artifacts have been signed with key: FC4005F4DCB8B2F4, 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.6.0-rc1
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachepinot-1022
>
> 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: Podling Pinot Report Reminder - November 2020

[Mayank Shrivastava]

Hello,
I had updated Pinot section of the wiki page. Is there any other action 
required to complete the report?

Thanks,
Mayank

From: jmcl...@apache.org 
Sent: Wednesday, November 4, 2020 9:35 PM
To: d...@pinot.incubator.apache.org 
Subject: Podling Pinot Report Reminder - November 2020

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, 18 November 2020.
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, November 04).

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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FINCUBATOR%2FNovember2020data=04%7C01%7Cmshrivas%40linkedin.com%7C2825aa294db221c108d8814c97aa%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637401513268804288%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=LnceKZPx%2B566tCANJX0v%2Fut6sdHRl233P2FpVbeIaTo%3Dreserved=0

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

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

[Mayank Shrivastava]

Yupeng, were you able to run mvn clean install -Pbin-dist​?
I ran into build issues while signing of release for the spark connector. Jack 
has a PR on fixing that.

Thanks,
Mayank

From: Yupeng Fu 
Sent: Wednesday, November 4, 2020 8:28 PM
To: dev@pinot.apache.org 
Subject: Re: [VOTE] Apache Pinot (incubating) 0.6.0 RC0


+1

Verified upsert features.

On Mon, Nov 2, 2020 at 4:33 PM Jialiang Li 
mailto:j...@apache.org>> wrote:
Hi Pinot Community,

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

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

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

Git hash for this release:
5fac13978f7093098a13ce91d5061b713c799cf3

The artifacts have been signed with key: FC4005F4DCB8B2F4, 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.6.0-rc0

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

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

--
--Yupeng

Re: Podling Pinot Report Reminder - November 2020

[Mayank Shrivastava]

I have updated the podling report for Apache Pinot. PPMC's/committers please 
take a look in case anything is missed.

Thanks,
Mayank

From: Felix Cheung 
Sent: Sunday, November 1, 2020 11:39 AM
To: dev@pinot.apache.org ; 
d...@pinot.incubator.apache.org 
Subject: Re: Podling Pinot Report Reminder - November 2020

Reminder


From: jmcl...@apache.org 
Sent: Friday, October 23, 2020 10:54:39 PM
To: d...@pinot.incubator.apache.org 
Subject: Podling Pinot Report Reminder - November 2020

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, 18 November 2020.
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, November 04).

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/November2020

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

Re: Podling Pinot Report Reminder - November 2020

[Mayank Shrivastava]

Apologies for the delay, I'll complete this as soon as possible.

Regards,
Mayank

From: Felix Cheung 
Sent: Sunday, November 1, 2020 11:39 AM
To: dev@pinot.apache.org ; 
d...@pinot.incubator.apache.org 
Subject: Re: Podling Pinot Report Reminder - November 2020

Reminder


From: jmcl...@apache.org 
Sent: Friday, October 23, 2020 10:54:39 PM
To: d...@pinot.incubator.apache.org 
Subject: Podling Pinot Report Reminder - November 2020

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, 18 November 2020.
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, November 04).

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/November2020

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

Re: [VOTE] Apache Pinot (incubating) 0.5.0 RC1

[Mayank Shrivastava]

+1

On Sun, Aug 30, 2020 at 1:19 AM H  wrote:

> +1
>
> On Sat, Aug 29, 2020 at 10:05 AM kishore g  wrote:
>
>> +1
>>
>> On Fri, Aug 28, 2020 at 2:21 PM Ting Chen  wrote:
>>
>>> Hi Pinot Community,
>>>
>>> This is a call for a vote to release Apache Pinot (incubating) version
>>> 0.5.0.
>>>
>>> The release candidate:
>>>
>>> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.5.0-rc1
>>>
>>> Git tag for this release:
>>> https://github.com/apache/incubator-pinot/tree/release-0.5.0-rc1
>>>
>>> Git hash for this release:
>>> 3c40ea207f84a36aa60bc2ff9987431d2d746222
>>>
>>> The artifacts have been signed with a key: C650A5210408F8F4, 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.5.0-rc1
>>>
>>> Staging repository:
>>> https://repository.apache.org/content/repositories/orgapachepinot-1015
>>>
>>> Documentation on verifying a release candidate:
>>>
>>> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
>>>
>>> *Special notes for verification*: During this step "diff -r
>>> apache-pinot-incubating-${VERSION}-src pinot-git-src, due to Cluster
>>> Manager UI & Query Console UI revamp (#5684), you might see the extra lines
>>> below. It is fine because they are generated code for the revamped
>>> controller UI.
>>>
>>> Only in
>>> apache-pinot-incubating-0.5.0-src/pinot-controller/src/main/resources: dist
>>>
>>> Only in
>>> apache-pinot-incubating-0.5.0-src/pinot-controller/src/main/resources:
>>> node_modules
>>>
>>> Only in
>>> apache-pinot-incubating-0.5.0-src/pinot-controller/src/main/resources:
>>> package-lock.json
>>>
>>>
>>>
>>> The vote will be open for at least 72 hours or until a 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] Enabling html for Pinot related mailing lists

[Mayank Shrivastava]

+1

> On Jun 13, 2020, at 8:01 PM, Seunghyun Lee  wrote:
> 
> 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

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

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

[Mayank Shrivastava]

+1

Went over the checklist in the doc below:
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FPINOT%2FValidating%2Ba%2Brelease%2Bcandidatedata=02%7C01%7Cmshrivas%40linkedin.com%7C6ec8faafbae34c72e25c08d807071aae%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637267074392293865sdata=ZUWippgZgxD%2FbxhMp6XTWWCppGAAT9jTawb9QhJwugw%3Dreserved=0

From: kishore g 
Sent: Monday, June 8, 2020 4:02 PM
To: dev@pinot.apache.org 
Subject: Re: [VOTE] Apache Pinot (incubating) 0.4.0 RC2

+1

tested stream and batch quickstart

On Mon, Jun 8, 2020 at 3:32 PM Xiang Fu  wrote:

> +1
>
> Xiang
>
> > On 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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fincubator%2Fpinot%2Fapache-pinot-incubating-0.4.0-rc2data=02%7C01%7Cmshrivas%40linkedin.com%7Cc57e9e048f76432728a708d80c000215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637272541462276019sdata=DbvUqeHN%2FQPH1xZbqxOczsILYQeUmiGhyCSI2sbDOjk%3Dreserved=0
> >>
> >> Git tag for this release:
> >> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fincubator-pinot%2Ftree%2Frelease-0.4.0-rc2data=02%7C01%7Cmshrivas%40linkedin.com%7Cc57e9e048f76432728a708d80c000215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637272541462276019sdata=eYvzPON6DIJUDR%2BkugMeI9mRhX2MOLq2lQ7A3gsL3kQ%3Dreserved=0
> >>
> >> Git hash for this release:
> >> 8355d2e0e489a8d127f2e32793671fba505628a8
> >>
> >> The artifacts have been signed with key: 6CC169A6FC19C470, which can be
> >> found in the following KEYS file.
> >> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Frelease%2Fincubator%2Fpinot%2FKEYSdata=02%7C01%7Cmshrivas%40linkedin.com%7Cc57e9e048f76432728a708d80c000215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637272541462276019sdata=lo9BhcrNvEWsT7sYTgpOBLDxUaZkDh9FRf7bPx%2FAHng%3Dreserved=0
> >>
> >> Release notes:
> >> GitHub:
> >>
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fincubator-pinot%2Freleases%2Ftag%2Frelease-0.4.0-rc2data=02%7C01%7Cmshrivas%40linkedin.com%7Cc57e9e048f76432728a708d80c000215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637272541462276019sdata=iJ4SiNBVdNMFXxREV8tZLNA3C8zI2cEm9ZSOKajlmLI%3Dreserved=0
> >>
> >> Staging repository:
> >> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachepinot-1013data=02%7C01%7Cmshrivas%40linkedin.com%7Cc57e9e048f76432728a708d80c000215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637272541462276019sdata=GqvPUIOd0e89WSQOsfB%2FdIiqjJM7znk44U8FoIXYu7E%3Dreserved=0
> >>
> >> Documentation on verifying a release candidate:
> >>
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FPINOT%2FValidating%2Ba%2Brelease%2Bcandidatedata=02%7C01%7Cmshrivas%40linkedin.com%7Cc57e9e048f76432728a708d80c000215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637272541462276019sdata=3c64G5lsg%2BOucmEfvB0U98pWKCaFcxdiAI9MqBOXhIQ%3Dreserved=0
> >>
> >>
> >> 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
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
> For additional commands, e-mail: dev-h...@pinot.apache.org
>
>

Re: Preparing for the upcoming Pinot 0.4.0 release

[Mayank Shrivastava]

I am done with the initial implementation of ThetaSketch, the last commit 
happened yesterday.

Cheers,
Mayank

From: Mayank Shrivastava 
Sent: Wednesday, May 13, 2020 10:33 AM
To: dev@pinot.apache.org 
Subject: Re: Preparing for the upcoming Pinot 0.4.0 release

While ThetaSketch major checkins have gone in, I am still working on making it 
work end to end. Will update on progress by EoD tomorrow.

Thanks,
Mayank

From: H 
Sent: Tuesday, May 12, 2020 9:23 PM
To: dev@pinot.apache.org 
Subject: Re: Preparing for the upcoming Pinot 0.4.0 release

Bumping this thread for 0.4.0 release.

The features called out earlier are either merged or close to being merged.
Kudos to the feature owners for making it in.

I plan to use the master branch as of this *coming Friday May 15th, 7pm PST* as
the release candidate.

I will send another email with the branch info before cutting the release.
Please let me know if there are questions or concerns.

Thanks,
Haibo

On Wed, Apr 29, 2020 at 10:11 PM H  wrote:

> Sounds good. Will revisit this next week.
>
> On Wed, Apr 29, 2020 at 22:08 kishore g  wrote:
>
>> Let’s wait for another week.
>> Want to get the following features
>> In
>> - theta sketch
>> - post Agg
>> - range index
>> - timespec to datetimespec
>>
>>
>> On Wed, Apr 29, 2020 at 9:44 PM H  wrote:
>>
>> > Hi Pinot community,
>> >
>> > I'm preparing for the upcoming Pinot 0.4.0 release. I plan to use the
>> > master branch as of this coming Friday May 1st, 7pm PST.
>> >
>> > I will send another email with the branch info before cutting the
>> > release. Please let me know if there are questions or concerns.
>> >
>> > Thanks,
>> > Haibo
>> >
>>
> --
> Sent from my iPhone
>

Re: Preparing for the upcoming Pinot 0.4.0 release

[Mayank Shrivastava]

While ThetaSketch major checkins have gone in, I am still working on making it 
work end to end. Will update on progress by EoD tomorrow.

Thanks,
Mayank

From: H 
Sent: Tuesday, May 12, 2020 9:23 PM
To: dev@pinot.apache.org 
Subject: Re: Preparing for the upcoming Pinot 0.4.0 release

Bumping this thread for 0.4.0 release.

The features called out earlier are either merged or close to being merged.
Kudos to the feature owners for making it in.

I plan to use the master branch as of this *coming Friday May 15th, 7pm PST* as
the release candidate.

I will send another email with the branch info before cutting the release.
Please let me know if there are questions or concerns.

Thanks,
Haibo

On Wed, Apr 29, 2020 at 10:11 PM H  wrote:

> Sounds good. Will revisit this next week.
>
> On Wed, Apr 29, 2020 at 22:08 kishore g  wrote:
>
>> Let’s wait for another week.
>> Want to get the following features
>> In
>> - theta sketch
>> - post Agg
>> - range index
>> - timespec to datetimespec
>>
>>
>> On Wed, Apr 29, 2020 at 9:44 PM H  wrote:
>>
>> > Hi Pinot community,
>> >
>> > I'm preparing for the upcoming Pinot 0.4.0 release. I plan to use the
>> > master branch as of this coming Friday May 1st, 7pm PST.
>> >
>> > I will send another email with the branch info before cutting the
>> > release. Please let me know if there are questions or concerns.
>> >
>> > Thanks,
>> > Haibo
>> >
>>
> --
> Sent from my iPhone
>

Re: Preconditions, Annotations, Exceptions, Nulls, and Optionals

[Mayank Shrivastava]

Hi Charlie,
Thanks for taking the initiative on this one. My recommendation would be to 
document all such areas, and then open it up for consensus on the convention to 
follow. I think @Jackie Jiang has done similar 
cleanup in the past (specific to Nonnull vs 
Nullable), would be good to build up on that.

I do agree with Kishore though, we should not trade for performance 
(specifically in query execution), and keep that in mind when discussing.

Cheers,
Mayank

From: Charlie Summers 
Sent: Saturday, May 9, 2020 9:25 PM
To: d...@pinot.incubator.apache.org 
Subject: Preconditions, Annotations, Exceptions, Nulls, and Optionals

Hey Pinot team,

My name is Charlie Summers and I'm a new contributor to the project. As
I've started diving into the code, I'm not seeing a consistent pattern for
how we handle unexpected behavior in the project.

In some places we're throwing exceptions. In some places we log an error
message then continue, returning a Null if a value is expected and having
calling code handle the Null. When handling Nulls, we sometimes
use @Nullable and @NotNull annotations and sometimes use
Preconditions.checkNotNull().

I was chatting a bit with Kishore about this in Slack - he didn't have a
strong preference for how to handle these things but was concerned about
the performance implications of over-using Annotations and Precondition
checks.

What are all of your feelings on the matter? Personally I'm a fan of
throwing Exceptions should state truly be exceptional instead of limping on
and then handling a Null later. Where there's a need for a
partially-functioning state or values may genuinely not be present, I'm a
fan of Optionals (about their performance:
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackoverflow.com%2Fquestions%2F34696884%2Fperformance-of-java-optional%2F34697019data=02%7C01%7Cmshrivas%40linkedin.com%7C10831b986b9647b5e19e08d7f49a3fce%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637246815649018974sdata=bE%2FzJcow6K9VFmyzewNjmiuqP2REm8CgulR6PtTkV2g%3Dreserved=0
).

What have you all found to be effective? And definitely let me know if
there is a more consistent standard that I'm missing because I've only just
started dabbling with the code base.

Cheers,
Charlie Summers

Re: Issue: Data-inconsistency during segment push

[Mayank Shrivastava]

Yes, the high level idea works. We will need to iron out the details a bit. Few 
examples:


  1.  For refresh use cases with large data size though, even the servers may 
non-trivial amount of time to download segments. We need to wait until all new 
version is ONLINE in external view before making the version switch. This 
implies that local storage on servers need to be doubled.
  2.  There will also be details to take care of such as when one of the 
segments does not come ONLINE in the new version due to an error, how long 
would we wait before incrementing the version.
  3.  Handling various failure scenarios such as rest-api call failing/timeouts 
etc.

Will start a doc for the same.


Thanks,
Mayank

From: kishore g 
Sent: Monday, April 6, 2020 8:15 PM
To: dev@pinot.apache.org 
Subject: Re: Issue: Data-inconsistency during segment push

One suggestion - high level

Put the time boundary in ZK (may be in /propertystore/table/routingInfo).

This can be updated via one of the following
- The upload job can set this via controller API after everything is pushed
- Controller can do this periodically
- Anything else

Brokers watch for this node and use the entry in routingInfo
- to come up with time boundary for APPEND use case
- use the version number for refresh use case to change to a newer version.

Append and Refresh use cases use different routing table provider
implementations.




On Thu, Mar 5, 2020 at 6:20 AM Mayank Shrivastava 
wrote:

> Today, we have an issue in Pinot, where data is in an inconsistent state
> during segment push, and the query results may be incorrect. This issue
> becomes more critical for enterprise applications to maintain customer
> trust, more so in case of REFRESH use cases with large data size, causing
> the period of inconsistency can be quite large. There are various flavors
> of this problem:
>
> 1. In APPEND use cases, the time-boundary is updated as soon as the first
> segment from the periodic push arrives. This causes queries to hit the
> offline table for period which does not have complete data in the offline
> table.
>
> 2. For REFRESH use cases, there is no requirement for segments to be
> partitioned, so data can be in an entirely inconsistent state during the
> push time.
>
> 3. We are seeing enterprise applications that create different
> denormalizations from source data(s) creating multiple tables in Pinot. In
> these cases, the same application queries multiple tables for their
> product. And there's increasing asks to ensure some sort of inter-table
> consistencies (provided client side takes care of synchronized data pushes
> to these tables).
>
> For 1 and 2. there are several potential bottlenecks that may increase the
> push time, including Pinot controller, deep-store and network b/w. For our
> cases, it seems that the biggest bottleneck is the network b/w between
> controller and compute farm that creates the segment.
>
> Next steps: Exchange ideas, and create proposals for the problems above.
>
> Cheers,
> Mayank
>

Re: Apache Pinot Docs repo name

[Mayank Shrivastava]

I get a 404 for these links.

From: Xiang Fu 
Sent: Wednesday, March 25, 2020 10:18 AM
To: dev@pinot.apache.org 
Subject: Re: Apache Pinot Docs repo name

How about  
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fincubator-pinot-docsdata=02%7C01%7Cmshrivas%40linkedin.com%7C62c398c976b4451aaaba08d7d0e098c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637207535363104332sdata=9nJ52o%2FpW2BcbMbMXSRHqVtgHB%2FXed5XRnL6V4DC05w%3Dreserved=0
 


Similar to
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fincubator-pinot-sitedata=02%7C01%7Cmshrivas%40linkedin.com%7C62c398c976b4451aaaba08d7d0e098c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637207535363104332sdata=%2Boinsn5ned8ZJF4pzfhG3Huby51247WhLI5kGxp4v0w%3Dreserved=0
 

https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fincubator-pinotdata=02%7C01%7Cmshrivas%40linkedin.com%7C62c398c976b4451aaaba08d7d0e098c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637207535363104332sdata=r1swYIJYXfWkckqrm9xxHONE8MB11yHcq4mDPdK6wro%3Dreserved=0
 


Best,

Xiang


> On Mar 25, 2020, at 10:16 AM, kishore g  wrote:
>
> Hi,
>
> I am creating a new repo for pinot docs. Any preference on the name?
>
> pinot-docs?
>
> thanks,
> Kishore G

Re: Apache Pinot Docs repo name

[Mayank Shrivastava]

pinot-docs lgtm.

-mayank

From: kishore g 
Sent: Wednesday, March 25, 2020 10:16 AM
To: dev@pinot.apache.org 
Subject: Apache Pinot Docs repo name

Hi,

I am creating a new repo for pinot docs. Any preference on the name?

pinot-docs?

thanks,
Kishore G

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

[Mayank Shrivastava]

+1

On Mon, Mar 16, 2020 at 2:09 AM Fu Xiang  wrote:

> Hi Pinot Community,
>
> This is a call for vote to the release Apache Pinot (incubating) version
> 0.3.0.
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.3.0-rc2
>
> Git tag for this release:
> https://github.com/apache/incubator-pinot/tree/release-0.3.0-rc2
>
> Git hash for this release:
> 9b2dc20c07dec6cf33df08cd996e8202c3ba
>
> The artifacts have been signed with key: CDEDB21B862F6C66, 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.3.0-rc2
> GitBook:
> https://apache-pinot.gitbook.io/apache-pinot-cookbook/releases/0.3.0
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachepinot-1010
>
> Documentation on verifying a release candidate:
>
> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
>
> *Updates from 0.3.0 RC0*:
> - Fixing the issue of thread local DocIdSet in ExpressionFilterOperator.
> - Fixing the issue of copying sample data from distribution jar for
> PinotQuickStarts.
>
> *Updates from 0.3.0 RC1*:
> - Support schema evolution for consuming segment.
> - Fixed the bug in default value provider classes.
> - Fixed the bug when no segment exists in RealtimeSegmentSelector.
> - Multiple tooling enhancements and fixes for QuickStarts.
>
> 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.3.0 RC1

[Mayank Shrivastava]

+1

On Mon, Mar 9, 2020 at 1:25 PM Subbu Subramaniam 
wrote:

> +1
>
> -Subbu
>
> On 2020/03/09 18:29:43, Fu Xiang  wrote:
> > Hi Pinot Community,
> >
> > This is a call for vote to the release Apache Pinot (incubating) version
> > 0.3.0.
> >
> > The release candidate:
> >
> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.3.0-rc1
> >
> > Git tag for this release:
> > https://github.com/apache/incubator-pinot/tree/release-0.3.0-rc1
> >
> > Git hash for this release:
> > 4a878f21aac289c84f289e47958de64850b7bb81
> >
> > The artifacts have been signed with key: CDEDB21B862F6C66, 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.3.0-rc1
> > GitBook:
> > https://apache-pinot.gitbook.io/apache-pinot-cookbook/releases/0.3.0
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachepinot-1008
> > 
> >
> > Documentation on verifying a release candidate:
> >
> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
> >
> > Updates from 0.3.0 RC0
> > - Fixing the issue of thread local DocIdSet in ExpressionFilterOperator
> > - Fixing the issue of copying sample data from distribution jar for
> > PinotQuickStarts
> >
> > 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: Pinot-incubator question about unofficial publications

[Mayank Shrivastava]

SGTM

On Mon, Mar 9, 2020 at 10:48 AM kishore g  wrote:

> I am also ok with this.
>
> On Mon, Mar 9, 2020 at 10:46 AM Subbu Subramaniam 
> wrote:
>
> > No concerns.
> >
> > -Subbu
> >
> > On 2020/03/03 22:52:08, kishore g  wrote:
> > > This looks good to me. Adding dev to see if others have any concerns.
> > >
> > > On Tue, Mar 3, 2020 at 1:49 PM Szczepan Faber 
> > wrote:
> > >
> > > > Hello ASF Pinot mentors!
> > > >
> > > >
> > > >
> > > > We are looking for a way for Apache Pinot (incubator) to host
> nightly,
> > > > unofficial binary publications. Can you review our high-level
> approach
> > and
> > > > let us know if it aligns with ASF release policy? The information we
> > found
> > > > in ASF release policy seems to be compliant with our idea, but we
> > wanted to
> > > > double check with you.
> > > >
> > > >
> > > >
> > > > - Every night a CI job builds Pinot and publishes binaries to
> > > > "pinot-nightly" Bintray repository
> > > >
> > > >  - Example versioning scheme: "0.3.0-dev.1", "0.3.0-dev.2"
> > > >
> > > > - The publications are not announced and not present in well-known
> > public
> > > > repositories
> > > >
> > > >
> > > >
> > > > ASF policy about test/nightly publications (
> > > > http://www.apache.org/legal/release-policy.html#host-rc):
> > > >
> > > >
> > > >
> > > > "Test packages are for use by consenting developers and interested
> > > > community members only, so they should not be hosted or linked on
> pages
> > > > intended for end users. They should not be mirrored; only blessed GA
> > > > releases should be mirrored."
> > > >
> > > >
> > > >
> > > > We'd appreciate guidance and review of our approach. We’re happy to
> > > > describe more details if needed!
> > > >
> > > > Thank you!
> > > >
> > > > --
> > > >
> > > > Szczepan Faber - tech lead Dev Tools (
> > > > https://www.linkedin.com/in/szczepanf/)
> > > >
> > > > How to give great code reviews
> > > > ?
> > > >
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
> > For additional commands, e-mail: dev-h...@pinot.apache.org
> >
> >
>

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

[Mayank Shrivastava]

+1

On Thu, Mar 5, 2020 at 12:15 PM Neha Pawar  wrote:

> +1
>
> 
>
>
> On Thu, Mar 5, 2020 at 12:16 AM Siddharth Teotia
>  wrote:
>
> > Running on Mac (Catalina 10.15.2) with JDK 8
> > 
> > From: Xiang Fu 
> > Sent: Thursday, March 5, 2020 12:08 AM
> > To: dev@pinot.apache.org 
> > Subject: Re: [VOTE] Apache Pinot (incubating) 0.3.0 RC0
> >
> > Which environment you are running this from?
> >
> > Current batch/stream/hybrid QuickStarts are passed from Travis for
> > OracleJDK 8 & 11 and OpenJDK 8 & 11.
> >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftravis-ci.org%2Fapache%2Fincubator-pinot%2Fbuilds%2F658378180%3Futm_medium%3Dnotification%26utm_source%3Dgithub_statusdata=02%7C01%7Csteotia%40linkedin.com%7Cdb30b49f3dd54a7ebb2108d7c0dc7d35%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637189925537456673sdata=i5Uvt1nd9v6pUajFVemEhkUKT2IQJDDKGNYYjpyQ7T0%3Dreserved=0
> > <
> >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftravis-ci.org%2Fapache%2Fincubator-pinot%2Fbuilds%2F658378180%3Futm_medium%3Dnotification%26utm_source%3Dgithub_statusdata=02%7C01%7Csteotia%40linkedin.com%7Cdb30b49f3dd54a7ebb2108d7c0dc7d35%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637189925537456673sdata=i5Uvt1nd9v6pUajFVemEhkUKT2IQJDDKGNYYjpyQ7T0%3Dreserved=0
> > >
> >
> > I tried to run this on my Mac and works.
> >
> > ➜ bin/quick-start-batch.sh
> > * Starting Zookeeper, controller, broker and server *
> > Executing command: StartZookeeper -zkPort 2123 -dataDir
> > /var/folders/kp/v8smb2f11tg6q2grpwkq7qnhgn/T//PinotAdmin/zkData
> > Start zookeeper at localhost:2123 in thread main
> > Executing command: StartController -clusterName QuickStartCluster
> > -controllerHost 127.0.0.1 -controllerPort 9000 -dataDir
> > /var/folders/kp/v8smb2f11tg6q2grpwkq7qnhgn/T//PinotController
> > -zkAddress localhost:2123
> > Invalid instance setup, missing znode path:
> > /QuickStartCluster/CONFIGS/PARTICIPANT/Controller_127.0.0.1_9000
> > Invalid instance setup, missing znode path:
> > /QuickStartCluster/INSTANCES/Controller_127.0.0.1_9000/MESSAGES
> > Invalid instance setup, missing znode path:
> > /QuickStartCluster/INSTANCES/Controller_127.0.0.1_9000/CURRENTSTATES
> > Invalid instance setup, missing znode path:
> > /QuickStartCluster/INSTANCES/Controller_127.0.0.1_9000/STATUSUPDATES
> > Invalid instance setup, missing znode path:
> > /QuickStartCluster/INSTANCES/Controller_127.0.0.1_9000/ERRORS
> > Mar 05, 2020 12:01:46 AM
> org.glassfish.grizzly.http.server.NetworkListener
> > start
> > INFO: Started listener bound to [0.0.0.0:9000]
> > Mar 05, 2020 12:01:46 AM org.glassfish.grizzly.http.server.HttpServer
> start
> > INFO: [HttpServer] Started.
> > Executing command: StartBroker -brokerHost null -brokerPort 8000
> > -zkAddress localhost:2123
> > Mar 05, 2020 12:01:50 AM
> org.glassfish.grizzly.http.server.NetworkListener
> > start
> > INFO: Started listener bound to [0.0.0.0:8000]
> > Mar 05, 2020 12:01:50 AM org.glassfish.grizzly.http.server.HttpServer
> start
> > INFO: [HttpServer-1] Started.
> > Invalid instance setup, missing znode path:
> > /QuickStartCluster/CONFIGS/PARTICIPANT/Broker_127.0.0.1_8000
> > Invalid instance setup, missing znode path:
> > /QuickStartCluster/INSTANCES/Broker_127.0.0.1_8000/MESSAGES
> > Invalid instance setup, missing znode path:
> > /QuickStartCluster/INSTANCES/Broker_127.0.0.1_8000/CURRENTSTATES
> > Invalid instance setup, missing znode path:
> > /QuickStartCluster/INSTANCES/Broker_127.0.0.1_8000/STATUSUPDATES
> > Invalid instance setup, missing znode path:
> > /QuickStartCluster/INSTANCES/Broker_127.0.0.1_8000/ERRORS
> > Executing command: StartServer -clusterName QuickStartCluster -serverHost
> > 127.0.0.1 -serverPort 7000 -serverAdminPort 7500 -dataDir
> > /tmp/1583395302452/PinotServerData0 -segmentDir
> > /tmp/1583395302452/PinotServerSegment0 -zkAddress localhost:2123
> > Invalid instance setup, missing znode path:
> > /QuickStartCluster/CONFIGS/PARTICIPANT/Server_127.0.0.1_7000
> > Invalid instance setup, missing znode path:
> > /QuickStartCluster/INSTANCES/Server_127.0.0.1_7000/MESSAGES
> > Invalid instance setup, missing znode path:
> > /QuickStartCluster/INSTANCES/Server_127.0.0.1_7000/CURRENTSTATES
> > Invalid instance setup, missing znode path:
> > /QuickStartCluster/INSTANCES/Server_127.0.0.1_7000/STATUSUPDATES
> > Invalid instance setup, missing znode path:
> > /QuickStartCluster/INSTANCES/Server_127.0.0.1_7000/ERRORS
> > Mar 05, 2020 12:01:54 AM
> org.glassfish.grizzly.http.server.NetworkListener
> > start
> > INFO: Started listener bound to [0.0.0.0:7500]
> > Mar 05, 2020 12:01:54 AM org.glassfish.grizzly.http.server.HttpServer
> start
> > INFO: [HttpServer-2] Started.
> > * Adding baseballStats table *
> > Executing command: AddTable -tableConfigFile
> >
> /private/tmp/rc0-test/rc-test/apache-pinot-incubating-0.3.0-bin/quickStartData1583395302399/baseballStats_offline_table_config.json
> > 

Re: Jepsen testing for Pinot

[Mayank Shrivastava]

Agree on the derived systems part. One thing to explore though would be if this 
can be applied to the real-time segment commit protocol.

Cheers,
Mayank

Sent from my iPhone

> On Feb 24, 2020, at 1:17 PM, kishore g  wrote:
> 
> We should define a new set of tests for derived systems
> 
>> On Mon, Feb 24, 2020 at 1:13 PM kishore g  wrote:
>> 
>> Does not make sense for Pinot
>> 
>> On Mon, Feb 24, 2020 at 1:10 PM siddharth teotia <
>> siddharthteo...@gmail.com> wrote:
>> 
>>> I think at some point we should think about using Jepsen for
>>> safety-testing
>>> of Pinot. While the tool has been predominantly used in databases that
>>> have distributed transactions, extensive node communication, algorithms
>>> relying on clock-skew, it can still be used to introduced faults in the
>>> cluster and check for existence of problems.
>>> 
>>> I believe Helix and ZK are the perfect candidates (but that work is going
>>> to be orthogonal to Pinot). However, since we use these extensively, it
>>> might still be worthwhile to see if Jepsen framework can expose some
>>> problems in Pinot.
>>> 
>>> https://jepsen.io/
>>> 
>>> Thanks,
>>> Sidd
>>> 
>> 

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

Re: Remove index from segment

[Mayank Shrivastava]

+1 on the idea. Curious though, how often do you see the index being removed 
from table config? It has been a rare event in my experience thus far.

Sent from my iPhone

> On Feb 11, 2020, at 2:37 PM, kishore g  wrote:
> 
> Currently, we only support adding indices to the pinot segment. If the
> index is removed from table config, we dont load it but continue to keep it
> in the segment. The only drawback with this is additional usage of disk
> space.
> 
> We should enhance the segment preprocessor to have the ability to rewrite
> the segment.

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

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

[Mayank Shrivastava]

+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: Pinot web console

[Mayank Shrivastava]

+1, seems quite useful.

From: kishore g 
Sent: Sunday, April 21, 2019 10:13 AM
To: dev@pinot.apache.org
Subject: Pinot web console

https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fclaudemamo%2Fkafka-web-consoledata=02%7C01%7Cmshrivas%40linkedin.com%7Cc4e32bebf31a40f816e908d6c67cc003%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636914636435882430sdata=SQQPV7%2F5ixQSYThQZyjiqbugFpKmvgoFGxKI93n2jvo%3Dreserved=0

How about having something like this for Pinot?