Design doc for Geospatial support in Pinot

[Yupeng Fu]

Hi all,

Please take a look at this issue
 and review this
design doc "Geospatial support in Pinot

" .
We can discuss questions and feedback on the design doc.

Thanks,
-- 
--Yupeng

Re: Design doc for Geospatial support in Pinot

[Yupeng Fu]

Unfortunately I was not able to configure the sharing policy for anyone
outside the company with the link to access, due to certain restrictions.
Please request access and I will grant it.
I will also put up a version under the Apache Wiki soon.

Cheers,

On Mon, Apr 20, 2020 at 9:21 PM Mayank Shrivastava 
wrote:

> Could you please open up read/comment access?
>
> Thanks,
> mayank
>
> On Mon, Apr 20, 2020 at 6:48 PM Yupeng Fu  wrote:
>
> > Hi all,
> >
> > Please take a look at this issue
> > <https://github.com/apache/incubator-pinot/issues/5280> and review this
> > design doc "Geospatial support in Pinot
> > <
> >
> https://docs.google.com/document/d/1Mkm5RHS_tof-vIUt5-UNeOgRYSBAN6M_pN-hedV6Q0g/edit#heading=h.i45os595j1sp
> > >
> > " .
> > We can discuss questions and feedback on the design doc.
> >
> > Thanks,
> > --
> > --Yupeng
> >
>


-- 
--Yupeng

Re: Design doc for Geospatial support in Pinot

[Yupeng Fu]

A copy of the proposal is added to Apache wiki at here
<https://cwiki.apache.org/confluence/display/PINOT/%5BProposal%5D+Geospatial+support+in+Pinot>.
Please keep the discussion on the google doc.

Cheers,

On Mon, Apr 20, 2020 at 9:59 PM Yupeng Fu  wrote:

> Unfortunately I was not able to configure the sharing policy for anyone
> outside the company with the link to access, due to certain restrictions.
> Please request access and I will grant it.
> I will also put up a version under the Apache Wiki soon.
>
> Cheers,
>
> On Mon, Apr 20, 2020 at 9:21 PM Mayank Shrivastava 
> wrote:
>
>> Could you please open up read/comment access?
>>
>> Thanks,
>> mayank
>>
>> On Mon, Apr 20, 2020 at 6:48 PM Yupeng Fu  wrote:
>>
>> > Hi all,
>> >
>> > Please take a look at this issue
>> > <https://github.com/apache/incubator-pinot/issues/5280> and review this
>> > design doc "Geospatial support in Pinot
>> > <
>> >
>> https://docs.google.com/document/d/1Mkm5RHS_tof-vIUt5-UNeOgRYSBAN6M_pN-hedV6Q0g/edit#heading=h.i45os595j1sp
>> > >
>> > " .
>> > We can discuss questions and feedback on the design doc.
>> >
>> > Thanks,
>> > --
>> > --Yupeng
>> >
>>
>
>
> --
> --Yupeng
>


-- 
--Yupeng

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

[Yupeng Fu]

+1

Verified upsert features.

On Mon, Nov 2, 2020 at 4:33 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-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: [VOTE] Apache Pinot (incubating) 0.6.0 RC0

[Yupeng Fu]

I see. I didn't run into that issue coz in order to speed up the internal
server compilation, I excluded a few modules including Spark connector.
Yes, tried again with the full rc0, I run into the same compilation issue
as you said.

On Wed, Nov 4, 2020 at 10:01 PM Mayank Shrivastava 
wrote:

> 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  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
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fincubator%2Fpinot%2Fapache-pinot-incubating-0.6.0-rc0&data=04%7C01%7Cmshrivas%40linkedin.com%7C97828c6ad0df42dd300708d88145db2e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637401484321508860%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=eWlKAse84u%2FmplIJAouZXJr44oC8Hp%2Fe%2FkV35HtjkAw%3D&reserved=0>
>
> Git tag for this release:
> https://github.com/apache/incubator-pinot/tree/release-0.6.0-rc0
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fincubator-pinot%2Ftree%2Frelease-0.6.0-rc0&data=04%7C01%7Cmshrivas%40linkedin.com%7C97828c6ad0df42dd300708d88145db2e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637401484321508860%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=54nd9vjYoMsQ%2B%2FHyU9L%2FLmOKKwCrWT%2F6rN4crds8p2A%3D&reserved=0>
>
> 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
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Frelease%2Fincubator%2Fpinot%2FKEYS&data=04%7C01%7Cmshrivas%40linkedin.com%7C97828c6ad0df42dd300708d88145db2e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637401484321518856%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=SPC1HJ%2BUH9LOIm%2Bd0LsvGZppnH%2FbhD3QxR2v3uvZyvs%3D&reserved=0>
>
> Release notes:
> https://github.com/apache/incubator-pinot/releases/tag/release-0.6.0-rc0
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fincubator-pinot%2Freleases%2Ftag%2Frelease-0.6.0-rc0&data=04%7C01%7Cmshrivas%40linkedin.com%7C97828c6ad0df42dd300708d88145db2e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637401484321528851%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=fMra%2FD9orq8vU3HeugHG%2BVoC%2Byts5dtMStEVX3Yq058%3D&reserved=0>
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachepinot-1021
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachepinot-1021&data=04%7C01%7Cmshrivas%40linkedin.com%7C97828c6ad0df42dd300708d88145db2e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637401484321528851%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=P%2B%2BaTe3ya%2BJ93ZsajYOrrUC%2FaPgrTq8k2O%2BLMaetM5M%3D&reserved=0>
>
> Documentation on verifying a release candidate:
>
> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FPINOT%2FValidating%2Ba%2Brelease%2Bcandidate&data=04%7C01%7Cmshrivas%40linkedin.com%7C97828c6ad0df42dd300708d88145db2e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637401484321538848%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=pdZSjlcQdGqCKJfsd%2Bfw3hgIgBUXMf4Mdzmv8sJSAoo%3D&reserved=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
>
> --
> --Yupeng
>


-- 
--Yupeng

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

[Yupeng Fu]

Yes. All related PRs were merged.

On Wed, Nov 4, 2020 at 11:18 PM Jialiang Li  wrote:

> Hi Yupeng,
>
> Thanks for reaching out. Can you help confirm that all the PRs of upsert
> features are included in this release?
>
> I'm cutting another release. So it'd be good if you can help confirm that.
>
> Thanks,
> Jack
>
> On 2020/11/05 06:01:05, Mayank Shrivastava 
> wrote:
> > 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  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
> <
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fincubator%2Fpinot%2Fapache-pinot-incubating-0.6.0-rc0&data=04%7C01%7Cmshrivas%40linkedin.com%7C97828c6ad0df42dd300708d88145db2e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637401484321508860%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=eWlKAse84u%2FmplIJAouZXJr44oC8Hp%2Fe%2FkV35HtjkAw%3D&reserved=0
> >
> >
> > Git tag for this release:
> > https://github.com/apache/incubator-pinot/tree/release-0.6.0-rc0<
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fincubator-pinot%2Ftree%2Frelease-0.6.0-rc0&data=04%7C01%7Cmshrivas%40linkedin.com%7C97828c6ad0df42dd300708d88145db2e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637401484321508860%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=54nd9vjYoMsQ%2B%2FHyU9L%2FLmOKKwCrWT%2F6rN4crds8p2A%3D&reserved=0
> >
> >
> > 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<
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Frelease%2Fincubator%2Fpinot%2FKEYS&data=04%7C01%7Cmshrivas%40linkedin.com%7C97828c6ad0df42dd300708d88145db2e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637401484321518856%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=SPC1HJ%2BUH9LOIm%2Bd0LsvGZppnH%2FbhD3QxR2v3uvZyvs%3D&reserved=0
> >
> >
> > Release notes:
> > https://github.com/apache/incubator-pinot/releases/tag/release-0.6.0-rc0
> <
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fincubator-pinot%2Freleases%2Ftag%2Frelease-0.6.0-rc0&data=04%7C01%7Cmshrivas%40linkedin.com%7C97828c6ad0df42dd300708d88145db2e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637401484321528851%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=fMra%2FD9orq8vU3HeugHG%2BVoC%2Byts5dtMStEVX3Yq058%3D&reserved=0
> >
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachepinot-1021<
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachepinot-1021&data=04%7C01%7Cmshrivas%40linkedin.com%7C97828c6ad0df42dd300708d88145db2e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637401484321528851%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=P%2B%2BaTe3ya%2BJ93ZsajYOrrUC%2FaPgrTq8k2O%2BLMaetM5M%3D&reserved=0
> >
> >
> > Documentation on verifying a release candidate:
> >
> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
> <
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FPINOT%2FValidating%2Ba%2Brelease%2Bcandidate&data=04%7C01%7Cmshrivas%40linkedin.com%7C97828c6ad0df42dd300708d88145db2e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637401484321538848%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&s

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

[Yupeng Fu]

+1

Verified upsert features.

On Mon, Nov 9, 2020 at 1:57 PM Mayank Shrivastava 
wrote:

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

-- 
--Yupeng

Re: Removing PQL endpoint

[Yupeng Fu]

+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: Removing PQL endpoint

[Yupeng Fu]

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 <
> siddharthteo...@gmail.com> 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.
>>>
>>

[VOTE] Apache Pinot (incubating) 0.7.0 RC0

[Yupeng Fu]

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: [VOTE] Apache Pinot (incubating) 0.7.0 RC0

[Yupeng Fu]

I didn't see such error on console out, neither on controller/server logs.

Could you add more info on how to reproduce it?

On Sat, Mar 6, 2021 at 2:12 AM Xiang Fu  wrote:

> I’m seeing this issue when running bin/quick-start-batch.sh
>
> ```
> Exception while executing a state transition task baseballStats_OFFLINE_0
> java.lang.reflect.InvocationTargetException: null
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[?:1.8.0_232]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[?:1.8.0_232]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.8.0_232]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_232]
> at
> org.apache.helix.messaging.handling.HelixStateTransitionHandler.invoke(HelixStateTransitionHandler.java:404)
> ~[pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
> at
> org.apache.helix.messaging.handling.HelixStateTransitionHandler.handleMessage(HelixStateTransitionHandler.java:331)
> [pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
> at org.apache.helix.messaging.handling.HelixTask.call(HelixTask.java:97)
> [pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
> at org.apache.helix.messaging.handling.HelixTask.call(HelixTask.java:49)
> [pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_232]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [?:1.8.0_232]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [?:1.8.0_232]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_232]
> Caused by: java.lang.NoSuchMethodError:
> java.nio.ByteBuffer.position(I)Ljava/nio/ByteBuffer;
> at
> org.apache.pinot.core.segment.creator.impl.inv.BitmapInvertedIndexWriter.(BitmapInvertedIndexWriter.java:60)
> ~[pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
> at
> org.apache.pinot.core.segment.creator.impl.inv.OffHeapBitmapInvertedIndexCreator.seal(OffHeapBitmapInvertedIndexCreator.java:181)
> ~[pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
> at
> org.apache.pinot.core.segment.index.loader.invertedindex.InvertedIndexHandler.createInvertedIndexForColumn(InvertedIndexHandler.java:122)
> ~[pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
> at
> org.apache.pinot.core.segment.index.loader.invertedindex.InvertedIndexHandler.createInvertedIndices(InvertedIndexHandler.java:70)
> ~[pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
> at
> org.apache.pinot.core.segment.index.loader.SegmentPreProcessor.process(SegmentPreProcessor.java:112)
> ~[pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
> at
> org.apache.pinot.core.indexsegment.immutable.ImmutableSegmentLoader.load(ImmutableSegmentLoader.java:99)
> ~[pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
> at
> org.apache.pinot.core.data.manager.offline.OfflineTableDataManager.addSegment(OfflineTableDataManager.java:52)
> ~[pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
> at
> org.apache.pinot.server.starter.helix.HelixInstanceDataManager.addOfflineSegment(HelixInstanceDataManager.java:121)
> ~[pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
> at
> org.apache.pinot.server.starter.helix.SegmentFetcherAndLoader.addOrReplaceOfflineSegment(SegmentFetcherAndLoader.java:158)
> ~[pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
> at
> org.apache.pinot.server.starter.helix.SegmentOnlineOfflineStateModelFactory$SegmentOnlineOfflineStateModel.onBecomeOnlineFromOffline(SegmentOnlineOfflineStateModelFactory.java:162)
> ~[pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
> ... 12 more
> Default rollback method invoked on error. Error Code: ERROR
> ```
>
> On Mar 5, 2021, at 6:04 PM, Felix Cheung 
> wrote:
>
> signing key should use a @apache.org address
>
> - incubating in name
> - signature and hash fine
> - DISCLAIMER is fine
> - LICENSE is fine
>
> NOTICE should have year 2021?
> Copyright 2018-2020 The Apache Software Foundation
> https://www.apache.org/legal/src-headers.html#notice
>
> - No unexpected binary files (some test .gz files)
> - All source files have ASF headers
>
>
> ---

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

[Yupeng Fu]

On Fri, Mar 5, 2021 at 6:05 PM Felix Cheung 
wrote:

> signing key should use a @apache.org address
>
Thanks for pointing it out. Updated the email address on the GPG key and
the signing key stays the same.

>
> - incubating in name
> - signature and hash fine
> - DISCLAIMER is fine
> - LICENSE is fine
>
> NOTICE should have year 2021?
> Copyright 2018-2020 The Apache Software Foundation
> https://www.apache.org/legal/src-headers.html#notice
>
I think so. Will package and upload a new binary, if no code changes for
RC1 needed.

>
>
> - No unexpected binary files (some test .gz files)
> - All source files have ASF headers
>
>
> --
> *From:* Yupeng Fu 
> *Sent:* Friday, March 5, 2021 9:28:24 AM
> *To:* dev@pinot.apache.org 
> *Subject:* [VOTE] Apache Pinot (incubating) 0.7.0 RC0
>
> 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
>


-- 
--Yupeng

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

[Yupeng Fu]

Confirmed the issue with Java 8.
It turns out that during release, we have to use Java 8 for compilation.
Read more about the details at
https://www.morling.dev/blog/bytebuffer-and-the-dreaded-nosuchmethoderror/

Will cut a RC1.

On Sat, Mar 6, 2021 at 5:31 PM Xiang Fu  wrote:

> I used this binary directory: apache-pinot-incubating-0.7.0-bin
>
> My java version is:
> ```
> openjdk version "1.8.0_232"
> OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_232-b09)
> OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.232-b09, mixed mode)
> ```
>
> I also tried to build the src directory and that has no problem.
>
>
>
> On Mar 6, 2021, at 10:06 AM, Yupeng Fu  wrote:
>
> I didn't see such error on console out, neither on controller/server logs.
>
> Could you add more info on how to reproduce it?
>
> On Sat, Mar 6, 2021 at 2:12 AM Xiang Fu  wrote:
>
>> I’m seeing this issue when running bin/quick-start-batch.sh
>>
>> ```
>> Exception while executing a state transition task baseballStats_OFFLINE_0
>> java.lang.reflect.InvocationTargetException: null
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> ~[?:1.8.0_232]
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> ~[?:1.8.0_232]
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> ~[?:1.8.0_232]
>> at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_232]
>> at
>> org.apache.helix.messaging.handling.HelixStateTransitionHandler.invoke(HelixStateTransitionHandler.java:404)
>> ~[pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
>> at
>> org.apache.helix.messaging.handling.HelixStateTransitionHandler.handleMessage(HelixStateTransitionHandler.java:331)
>> [pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
>> at org.apache.helix.messaging.handling.HelixTask.call(HelixTask.java:97)
>> [pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
>> at org.apache.helix.messaging.handling.HelixTask.call(HelixTask.java:49)
>> [pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
>> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_232]
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>> [?:1.8.0_232]
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>> [?:1.8.0_232]
>> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_232]
>> Caused by: java.lang.NoSuchMethodError:
>> java.nio.ByteBuffer.position(I)Ljava/nio/ByteBuffer;
>> at
>> org.apache.pinot.core.segment.creator.impl.inv.BitmapInvertedIndexWriter.(BitmapInvertedIndexWriter.java:60)
>> ~[pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
>> at
>> org.apache.pinot.core.segment.creator.impl.inv.OffHeapBitmapInvertedIndexCreator.seal(OffHeapBitmapInvertedIndexCreator.java:181)
>> ~[pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
>> at
>> org.apache.pinot.core.segment.index.loader.invertedindex.InvertedIndexHandler.createInvertedIndexForColumn(InvertedIndexHandler.java:122)
>> ~[pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
>> at
>> org.apache.pinot.core.segment.index.loader.invertedindex.InvertedIndexHandler.createInvertedIndices(InvertedIndexHandler.java:70)
>> ~[pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
>> at
>> org.apache.pinot.core.segment.index.loader.SegmentPreProcessor.process(SegmentPreProcessor.java:112)
>> ~[pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
>> at
>> org.apache.pinot.core.indexsegment.immutable.ImmutableSegmentLoader.load(ImmutableSegmentLoader.java:99)
>> ~[pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
>> at
>> org.apache.pinot.core.data.manager.offline.OfflineTableDataManager.addSegment(OfflineTableDataManager.java:52)
>> ~[pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
>> at
>> org.apache.pinot.server.starter.helix.HelixInstanceDataManager.addOfflineSegment(HelixInstanceDataManager.java:121)
>> ~[pinot-all-0.7.0-jar-with-dependencies.jar:0.7.0-157bd569303bbab60d79dbd36ba68089d1ee651f]
>> at
>> org.apache.pinot.server.starter.helix.SegmentFetcherAndLoader.addOrReplaceOfflineSegment(SegmentFetcherAndLoader.java:158)

[VOTE] Apache Pinot (incubating) 0.7.0 RC1

[Yupeng Fu]

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 RC1

[Yupeng Fu]

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-rc0>
>> 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-1023>
>> 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

[Yupeng Fu]

That's right.

Corrected:

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-rc0>
https://github.com/apache/incubator-pinot/tree/release-0.7.0-rc1

 Git hash for this release:  695ca390a8080409b3b76f250f2315b81b86b362

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


On Thu, Mar 11, 2021 at 12:34 PM Fu Xiang  wrote:

> I think the commit hash in the email should be :
> 695ca390a8080409b3b76f250f2315b81b86b362
> <https://github.com/apache/incubator-pinot/commit/695ca390a8080409b3b76f250f2315b81b86b362>
> (See step 6 here:
> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
> )
>
> Verified other parts.
> [Y] Verify if the bundle contains "incubating" in name
> [Y] Verify signature, hash
> [N]Verify if the released source matches with the provided git tag & hash
> [Y]Verify if DISCLAIMER, LICENSE, NOTICE files are present
> [Y]Check if the source distribution can compile (Do not skip the tests)
> [Y]Run quick demo from both source and binary distributions
>
> On Thu, Mar 11, 2021 at 9:36 AM kishore g  wrote:
>
>> +1
>>
>> On Thu, Mar 11, 2021 at 9:34 AM Mayank Shrivastava <
>> mayanks.apa...@gmail.com> wrote:
>>
>>> +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-rc0>
>>>>> https://github.com/apache/incubator-pinot/tree/release-0.7.0-rc1
>>>>>
>>>>&g

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

[Yupeng Fu]

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

Apach Pinot (incubating) 0.7.0 RC1 has passed with 4 +1 (binding) votes and
no 0 or -1 votes.

Binding
+1 Kishore Gopalakrishna
+1 Xiang Fu
+1 Mayank Shrivastava
+1 Siddharth Teotia

Best,

On Fri, Mar 12, 2021 at 4:34 PM siddharth teotia 
wrote:

> No. We can proceed.
>
> + 1
>
> On Fri, Mar 12, 2021, 3:32 PM kishore g  wrote:
>
>> Sidd, is this a blocker? can we fix this in the next version.
>>
>> On Thu, Mar 11, 2021 at 10:43 PM siddharth teotia <
>> siddharthteo...@gmail.com> wrote:
>>
>>> Should we remove dist and package-lock.json from the source distribution
>>> directory?
>>>
>>> The directory structure should be the same as this -
>>> https://github.com/apache/incubator-pinot/tree/release-0.7.0-rc/pinot-controller/src/main/resources
>>>
>>>
>>>
>>> On Thu, Mar 11, 2021 at 7:47 PM Xiang Fu  wrote:
>>>
>>>> +1
>>>>
>>>> On Mar 11, 2021, at 3:07 PM, Yupeng Fu  wrote:
>>>>
>>>> That's right.
>>>>
>>>> Corrected:
>>>>
>>>> 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-rc0>
>>>> https://github.com/apache/incubator-pinot/tree/release-0.7.0-rc1
>>>>
>>>>  Git hash for this release:  695ca390a8080409b3b76f250f2315b81b86b362
>>>>
>>>> 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-1023>
>>>> 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
>>>>
>>>>
>>>> On Thu, Mar 11, 2021 at 12:34 PM Fu Xiang  wrote:
>>>>
>>>>> I think the commit hash in the email should be :
>>>>> 695ca390a8080409b3b76f250f2315b81b86b362
>>>>> <https://github.com/apache/incubator-pinot/commit/695ca390a8080409b3b76f250f2315b81b86b362>
>>>>> (See step 6 here:
>>>>> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
>>>>> )
>>>>>
>>>>> Verified other parts.
>>>>> [Y] Verify if the bundle contains "incubating" in name
>>>>> [Y] Verify signature, hash
>>>>> [N]Verify if the released source matches with the provided git tag &
>>>>> hash
>>>>> [Y]Verify if DISCLAIMER, LICENSE, NOTICE files are present
>>>>> [Y]Check if the source distribution can compile (Do not skip the tests)
>>>>> [Y]Run quick demo from both source and binary distributions
>>>>>
>>>>> On Thu, Mar 11, 2021 at 9:36 AM kishore g  wrote:
>>>>>
>>>>>> +1
>>>>>>
>>>>>> On Thu, Mar 11, 2021 at 9:34 AM Mayank Shrivastava <
>>>>>> mayanks.apa...@gmail.com> wrote:
>>>>>>
>>>>>>> +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|

[RESULT][VOTE] Apache Pinot (incubating) 0.7.0 RC1

[Yupeng Fu]

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

Apach Pinot (incubating) 0.7.0 RC1 has passed with 4 +1 (binding) votes and
no 0 or -1 votes.

Binding
+1 Kishore Gopalakrishna
+1 Xiang Fu
+1 Mayank Shrivastava
+1 Siddharth Teotia

-- 
--Yupeng

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

[Yupeng Fu]

Yes, it was sent out to general@incubator, too. Please also vote on that
thread.

On Tue, Mar 16, 2021 at 3:17 PM kishore g  wrote:

> Thanks Yupeng. please note that we need to get approval from general@ as
> well.
>
>
> https://cwiki.apache.org/confluence/display/PINOT/Creating+an+Apache+Release
>
>
> On Tue, Mar 16, 2021 at 3:12 PM Yupeng Fu  wrote:
>
>> Thanks everyone for validating a release candidate. This vote is now
>> closed.
>>
>> Apach Pinot (incubating) 0.7.0 RC1 has passed with 4 +1 (binding) votes and
>> no 0 or -1 votes.
>>
>> Binding
>> +1 Kishore Gopalakrishna
>> +1 Xiang Fu
>> +1 Mayank Shrivastava
>> +1 Siddharth Teotia
>>
>> --
>> --Yupeng
>>
>

-- 
--Yupeng

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

[Yupeng Fu]

Felix/Kishore,

The git hash on the git tag is now the same as the one sent out in the
vote. Please check again
https://github.com/apache/incubator-pinot/commits/release-0.7.0

Sorry for the inconvenience and thanks for checking.

Best,

On Mon, Mar 22, 2021 at 9:03 AM kishore g  wrote:

> What’s the resolution here.
>
> Felix/Olivier any thoughts?
>
> -- Forwarded message -
> From: Felix Cheung 
> Date: Fri, Mar 19, 2021 at 3:45 PM
> Subject: Re: [VOTE] Apache Pinot (incubating) 0.7.0 RC1
> To: 
>
>
> For some reason the git hash has changed in release git tag
>
> https://github.com/apache/incubator-pinot/commits/release-0.7.0
>
>
> https://github.com/apache/incubator-pinot/commit/de0236c25727ffc2408c5bf55836bbfecf40499c
>
>
>
>
> On Fri, Mar 19, 2021 at 11:00 AM kishore g  wrote:
>
> > Jim/Felix and others
> >
> > Do we have your +1 to go ahead with the release.
> >
> > Thanks
> > Kishore G
> >
> > On Thu, Mar 18, 2021 at 9:32 PM kishore g  wrote:
> >
> > > That would be great. We will update the release runbook to make sure
> this
> > > doesn't happen again.
> > >
> > > Here is my +1
> > >
> > >
> > >
> > > On Thu, Mar 18, 2021 at 11:03 AM Jim Jagielski 
> wrote:
> > >
> > >> I propose that we run the vote anyway, thus ensuring IPMC oversight
> and
> > >> (post)approval, and then update the release runbook to make sure this
> > >> doesn't happen again. Make sense?
> > >>
> > >> > On Mar 17, 2021, at 11:35 PM, Felix Cheung 
> > >> wrote:
> > >> >
> > >> > It is unclear the guidance on this but since it is impossible remove
> > >> from
> > >> > maven
> > >> >
> > >> > https://repository.apache.org/#nexus-search;classname~Pinot
> > >> >
> > >> > Once it is published, I’d suggest we update all the links and git
> hash
> > >> and
> > >> > still proceed to vote on this. If there is any issue we should vote
> on
> > >> > another release with fix ASAP. Otherwise hopefully IPMC can continue
> > to
> > >> > sign off on this release.
> > >> >
> > >> >
> > >> >
> > >> > On Wed, Mar 17, 2021 at 3:09 PM kishore g 
> > wrote:
> > >> >
> > >> >> Apologies for the mistake. We have done multiple releases until now
> > and
> > >> >> this is the first time we missed the step to get the approval from
> > >> IPMC was
> > >> >> missed before making the release.
> > >> >>
> > >> >> What is the right thing to do at this point? Should we cut another
> > >> release
> > >> >> or can we go ahead with this and ensure that this does not happen
> > >> again.
> > >> >>
> > >> >> thanks,
> > >> >> Kishore G
> > >> >>
> > >> >> On Wed, Mar 17, 2021 at 10:59 AM Felix Cheung <
> > felixche...@apache.org>
> > >> >> wrote:
> > >> >>
> > >> >>> Unfortunately this isn’t the right process for a podling release.
> > >> >>>
> > >> >>> As the mentor, I am sorry to see the release is not up to the
> > standard
> > >> >>> upheld by previous releases.
> > >> >>>
> > >> >>>
> > >> >>> On Wed, Mar 17, 2021 at 7:02 AM kezhenxu94@apache <
> > >> kezhenx...@apache.org
> > >> >>>
> > >> >>> wrote:
> > >> >>>
> > >> >>>> I think this release violates the Apache release policy because
> it
> > >> >> didn’t
> > >> >>>> get the approvals from IPMC but was released actually (in both
> > >> dist.a.o
> > >> >>> and
> > >> >>>> GitHub).
> > >> >>>>
> > >> >>>> —
> > >> >>>> Zhenxu Ke (柯振旭)
> > >> >>>> GitHub @kezhenxu94
> > >> >>>>
> > >> >>>>> On Mar 17, 2021, at 06:14, Yupeng Fu 
> wrote:
> > >> >>>>>
> > >> >>>>> Hi all,
> > >> >>>>>
> > >> >>>>> This is a call for vote to the rele

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

[Yupeng Fu]

Replied.

Thanks,

On Mon, Mar 22, 2021 at 9:15 AM kishore g  wrote:

> Yupeng, can you respond to the thread on the general thread?
>
>
>
> On Mon, Mar 22, 2021 at 9:11 AM Yupeng Fu  wrote:
>
>> Felix/Kishore,
>>
>> The git hash on the git tag is now the same as the one sent out in the
>> vote. Please check again
>> https://github.com/apache/incubator-pinot/commits/release-0.7.0
>>
>> Sorry for the inconvenience and thanks for checking.
>>
>> Best,
>>
>> On Mon, Mar 22, 2021 at 9:03 AM kishore g  wrote:
>>
>>> What’s the resolution here.
>>>
>>> Felix/Olivier any thoughts?
>>>
>>> -- Forwarded message -
>>> From: Felix Cheung 
>>> Date: Fri, Mar 19, 2021 at 3:45 PM
>>> Subject: Re: [VOTE] Apache Pinot (incubating) 0.7.0 RC1
>>> To: 
>>>
>>>
>>> For some reason the git hash has changed in release git tag
>>>
>>> https://github.com/apache/incubator-pinot/commits/release-0.7.0
>>>
>>>
>>> https://github.com/apache/incubator-pinot/commit/de0236c25727ffc2408c5bf55836bbfecf40499c
>>>
>>>
>>>
>>>
>>> On Fri, Mar 19, 2021 at 11:00 AM kishore g  wrote:
>>>
>>> > Jim/Felix and others
>>> >
>>> > Do we have your +1 to go ahead with the release.
>>> >
>>> > Thanks
>>> > Kishore G
>>> >
>>> > On Thu, Mar 18, 2021 at 9:32 PM kishore g  wrote:
>>> >
>>> > > That would be great. We will update the release runbook to make sure
>>> this
>>> > > doesn't happen again.
>>> > >
>>> > > Here is my +1
>>> > >
>>> > >
>>> > >
>>> > > On Thu, Mar 18, 2021 at 11:03 AM Jim Jagielski 
>>> wrote:
>>> > >
>>> > >> I propose that we run the vote anyway, thus ensuring IPMC oversight
>>> and
>>> > >> (post)approval, and then update the release runbook to make sure
>>> this
>>> > >> doesn't happen again. Make sense?
>>> > >>
>>> > >> > On Mar 17, 2021, at 11:35 PM, Felix Cheung <
>>> felixche...@apache.org>
>>> > >> wrote:
>>> > >> >
>>> > >> > It is unclear the guidance on this but since it is impossible
>>> remove
>>> > >> from
>>> > >> > maven
>>> > >> >
>>> > >> > https://repository.apache.org/#nexus-search;classname~Pinot
>>> > >> >
>>> > >> > Once it is published, I’d suggest we update all the links and git
>>> hash
>>> > >> and
>>> > >> > still proceed to vote on this. If there is any issue we should
>>> vote on
>>> > >> > another release with fix ASAP. Otherwise hopefully IPMC can
>>> continue
>>> > to
>>> > >> > sign off on this release.
>>> > >> >
>>> > >> >
>>> > >> >
>>> > >> > On Wed, Mar 17, 2021 at 3:09 PM kishore g 
>>> > wrote:
>>> > >> >
>>> > >> >> Apologies for the mistake. We have done multiple releases until
>>> now
>>> > and
>>> > >> >> this is the first time we missed the step to get the approval
>>> from
>>> > >> IPMC was
>>> > >> >> missed before making the release.
>>> > >> >>
>>> > >> >> What is the right thing to do at this point? Should we cut
>>> another
>>> > >> release
>>> > >> >> or can we go ahead with this and ensure that this does not happen
>>> > >> again.
>>> > >> >>
>>> > >> >> thanks,
>>> > >> >> Kishore G
>>> > >> >>
>>> > >> >> On Wed, Mar 17, 2021 at 10:59 AM Felix Cheung <
>>> > felixche...@apache.org>
>>> > >> >> wrote:
>>> > >> >>
>>> > >> >>> Unfortunately this isn’t the right process for a podling
>>> release.
>>> > >> >>>
>>> > >> >>> As the mentor, I am sorry to see the release is not up to the
>>> > standard
>>> >

Re: DISCUSS Pinot Graduation

[Yupeng Fu]

+1 on graduation readiness. Apache Pinot has a lot of accomplishments in
the past years on project maturity. It has a strong community and good
adoption in the industry.

Best,

On Sun, May 9, 2021 at 8:54 AM Mayank Shrivastava 
wrote:

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

-- 
--Yupeng

Re: [VOTE] Apache Pinot graduation to a TLP

[Yupeng Fu]

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

-- 
--Yupeng

Re: Request for Gitbook edit permission

[Yupeng Fu]

Hi,

You can submit a PR to https://github.com/pinot-contrib/pinot-docs

On Wed, Jun 30, 2021 at 3:41 PM Amrish Lal  wrote:

> Hello,
>
> I would like to update documentation related to recent JSON query
> modifications (https://docs.pinot.apache.org/users/user-guide-query) and
> also add a JSON query tutorial (
> https://docs.pinot.apache.org/users/tutorials). Can I please get the edit
> permission for Pinot documentation on Gitbook?
>
> Thanks,
> --Amrish
> https://github.com/amrishlal
>
>

-- 
--Yupeng

Re: [VOTE] Apache Pinot 0.8.0 RC0

[Yupeng Fu]

Not sure if it's just me.  I got maven compilation failure with

[WARNING] Error injecting:
org.apache.maven.artifact.installer.DefaultArtifactInstaller
com.google.inject.ProvisionException: Unable to provision, see the
following errors:

1) Error injecting: private org.eclipse.aether.spi.log.Logger
org.apache.maven.repository.internal.DefaultVersionRangeResolver.logger
  while locating
org.apache.maven.repository.internal.DefaultVersionRangeResolver
  while locating java.lang.Object annotated with *
  at org.eclipse.sisu.wire.LocatorWiring
  while locating org.eclipse.aether.impl.VersionRangeResolver
for parameter 2 at
org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.(Unknown
Source)
  while locating
org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector
  while locating java.lang.Object annotated with *
  at org.eclipse.sisu.wire.LocatorWiring
  while locating org.eclipse.aether.impl.DependencyCollector
for parameter 5 at
org.eclipse.aether.internal.impl.DefaultRepositorySystem.(Unknown
Source)
  while locating org.eclipse.aether.internal.impl.DefaultRepositorySystem
  while locating java.lang.Object annotated with *
  while locating
org.apache.maven.artifact.installer.DefaultArtifactInstaller
Caused by: java.lang.IllegalArgumentException: Can not set
org.eclipse.aether.spi.log.Logger field
org.apache.maven.repository.internal.DefaultVersionRangeResolver.logger to
org.eclipse.aether.internal.impl.slf4j.Slf4jLoggerFactory
at
java.base/jdk.internal.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldA
...

[ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
[ERROR] at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[ERROR] at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[ERROR] at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ERROR] at java.base/java.lang.reflect.Method.invoke(Method.java:566)
[ERROR] at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
[ERROR] at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
[ERROR] at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
[ERROR] at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
[ERROR]
[ERROR] 4 errors
[ERROR] role: org.apache.maven.plugin.Mojo
[ERROR] roleHint:
org.apache.maven.plugins:maven-install-plugin:2.5.2:install
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]

On Thu, Aug 12, 2021 at 2:49 PM Xiaotian Jiang  wrote:

> +1
>
> Jackie
>
> On Wed, Aug 11, 2021 at 4:03 PM Seunghyun Lee  wrote:
>
>> Hi Pinot Community,
>>
>> This is a call for a vote to release Apache Pinot 0.8.0.
>>
>> The release candidate:
>> https://dist.apache.org/repos/dist/dev/pinot/apache-pinot-0.8.0-rc0
>>
>> Git tag for this release:
>> https://github.com/apache/pinot/tree/release-0.8.0-rc0
>>
>> Git hash for this release:
>> c4ceff06d21fc1c1b88469a8dbae742a4b609808
>>
>> The artifacts have been signed with key: 7199AF89, which can be found in
>> the following KEYS file.
>> https://dist.apache.org/repos/dist/release/pinot/KEYS
>>
>> Release notes:
>> https://github.com/apache/pinot/releases/tag/release-0.8.0-rc0
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachepinot-1030
>>
>> Documentation on verifying a release candidate:
>>
>> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
>>
>> The vote will be open for at least 72 hours or until a necessary number
>> of votes is reached.
>>
>> Please vote accordingly,
>>
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove with the reason
>>
>> Thanks,
>> Apache Pinot team
>>
>

-- 
--Yupeng

Re: [VOTE] Apache Pinot 0.8.0 RC0

[Yupeng Fu]

Also, in the release note, could you include the partial upsert support?
It's an important feature added to upsert.

Thanks,

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

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


-- 
--Yupeng

Re: [VOTE] Apache Pinot 0.8.0 RC0

[Yupeng Fu]

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

Re: [VOTE] Apache Pinot 0.8.0 RC0

[Yupeng Fu]

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

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

[Yupeng Fu]

+1



On Tue, Sep 14, 2021 at 9:50 AM Rong Rong  wrote:

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


-- 
--Yupeng

Re: [VOTE] Apache Pinot 0.9.1 RC0

[Yupeng Fu]

+1

On Mon, Dec 13, 2021 at 11:23 AM Xiaotian Jiang 
wrote:

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

-- 
--Yupeng

Re: Apache Pinot geospatial support

[Yupeng Fu]

Thanks for letting me know.

Hi, Julian, sure, I can join the group on behalf of the Pinot dev.

Best,

On Mon, Feb 7, 2022 at 6:10 PM kishore g  wrote:

> Thanks Julian for forwarding this to me. Adding Pinot dev and Yupeng from
> Uber who might be interested in joining the group
>
> On Mon, Feb 7, 2022 at 4:59 PM Julian Hyde  wrote:
>
>> Kishore,
>>
>> Apache’s Geospatial group has noticed Pinot’s geospatial support and
>> wonders whether someone would like to join the group.
>>
>> Geospatial isn’t a project, just a mailing list really, but it helps
>> coordinate efforts between projects and showcase their efforts in the
>> Geospatial track at ApacheCon.
>>
>> Can you float this on the dev list and get one or two people to
>> subscribe? Low volume, I’m sure it would be worth their time.
>>
>> Julian
>>
>>
>> Begin forwarded message:
>>
>> *From: *George Percivall 
>> *Subject: **Apache Pinot geospatial support*
>> *Date: *February 3, 2022 at 6:34:39 AM PST
>> *To: *"geospat...@apache.org" 
>> *Reply-To: *geospat...@apache.org
>>
>> Has anyone here used Apache Pinot?
>> https://docs.pinot.apache.org/basics/indexing/geospatial-support <
>> https://docs.pinot.apache.org/basics/indexing/geospatial-support>
>>
>> Does anyone know a Pinot committer?  Please let them know about this list.
>> https://github.com/apache/pinot/graphs/contributors <
>> https://github.com/apache/pinot/graphs/contributors>
>>
>>
>> George Percivall
>> GeoRoundtable 
>> perciv...@apache.org 
>>
>>
>>
>>

-- 
--Yupeng

Re: Apache Pinot™ Slack Workspace Rename

[Yupeng Fu]

+1 to a separate slack workspace for StarTree related channels.

On Wed, May 25, 2022 at 4:04 PM Tim Berglund  wrote:

> These are great things! My team and I at Confluent worked hard to help new
> hires come up to speed with a list like this and to keep events like Kafka
> Summit and our meetups operating with integrity. Not everybody gets it
> right away, but we always got them on board with sufficient help. I've seen
> it done badly in past gigs, so I'm eager to keep things healthy and
> well-differentiated going forward. :)
>
> On Wed, May 25, 2022 at 4:04 PM Owen O'Malley 
> wrote:
>
>> You cut the video link, but it was relevant.
>>
>> At Hortonworks, we found it worthwhile to train the engineers, marketing,
>> & events teams on:
>> * Apache structure and roles
>> * The Apache Way
>> * Apache License
>> * Why Hortonworks chooses to work with Apache
>> * Being both a Hortonworker and a part of Apache
>> * Practical tips: what works & mistakes not to repeat
>> * Trademarks
>>
>> .. Owen
>>
>>
>>
>> On Wed, May 25, 2022 at 9:51 PM Tim Berglund 
>> wrote:
>>
>>>
>>> > I'd also suggest that Startree work on training their marketing and
>>> sales team on working with Apache projects.
>>>
>>> May I ask you to be more specific here? I've been doing some internal
>>> training in the past two months to help with problems like the one I'm
>>> rectifying here. Maintaining proper boundaries and ASF branding guidelines
>>> is important.
>>>
>>>
>>> On Wed, May 25, 2022 at 3:48 PM Owen O'Malley 
>>> wrote:
>>>
 As an Apache member observer, unless the project wants to abandon
 Slack, it seems to me that Startree should make a new Slack workspace
 rather than taking the Apache Pinot one.

 I'd also suggest that Startree work on training their marketing and
 sales team on working with Apache projects. Take a look at Alan Gate's
 presentation on 'Training Our Teams on the Apache Way.'
 https://youtu.be/uFNE0IpKOxU

 .. Owen

 On Wed, May 25, 2022 at 9:17 PM Seunghyun Lee  wrote:

> I also definitely agree that Startree has put a tremendous effort to
> grow the ASF Pinot community slack channel and helping people for
> troubleshooting/debug the issue.
>
> On the other hand, the community slack channel was created as part of
> the Apache incubation process and this workspace has always been regarded
> as one of the community growth metrics for ASF Pinot.
>
> As Sidd mentioned, a lot of ASF Pinot-related discussions are
> happening in the slack channel (e.g. contributor/committer/pmc 
> discussions,
> cross org collaboration on the features etc). From what Tim is
> highlighting, I think that maybe it is better to keep a separate 
> workspace:
> one for Startree customers and the other for only ASF Pinot users and
> contributors.
>
> Best,
> Seunghyun
>
>
>
>
> On Wed, May 25, 2022 at 2:00 PM siddharth teotia <
> siddharthteo...@gmail.com> wrote:
>
>> Hi Tim,
>>
>> Thank you for sharing this.
>>
>> > StarTree is committed to making Pinot famous—that’s my actual job,
>> in fact—and to helping users of the open-source project be successful 
>> with
>> it, but we need to keep the boundaries between the ASF and StarTree 
>> clearly
>> defined. Renaming this Slack is an important part of that distinction
>>
>> I understand where you are coming from and why you may want to keep
>> distinction between ASF Pinot and Startree. However, I am not quite sure
>> how renaming this is going to help with distinction because then all the
>> ASF Pinot related conversations (between contributors / committers / PMCs
>> for release, PR, issue etc discussion) will have to go through Startree
>> workspace which may not be the correct place to do so because these
>> discussions are orthogonal to Startree or any company using / 
>> contributing
>> to ASF Pinot.
>>
>> This workspace was initially created to help grow the ASF Pinot
>> community and have the related discussions there. I completely agree that
>> Startree has done a great job in bringing more folks to the workspace,
>> helping them on a day to day basis etc. However, renaming will actually
>> blur the distinction to be honest.
>>
>> Shall we discuss this to see if there is any alternative to achieve
>> this distinction ?
>>
>> Thanks
>> Sidd
>>
>>
>>
>>
>>
>> On Wed, May 25, 2022 at 11:56 AM Tim Berglund 
>> wrote:
>>
>>> Pinot Dev,
>>>
>>> I’m Tim Berglund. The barest intro of me: I run Developer Relations
>>> at StarTree. I wanted to go over a change I’m making to our Slack 
>>> workspace
>>> so it is not a surprise to you and we have a chance to talk through any
>>> questions.
>>>
>>> On June 1, 2022, we will rename the Apache Pinot™ Sl

Re: [VOTE] Apache Pinot 1.1.0 RC1

[Yupeng Fu]

+1 (binding)

On Tue, Mar 19, 2024 at 11:04 PM siddharth teotia 
wrote:

> +1 (binding)
>
> -Sidd
>
> On Sat, Mar 16, 2024 at 10:39 PM Fu Xiang  wrote:
>
>> +1 (binding)
>>
>> Xiang Fu
>>
>>
>> On Sun, Mar 17, 2024 at 06:24 Mayank Shrivastava <
>> mayanks.apa...@gmail.com> wrote:
>>
>>> +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/
>>> >> <
>>> https://repository.apache.org/content/repositories/orgapachepinot-1060/>
>>> >> 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
>>>
>>>

-- 
--Yupeng