Re: Apache Pinot geospatial support

[kishore g]

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

Re: [VOTE] Apache Pinot 0.9.3 RC0

[kishore g]

+1

On Fri, Dec 24, 2021 at 7:00 AM Mayank Shrivastava 
wrote:

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

[kishore g]

+1 thanks Xiang for getting this release out

On Tue, Dec 14, 2021 at 10:04 PM Mayank Shrivastava 
wrote:

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

[kishore g]

+1

On Sun, Dec 12, 2021 at 8:16 PM Seunghyun Lee  wrote:

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

Re: [VOTE] Apache Pinot 0.9.0 RC0

[kishore g]

+ 1

On Tue, Nov 16, 2021 at 12:44 PM Mayank Shrivastava 
wrote:

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

Re: [VOTE] Apache Pinot 0.8.0 RC0

[kishore g]

+1 binding

On Mon, Aug 16, 2021 at 11:19 AM Jialiang Li  wrote:

> +1
>
> I'm using maven 3.8.1 and validated both jdk8 and jdk11.
>
> On 2021/08/13 23:44:04, Mayank Shrivastava  wrote:
> > +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 <
> jackie@gmail.com>
> > > wrote:
> > >
> > >> +1
> > >>
> > >> Jackie
> > >>
> > >

Re: [VOTE] Graduate Apache Pinot as TLP

[kishore g]

+1

On Wed, Jun 23, 2021 at 3:10 PM Xiaotian Jiang  wrote:

> +1
>
> Jackie
>
> On Tue, Jun 22, 2021 at 12:44 PM Mayank Shrivastava 
> wrote:
>
>> 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
>>
>> RES

Re: [VOTE] Apache Pinot graduation to a TLP

[kishore g]

+1

On Mon, Jun 7, 2021 at 4:56 AM Jim Jagielski  wrote:

> +1
>
> On Jun 4, 2021, at 12:55 PM, 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.
>
>
>

Re: Review request for Apache Maturity Model Assessment for Pinot

[kishore g]

Thanks Seunghyun for putting this together.

On Mon, May 17, 2021 at 9:01 PM Felix Cheung 
wrote:

> Great!
>
> --
> *From:* Seunghyun Lee 
> *Sent:* Monday, May 17, 2021 5:08:42 PM
> *To:* dev@pinot.apache.org 
> *Subject:* Review request for Apache Maturity Model Assessment for Pinot
>
> Hi all,
>
> I have finished the initial draft of Apache Maturity Model Assessment
> document for Pinot. This document will be evaluated as part of our
> graduation process.
>
>
> https://cwiki.apache.org/confluence/display/PINOT/Apache+Maturity+Model+Assessment+for+Pinot
>
> It would be great if we can get some reviews from the community.
>
> Best,
> Seunghyun
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
> For additional commands, e-mail: dev-h...@pinot.apache.org
>
>

Re: DISCUSS Pinot Graduation

[kishore g]

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
>>>> >-
>>>> >
>>>> >Updated Apache Pinot (incubating) page
>>>> ><https://incubator.apache.org/projects/pinot.html>
>>>> >-
>>>> >
>>>> >Updated Roster Page <https://whimsy.apache.org/roster/ppmc/pinot>
>>>> >-
>>>> >
>>>> >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
>>>> ><https://communityinviter.com/apps/apache-pinot/apache-pinot>. 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: About cutting the 0.8.0 release (graduation release)

[kishore g]

Thanks Seunghyun for starting this thread.

There is no special requirement to have a graduation release. Graduation is
a separate process from release. It’s just that release process changes
slightly after the graduation.

Do you want to do this release before or after graduation?

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

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

DISCUSS Pinot Graduation

[kishore g]

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
   <https://incubator.apache.org/projects/pinot.html>
   -

   Updated Roster Page <https://whimsy.apache.org/roster/ppmc/pinot>
   -

   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
   <https://communityinviter.com/apps/apache-pinot/apache-pinot>. 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

[kishore g]

+1

On Thu, Apr 8, 2021 at 3:14 PM Mayank Shrivastava 
wrote:

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

[kishore g]

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

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

[kishore g]

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 release Apache Pinot (incubating)
> >> >>> version
> >> >>>>> 0.7.0.
> >> >>>>>
> >> >>>>> Apache Pinot (incubating) is a distributed columnar storage
engine
> >> >> that
> >> >>>> can
> >> >>>>> ingest data in realtime and serve analytical queries at low
> latency.
> >> >>>>>
> >> >>>>> Pinot community has voted and approved this release.
> >> >>>>>
> >> >>>>> Vote thread:
> >> >>>>>
> >> >>>>
> >> >>>
> >> >>
> >>
>
https://lists.apache.org/thread.html/r850cee1e6fc23804d161a31d465e30d5d12b7a4e1cc8035264ea91d6%40%3Cdev.pinot.apache.org%3E
> >

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

[kishore g]

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
>

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

[kishore g]

Sidd, is this a blocker? can we fix this in the next version.

On Thu, Mar 11, 2021 at 10:43 PM siddharth teotia 
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|: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-pi

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

[kishore g]

+1

On Thu, Mar 11, 2021 at 9:34 AM Mayank Shrivastava 
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-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 RC0

[kishore g]

+1



On Fri, Mar 5, 2021 at 11:09 AM Mayank Shrivastava 
wrote:

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

[kishore g]

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: Mentor for Pinot

[kishore g]

Hi Owen, Thanks for the offer. We are in good hands with Oliver who has
helped me with Helix. We will let you know if we need additional help in
the future

Thanks,
Kishore G

On Fri, Feb 12, 2021 at 4:51 PM Owen O'Malley 
wrote:

> Now that Gobblin has graduated from Apache Incubator, I would like to
> volunteer as a mentor for Pinot, if the project thinks that would help. I
> have gone through the process several times of helping projects graduate
> from Incubator. *smile*
>
> Let me know your thoughts,
>Owen
>

Re: Podling Pinot Report Reminder - February 2021

[kishore g]

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.5.0 RC2

[kishore g]

+1

On Thu, Sep 3, 2020 at 1:14 PM Kartik Khare  wrote:

> +1
>
> On 2020/09/03 04:47:41, 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-rc2
> >
> > Diff with apache-pinot-incubating-0.5.0-rc1
> > https://github.com/apache/incubator-pinot/commit/d902c1a (Remove the
> > node_modules codes from the src package)
> >
> > Git tag for this release:
> > https://github.com/apache/incubator-pinot/tree/release-0.5.0-rc2
> >
> > Git hash for this release:
> > d87bbc9032c6efe626eb5f9ef1db4de7aa067179
> >
> > 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-rc2
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachepinot-1016
> >
> > 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
> > related to 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:
> > 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
> >
>
> -
> 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

[kishore g]

+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: Moving request optimizer and parser factory from pinot-broker to pinot-core

[kishore g]

It's ok to move the request optimizer to core. We have to clean up the core
and common anyway and we can handle it when we get there

On Mon, Aug 3, 2020 at 2:17 PM Jia Guo  wrote:

> Hi Pinot Devs,
>
>
>
> This is Jia from Pinot team @ LinkedIn. Currently @Siddharth
> Teotia , @Dino Occhialini ,
> and I are integrating a config recommendation engine within LI. For
> cleaner interface and better user experience, it is good to have a rest
> endpoint on controller; and therefore the engine should also resides in
> controller. To achieve this, we are proposing to move its dependencies,
> request optimizer and parser factory, from broker to core. We have explored
> other options as -- (1) moving engine to broker, but logically having this
> API on broker does not make sense and will be hard to invoke, (2) moving
> dependencies to common, will require more dependencies (e.g. part of query
> context) to be moved from core to common to avoid cycle, which is not
> clean; and so finally moving optimizer to core is a viable solution.
>
> Please feel free to give us feedback! Thanks!
>
>
>
>
>
>
>

Apache Pinot 0.5.0 release

[kishore g]

We have added a lot of new features since 0.4.0 and it’s time to cut 0.5.0
release.

Any volunteers?

Re: [Vote] Enabling html for Pinot related mailing lists

[kishore g]

+1

On Sat, Jun 13, 2020 at 8:09 PM H  wrote:

> +1
>
> On Sat, Jun 13, 2020 at 8:04 PM Mayank Shrivastava <
> mayanks.apa...@gmail.com>
> wrote:
>
> > +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: new Metadata format for download url in LLCRealtimeSegmentZKMetadata

[kishore g]

cause performance impact on the server. So we should only use peer
> > > download if there is no other option, i.e. as a backup.
> > > If we model peer download as a backup plan, we should not overload the
> > > existing downloadUri to trigger it. Instead, we should try to download
> > > with the downloadUri first, and only if it fails (including the case
> > > where downloadUri does not exist), we try to download from peer.
> > >
> > > On Thu, Jun 11, 2020 at 3:26 PM TING CHEN 
> > > wrote:
> > > >
> > > > Our current design
> > > > <
> > >
> https://cwiki.apache.org/confluence/display/PINOT/By-passing+deep-store+requirement+for+Realtime+segment+completion
> > > >
> > > > does not add a new pinotFS for *peer://*. This is a very interesting
> > > > question though. The only operations our design uses today for peer
> "FS"
> > > is
> > > > essentially *copyToLocal()* in the pinotFS interface. Our design
> > > basically
> > > > has a class and a few supporting methods
> > > > <
> > >
> https://cwiki.apache.org/confluence/display/PINOT/By-passing+deep-store+requirement+for+Realtime+segment+completion#BypassingdeepstorerequirementforRealtimesegmentcompletion-EnablebesteffortsegmentuploadinSplitSegmentCommiteranddownloadsegmentfrompeerservers
> > > .>
> > > > implementing the above method. That is why we do not add a
> full-fledged
> > > > pinotFS subclass for this design.
> > > >
> > > >
> > > > On Thu, Jun 11, 2020 at 3:00 PM kishore g 
> wrote:
> > > >
> > > > > Also, will peer:// have an implementation of pinotFS ?
> > > > >
> > > > > On Thu, Jun 11, 2020 at 2:58 PM kishore g 
> wrote:
> > > > >
> > > > > > +1 peer.
> > > > > >
> > > > > > unrelated to this - do we support multiple URI's?
> > > > > >
> > > > > > On Thu, Jun 11, 2020 at 2:51 PM Subbu Subramaniam <
> > > mcvsu...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > >> Hey Ting,
> > > > > >>
> > > > > >> I like the URI in metadata as "peer:///segmentName". This way,
> the
> > > URI
> > > > > >> remains parsable and we can use the scheme to check for a
> segment
> > > > > fetcher,
> > > > > >>
> > > > > >> thanks
> > > > > >>
> > > > > >> -Subbu
> > > > > >>
> > > > > >> On 2020/06/10 01:09:25, TING CHEN 
> > > wrote:
> > > > > >> > As part of the deep store by-passing
> > > > > >> > <
> > > > > >>
> > > > >
> > >
> https://cwiki.apache.org/confluence/display/PINOT/By-passing+deep-store+requirement+for+Realtime+segment+completion
> > > > > >> >
> > > > > >> > project, a server is allowed to download segments from peer
> Pinot
> > > > > >> servers
> > > > > >> > during Low Level Consumer (LLC) instead of deep segment
> stores. To
> > > > > >> enable
> > > > > >> > this feature, we plan to add a new URI format for the field
> > > > > >> > *segment.realtime.download.url
> > > > > >> > *in LLCRealtimeSegmentZKMetadata.
> > > > > >> >
> > > > > >> > The new URI format serves the purpose of instructing a Pinot
> > > server to
> > > > > >> find
> > > > > >> > and download the segment from a peer server. Controller
> writes it
> > > to
> > > > > >> Helix
> > > > > >> > in case of segment upload failure or no deep store configured
> at
> > > all.
> > > > > We
> > > > > >> > proposed the following format options and want to hear your
> > > feedback:
> > > > > >> >
> > > > > >> >1. peer:///segmentName; (my preference)
> > > > > >> >2. simply an empty string *''*
> > > > > >> >
> > > > > >> > Both are in essence specially markers to indicate that the
> > > segment is
> > > > > >> not
> > > > > >> > found in deep store and servers have to download them from
> peer
> > > > > servers.
> > > > > >> > (1) has the benefit of better readability than (2) for
> debugging
> > > > > >> purposes.
> > > > > >> >
> > > > > >> > Please let me know what you think.
> > > > > >> >
> > > > > >> > Ting Chen
> > > > > >> >
> > > > > >>
> > > > > >>
> > > -
> > > > > >> 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: new Metadata format for download url in LLCRealtimeSegmentZKMetadata

[kishore g]

Also, will peer:// have an implementation of pinotFS ?

On Thu, Jun 11, 2020 at 2:58 PM kishore g  wrote:

> +1 peer.
>
> unrelated to this - do we support multiple URI's?
>
> On Thu, Jun 11, 2020 at 2:51 PM Subbu Subramaniam 
> wrote:
>
>> Hey Ting,
>>
>> I like the URI in metadata as "peer:///segmentName". This way, the URI
>> remains parsable and we can use the scheme to check for a segment fetcher,
>>
>> thanks
>>
>> -Subbu
>>
>> On 2020/06/10 01:09:25, TING CHEN  wrote:
>> > As part of the deep store by-passing
>> > <
>> https://cwiki.apache.org/confluence/display/PINOT/By-passing+deep-store+requirement+for+Realtime+segment+completion
>> >
>> > project, a server is allowed to download segments from peer Pinot
>> servers
>> > during Low Level Consumer (LLC) instead of deep segment stores. To
>> enable
>> > this feature, we plan to add a new URI format for the field
>> > *segment.realtime.download.url
>> > *in LLCRealtimeSegmentZKMetadata.
>> >
>> > The new URI format serves the purpose of instructing a Pinot server to
>> find
>> > and download the segment from a peer server. Controller writes it to
>> Helix
>> > in case of segment upload failure or no deep store configured at all. We
>> > proposed the following format options and want to hear your feedback:
>> >
>> >1. peer:///segmentName; (my preference)
>> >2. simply an empty string *''*
>> >
>> > Both are in essence specially markers to indicate that the segment is
>> not
>> > found in deep store and servers have to download them from peer servers.
>> > (1) has the benefit of better readability than (2) for debugging
>> purposes.
>> >
>> > Please let me know what you think.
>> >
>> > Ting Chen
>> >
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
>> For additional commands, e-mail: dev-h...@pinot.apache.org
>>
>>

Re: new Metadata format for download url in LLCRealtimeSegmentZKMetadata

[kishore g]

+1 peer.

unrelated to this - do we support multiple URI's?

On Thu, Jun 11, 2020 at 2:51 PM Subbu Subramaniam 
wrote:

> Hey Ting,
>
> I like the URI in metadata as "peer:///segmentName". This way, the URI
> remains parsable and we can use the scheme to check for a segment fetcher,
>
> thanks
>
> -Subbu
>
> On 2020/06/10 01:09:25, TING CHEN  wrote:
> > As part of the deep store by-passing
> > <
> https://cwiki.apache.org/confluence/display/PINOT/By-passing+deep-store+requirement+for+Realtime+segment+completion
> >
> > project, a server is allowed to download segments from peer Pinot servers
> > during Low Level Consumer (LLC) instead of deep segment stores. To enable
> > this feature, we plan to add a new URI format for the field
> > *segment.realtime.download.url
> > *in LLCRealtimeSegmentZKMetadata.
> >
> > The new URI format serves the purpose of instructing a Pinot server to
> find
> > and download the segment from a peer server. Controller writes it to
> Helix
> > in case of segment upload failure or no deep store configured at all. We
> > proposed the following format options and want to hear your feedback:
> >
> >1. peer:///segmentName; (my preference)
> >2. simply an empty string *''*
> >
> > Both are in essence specially markers to indicate that the segment is not
> > found in deep store and servers have to download them from peer servers.
> > (1) has the benefit of better readability than (2) for debugging
> purposes.
> >
> > Please let me know what you think.
> >
> > Ting Chen
> >
>
> -
> 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

[kishore g]

+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://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.4.0-rc2
> >>
> >> Git tag for this release:
> >> https://github.com/apache/incubator-pinot/tree/release-0.4.0-rc2
> >>
> >> Git hash for this release:
> >> 8355d2e0e489a8d127f2e32793671fba505628a8
> >>
> >> The artifacts have been signed with key: 6CC169A6FC19C470, which can be
> >> found in the following KEYS file.
> >> https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS
> >>
> >> Release notes:
> >> GitHub:
> >>
> https://github.com/apache/incubator-pinot/releases/tag/release-0.4.0-rc2
> >>
> >> Staging repository:
> >> https://repository.apache.org/content/repositories/orgapachepinot-1013
> >>
> >> Documentation on verifying a release candidate:
> >>
> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
> >>
> >>
> >> The vote will be open for at least 72 hours or until necessary number of
> >> votes are reached.
> >>
> >> Please vote accordingly,
> >>
> >> [ ] +1 approve
> >> [ ] +0 no opinion
> >> [ ] -1 disapprove with the reason
> >>
> >> Thanks,
> >> Apache Pinot (incubating) team
> >>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
> > For additional commands, e-mail: dev-h...@pinot.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
> For additional commands, e-mail: dev-h...@pinot.apache.org
>
>

Re: [incubator-pinot] branch release-0.4.0-rc1 updated: WIP

[kishore g]

is it possible to use a env variable to trigger this?

On Tue, May 26, 2020 at 10:32 AM Xiaotian Jiang 
wrote:

> In order to turn the sampling off, please comment out line 300-303 and
> line 337-341 in BaseClusterIntegrationTestSet
>
> On Mon, May 25, 2020 at 4:26 PM kishore g  wrote:
> >
> > Can we make sure we run the integration test with sampling turned off
> for this release
> >
> > On Mon, May 25, 2020 at 4:24 PM  wrote:
> >>
> >> This is an automated email from the ASF dual-hosted git repository.
> >>
> >> haibow pushed a commit to branch release-0.4.0-rc1
> >> in repository https://gitbox.apache.org/repos/asf/incubator-pinot.git
> >>
> >>
> >> The following commit(s) were added to refs/heads/release-0.4.0-rc1 by
> this push:
> >>  new 88f41ea  WIP
> >> 88f41ea is described below
> >>
> >> commit 88f41ea971258a11b437d75e248fc84140cb150f
> >> Author: haibow 
> >> AuthorDate: Mon May 25 16:23:33 2020 -0700
> >>
> >> WIP
> >> ---
> >>  LICENSE-binary  | 154
> 
> >>  NOTICE-binary   |  52 +++-
> >>  licenses-binary/LICENSE-gpl-2.0.txt | 125 +
> >>  3 files changed, 280 insertions(+), 51 deletions(-)
> >>
> >> diff --git a/LICENSE-binary b/LICENSE-binary
> >> index 5c0e3e4..b537893 100644
> >> --- a/LICENSE-binary
> >> +++ b/LICENSE-binary
> >> @@ -211,28 +211,32 @@ com.clearspring.analytics:stream:2.7.0
> >>  com.fasterxml.jackson.core:jackson-annotations:2.9.8
> >>  com.fasterxml.jackson.core:jackson-core:2.9.8
> >>  com.fasterxml.jackson.core:jackson-databind:2.9.8
> >> +com.fasterxml.jackson.dataformat:jackson-dataformat-xml:2.9.8
> >>  com.fasterxml.jackson.dataformat:jackson-dataformat-yaml:2.9.8
> >> +com.fasterxml.jackson.datatype:jackson-datatype-jsr310:2.10.0
> >>  com.fasterxml.jackson.jaxrs:jackson-jaxrs-base:2.9.8
> >>  com.fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider:2.9.8
> >>  com.fasterxml.jackson.module:jackson-module-jaxb-annotations:2.9.8
> >>  com.fasterxml.jackson.module:jackson-module-paranamer:2.6.5
> >>  com.fasterxml.jackson.module:jackson-module-scala_2.11:2.6.5
> >> +com.fasterxml.woodstox:woodstox-core:5.0.3
> >>  com.github.jnr:jffi:1.2.9
> >>  com.github.jnr:jnr-constants:0.8.7
> >>  com.github.jnr:jnr-ffi:2.0.3
> >> +com.google.api-client:google-api-client
> >>  com.google.api.grpc:proto-google-common-protos:1.17.0
> >>  com.google.api.grpc:proto-google-iam-v1:0.13.0
> >>  com.google.api:api-common:1.8.1
> >>  com.google.api:gax:1.49.1
> >>  com.google.api:gax-httpjson:0.66.1
> >> -com.google.api:google-api-client:1.30.4
> >> -com.google.api:google-api-services-storage:v1-rev20190910-1.30.3.jar
> >> +com.google.apis:google-api-services-storage:v1-rev20190910-1.30.3
> >>  com.google.auth:google-auth-library-credentials:0.18.0
> >>  com.google.auth:google-auth-library-oauth2-http:0.18.0
> >>  com.google.auto.value:auto-value-annotations:1.6.6
> >>  com.google.cloud:google-cloud-core:1.91.3
> >>  com.google.cloud:google-cloud-core-http:1.91.3
> >> -com.google.cloud:google-cloud-storage:1.101.0
> >> +com.google.cloud:google-cloud-nio:0.120.0-alpha
> >> +com.google.cloud:google-cloud-storage:1.102.0
> >>  com.google.code.findbugs:jsr305:3.0.0
> >>  com.google.code.gson:gson:2.2.4
> >>  com.google.errorprone:error_prone_annotations:2.3.2
> >> @@ -240,21 +244,20 @@ com.google.guava:guava:20.0
> >>  com.google.http-client:google-http-client-appengine:1.32.1
> >>  com.google.http-client:google-http-client-jackson2:1.32.1
> >>  com.google.http-client:google-http-client:1.32.1
> >> -com.google.inject.extensions:guice-servlet:3.0
> >> -com.google.inject:guice:3.0
> >>  com.google.j2objc:j2objc-annotations:1.3
> >>  com.google.oauth-client:google-oauth-client:1.30.3
> >>  com.google.protobuf:protobuf-java-util:3.10.0
> >>  com.google.protobuf:protobuf-java:2.5.0
> >>  com.google.protobuf:protobuf-java:3.10.0
> >>  com.jamesmurty.utils:java-xmlbuilder:0.4
> >> +com.jamesmurty.utils:java-xmlbuilder:1.0
> >> +com.jayway.jsonpath:json-path:2.4.0
> >>  com.lmax:disruptor:3.3.4
> >>  com.ning:async-http-client:1.9.21
> >>  com.ning:compress-lzf:1.0.3
> >>  com.tdunning:t-digest:3.2
> >> -com.twitter:ch

Re: [incubator-pinot] branch release-0.4.0-rc1 updated: WIP

[kishore g]

Can we make sure we run the integration test with sampling turned off for
this release

On Mon, May 25, 2020 at 4:24 PM  wrote:

> This is an automated email from the ASF dual-hosted git repository.
>
> haibow pushed a commit to branch release-0.4.0-rc1
> in repository https://gitbox.apache.org/repos/asf/incubator-pinot.git
>
>
> The following commit(s) were added to refs/heads/release-0.4.0-rc1 by this
> push:
>  new 88f41ea  WIP
> 88f41ea is described below
>
> commit 88f41ea971258a11b437d75e248fc84140cb150f
> Author: haibow 
> AuthorDate: Mon May 25 16:23:33 2020 -0700
>
> WIP
> ---
>  LICENSE-binary  | 154
> 
>  NOTICE-binary   |  52 +++-
>  licenses-binary/LICENSE-gpl-2.0.txt | 125 +
>  3 files changed, 280 insertions(+), 51 deletions(-)
>
> diff --git a/LICENSE-binary b/LICENSE-binary
> index 5c0e3e4..b537893 100644
> --- a/LICENSE-binary
> +++ b/LICENSE-binary
> @@ -211,28 +211,32 @@ com.clearspring.analytics:stream:2.7.0
>  com.fasterxml.jackson.core:jackson-annotations:2.9.8
>  com.fasterxml.jackson.core:jackson-core:2.9.8
>  com.fasterxml.jackson.core:jackson-databind:2.9.8
> +com.fasterxml.jackson.dataformat:jackson-dataformat-xml:2.9.8
>  com.fasterxml.jackson.dataformat:jackson-dataformat-yaml:2.9.8
> +com.fasterxml.jackson.datatype:jackson-datatype-jsr310:2.10.0
>  com.fasterxml.jackson.jaxrs:jackson-jaxrs-base:2.9.8
>  com.fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider:2.9.8
>  com.fasterxml.jackson.module:jackson-module-jaxb-annotations:2.9.8
>  com.fasterxml.jackson.module:jackson-module-paranamer:2.6.5
>  com.fasterxml.jackson.module:jackson-module-scala_2.11:2.6.5
> +com.fasterxml.woodstox:woodstox-core:5.0.3
>  com.github.jnr:jffi:1.2.9
>  com.github.jnr:jnr-constants:0.8.7
>  com.github.jnr:jnr-ffi:2.0.3
> +com.google.api-client:google-api-client
>  com.google.api.grpc:proto-google-common-protos:1.17.0
>  com.google.api.grpc:proto-google-iam-v1:0.13.0
>  com.google.api:api-common:1.8.1
>  com.google.api:gax:1.49.1
>  com.google.api:gax-httpjson:0.66.1
> -com.google.api:google-api-client:1.30.4
> -com.google.api:google-api-services-storage:v1-rev20190910-1.30.3.jar
> +com.google.apis:google-api-services-storage:v1-rev20190910-1.30.3
>  com.google.auth:google-auth-library-credentials:0.18.0
>  com.google.auth:google-auth-library-oauth2-http:0.18.0
>  com.google.auto.value:auto-value-annotations:1.6.6
>  com.google.cloud:google-cloud-core:1.91.3
>  com.google.cloud:google-cloud-core-http:1.91.3
> -com.google.cloud:google-cloud-storage:1.101.0
> +com.google.cloud:google-cloud-nio:0.120.0-alpha
> +com.google.cloud:google-cloud-storage:1.102.0
>  com.google.code.findbugs:jsr305:3.0.0
>  com.google.code.gson:gson:2.2.4
>  com.google.errorprone:error_prone_annotations:2.3.2
> @@ -240,21 +244,20 @@ com.google.guava:guava:20.0
>  com.google.http-client:google-http-client-appengine:1.32.1
>  com.google.http-client:google-http-client-jackson2:1.32.1
>  com.google.http-client:google-http-client:1.32.1
> -com.google.inject.extensions:guice-servlet:3.0
> -com.google.inject:guice:3.0
>  com.google.j2objc:j2objc-annotations:1.3
>  com.google.oauth-client:google-oauth-client:1.30.3
>  com.google.protobuf:protobuf-java-util:3.10.0
>  com.google.protobuf:protobuf-java:2.5.0
>  com.google.protobuf:protobuf-java:3.10.0
>  com.jamesmurty.utils:java-xmlbuilder:0.4
> +com.jamesmurty.utils:java-xmlbuilder:1.0
> +com.jayway.jsonpath:json-path:2.4.0
>  com.lmax:disruptor:3.3.4
>  com.ning:async-http-client:1.9.21
>  com.ning:compress-lzf:1.0.3
>  com.tdunning:t-digest:3.2
> -com.twitter:chill-java:0.8.0
> -com.twitter:chill_2.11:0.8.0
> -com.typesafe:config:1.3.2
> +com.typesafe.netty:netty-reactive-streams-http:2.0.4
> +com.typesafe.netty:netty-reactive-streams:2.0.4
>  com.typesafe.scala-logging:scala-logging_2.11:3.9.0
>  com.yammer.metrics:metrics-core:2.2.0
>  commons-beanutils:commons-beanutils:1.8.3
> @@ -271,15 +274,35 @@ commons-lang:commons-lang:2.6
>  commons-logging:commons-logging:1.2
>  commons-net:commons-net:3.1
>  io.airlift:aircompressor:0.10
> +io.confluent:common-config:5.3.1
> +io.confluent:common-utils:5.3.1
> +io.confluent:kafka-avro-serializer:5.3.1
> +io.confluent:kafka-schema-registry-client:5.3.1
>  io.dropwizard.metrics:metrics-core:3.2.3
> -io.dropwizard.metrics:metrics-graphite:3.1.2
> -io.dropwizard.metrics:metrics-json:3.1.2
> -io.dropwizard.metrics:metrics-jvm:3.1.2
> +io.dropwizard.metrics:metrics-graphite:3.2.3
> +io.dropwizard.metrics:metrics-json:3.2.3
> +io.dropwizard.metrics:metrics-jvm:3.2.3
>  io.grpc:grpc-context:1.22.1
> +io.netty:netty-all:4.1.42.Final
> +io.netty:netty-buffer:4.1.42.Final
> +io.netty:netty-codec-http2:4.1.42.Final
> +io.netty:netty-codec-http:4.1.42.Final
> +io.netty:netty-codec-socks:4.1.42.Final
> +io.netty:netty-codec:4.1.42.Final
> +io.netty:netty-common:4.1.42.Final
> +io.netty:netty-handler-proxy:4.1.42.Final
> +io.netty:ne

Re: Preparing for the upcoming Pinot 0.4.0 release

[kishore g]

If we have thought of all the cases and know that it won't impact existing
- why delay it to the next release?. The earlier we start pushing users to
use datetimespec the better it is for us.

On Tue, May 19, 2020 at 10:20 AM Subbu Subramaniam 
wrote:

> I meant to suggest  release 0.4.0 excluding PR 5399 (date time spec)
>
> -Subbu
>
> On 2020/05/19 17:18:13, Subbu Subramaniam  wrote:
> > On the other hand, it may be wise to release 0.4.0 without this change.
> >
> > Those of us who pick up changes regularly from the master can verify
> that there is no incompatibility inadvertently introduced  by this change
> (Not everything can be caught by review)
> >
> > And then we can push this change in 0.5.0, not worrying about another
> backward incomaptibility introduced trying to fix a previous incompat.
> >
> > My suggestion
> >
> > -Subbu
> >
> > On 2020/05/19 16:36:16, Neha Pawar  wrote:
> > > Please let's wait for
> https://github.com/apache/incubator-pinot/pull/5399 the
> > > DateTimeFieldSpec support. I have 2 reviews, waiting on just 1 more.
> > > Will keep you posted.
> > >
> > > Thanks,
> > > *Neha Pawar*
> > >
> > > 
> > >
> > >
> > > On Sun, May 17, 2020 at 6:03 PM H  wrote:
> > >
> > > > Will wait for a few more diffs and revisit the release the coming
> week.
> > > > Please let me know if you are planning on some diffs and would like
> to get
> > > > them in the release.
> > > >
> > > > On Thu, May 14, 2020 at 8:09 PM H  wrote:
> > > >
> > > > > Thanks for letting me know Mayank!
> > > > >
> > > > > On Thu, May 14, 2020 at 4:43 PM Mayank Shrivastava
> > > > >  wrote:
> > > > >
> > > > >> 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
> > > > >> >
> > > > >>
> > > > >
> > > >
> > >
> >
> > -
> > 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

[kishore g]

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
>

Re: Pinot server RAM not getting released

[kishore g]

Adding Pinot dev.

On Mon, Apr 6, 2020 at 11:25 PM shounak kulkarni 
wrote:

> I have deployed pinot in a kubernetes cluster. When I start ingesting data
> in kafka, the RAM keeps on piling up even after segment creation and
> eventually pod crashes due to OOM.
> I am keeping the segment threshold size as 100 and ingesting about 10
> million entries in kafka, memory limit is 4GB for server.
>
> Thanks!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Pinot Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pinot_users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pinot_users/ad3fb0de-0407-4bfe-bc2d-c17e68f7b8f0%40googlegroups.com
> 
> .
>

Re: Issue: Data-inconsistency during segment push

[kishore g]

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

[kishore g]

Apache allowed us to create a repo but it won't give access to GitBook to
write to it. Options

- create a separate repo for pinot-docs outside of Apache and grant access
to GitBook
- move back to the old way of editing docs.

thanks
Kishore G

On Wed, Mar 25, 2020 at 10:21 AM kishore g  wrote:

> Done: https://github.com/apache/incubator-pinot-docs
>
>
>
> On Wed, Mar 25, 2020 at 10:18 AM Xiang Fu  wrote:
>
>> How about  https://github.com/apache/incubator-pinot-docs <
>> https://github.com/apache/incubator-pinot-docs>
>>
>> Similar to
>> https://github.com/apache/incubator-pinot-site <
>> https://github.com/apache/incubator-pinot-site>
>> https://github.com/apache/incubator-pinot <
>> https://github.com/apache/incubator-pinot>
>>
>> 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

[kishore g]

Done: https://github.com/apache/incubator-pinot-docs



On Wed, Mar 25, 2020 at 10:18 AM Xiang Fu  wrote:

> How about  https://github.com/apache/incubator-pinot-docs <
> https://github.com/apache/incubator-pinot-docs>
>
> Similar to
> https://github.com/apache/incubator-pinot-site <
> https://github.com/apache/incubator-pinot-site>
> https://github.com/apache/incubator-pinot <
> https://github.com/apache/incubator-pinot>
>
> 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
>
>

Apache Pinot Docs repo name

[kishore g]

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

[kishore g]

+1

On Tue, Mar 17, 2020 at 10:02 AM Neha Pawar  wrote:

> +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: Pinot-incubator question about unofficial publications

[kishore g]

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
> > > <https://thenewstack.io/linkedin-code-review/>?
> > >
> >
>
> -
> 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

[kishore g]

+1

On Tue, Mar 3, 2020 at 1:29 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-rc0
>
> Git tag for this release:
> https://github.com/apache/incubator-pinot/tree/release-0.3.0-rc0
>
> Git hash for this release:
> ca35bc64929ff27683e5f72ec2691a5dff6e89cf
>
> 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-rc0
> GitBook:
> https://apache-pinot.gitbook.io/apache-pinot-cookbook/releases/0.3.0
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachepinot-1006
>
> 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: [NOTICE] Structural changes to Apache downloads

[kishore g]

FYI

On Wed, Mar 4, 2020 at 7:04 AM Daniel Gruno  wrote:

> Hello, Apache PMCs,
>
> In order to better provide our millions of users with downloads, the
> Apache Infrastructure Team has been restructuring the way downloads work
> for our main distribution channels in the past few weeks. For users,
> this will largely go unnoticed, and for projects likely the same, but we
> did want to reach out to projects and inform them of the changes we've
> made:
>
> As of March 2020, we are deprecating www.apache.org/dist/ in favor of
> https://downloads.apache.org/ for backup downloads as well as signature
> and checksum verification. The primary driver has been splitting up web
> site visits and downloads to gain better control and offer a better
> service for both downloads and web site visits.
>
> As stated, this does not impact end-users, and should have a minimal
> impact on projects, as our download selectors as well as visits to
> www.apache.org/dist/ have been adjusted to make use of
> downloads.apache.org instead. We do however ask that projects, in their
> own time-frame, change references on their own web sites from
> www.apache.org/dist/ to downloads.apache.org wherever such references
> may exist, to complete the switch in full. We will NOT be turning off
> www.apache.org/dist/ in the near future, but would greatly appreciate if
> projects could help us transition away from the old URLs in their
> documentation and on their download pages.
>
> The standard way of uploading releases[1] will STILL apply, however
> there may be a short delay (<= 15 minutes) between releasing and
> releases showing up on downloads.apache.org for technical reasons.
>
> If you have any questions about this change, please do not hesitate
> to reach out to us at us...@infra.apache.org.
>
> With regards,
> Daniel on behalf of ASF Infrastructure.
>
> [1] https://www.apache.org/legal/release-policy.html#upload-ci
>

Re: Pinot-incubator question about unofficial publications

[kishore g]

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

Re: Jepsen testing for Pinot

[kishore g]

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

Re: Jepsen testing for Pinot

[kishore g]

Does not make sense for Pinot

On Mon, Feb 24, 2020 at 1:10 PM siddharth teotia 
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
>

Moving from RTD to Gitbook

[kishore g]

Hi,

In the next release (should happen over the next couple of weeks), we will
be moving out of ReadTheDocs to Gitbook. Going forward, please use GitBook
while adding any documentation. We have moved all the content from RTD to
GitBook. I am still working on re-organizing the contents and adding new
content.

Please let me know if you have any questions/comments.

thanks,
Kishore G

Cleanup Pom

[kishore g]

has anyone tried using this?

https://github.com/kdgregory/pomutil

Re: Preparing for upcoming Pinot Release

[kishore g]

Hi Subbu,

I am with you on significant changes to the package names and the need to
recompile the code if anyone has the wrapper like LinkedIn. What do you
think is the best way to communicate this without calling it 1.0.

thanks,
Kishore G




On Sun, Feb 16, 2020 at 9:40 AM Subbu Subramaniam 
wrote:

> I disagree.
>
> In LinkedIn, we had to change our wrapper software significantly due to
> the API (and package name) changes.
>
> Have you compiled the release notes? That should indicate the amount of
> changes that went in.
>
> -Subbu
>
> On 2020/02/16 05:49:16, Fu Xiang  wrote:
> > Regarding the version, I suggest to still call it 0.3.0 as the
> > PluginManager is still backward compatible from users' perspective in PR:
> > https://github.com/apache/incubator-pinot/pull/5035.
> >
> > We can leave 1.0.0 for something bigger later.
> >
> > On Thu, Feb 13, 2020 at 12:08 Subbu Subramaniam 
> wrote:
> >
> > > Thanks, @kishore g 
> > > Please do send it out for a review when the docs are ready
> > >
> > > thanks
> > >
> > > -Subbu
> > >
> > >
> > > On Thu, Feb 13, 2020 at 10:27 AM kishore g 
> wrote:
> > >
> > > > @Siddharth Teotia  Lets get the text PR
> merged.
> > > > Will be good to release it as experimental and collect feedback.
> > > >
> > > > @Subbu Subramaniam  We have moved all the docs
> from
> > > > RTD to gitbook. I need to restructure a bit and it will be ready to
> go by
> > > > the time we make the release.
> > > > Let's call out all the major changes in 1.0.0
> > > >
> > > > On Thu, Feb 13, 2020 at 9:59 AM Subbu Subramaniam <
> mcvsu...@apache.org>
> > > > wrote:
> > > >
> > > >> Hi Xiang,
> > > >>
> > > >> Thanks for taking on the release work.
> > > >>
> > > >> I suppose the version will be 1.0.0?
> > > >>
> > > >> Please make sure that:
> > > >> 1. Either we are migrated fully to the new documentation, OR we have
> > > >> documented all new features in the existing documentation. The
> current
> > > >> situation is that neither of these is true. It will be unfortunate
> if we
> > > >> make a release with documentation in two places, neither of which is
> > > >> complete. I will be willing to help fix the doc issue. Please send
> out
> > > an
> > > >> email to committers (or general) providing appropriate instructions,
> > > and we
> > > >> can have the community fix the documents before the release.
> > > >> 2. The release notes lists all the incompatiblities introduced, and
> > > >> migration plans, etc.  I know of at least one incompatibility. You
> > > cannot
> > > >> upgrade from 0.1 to 1.0 without going through 0.2, because of
> > > >> incomaptibolituy introduced in
> > > >> https://github.com/apache/incubator-pinot/pull/4346 (if you have
> those
> > > >> queries, of course). There may be others, given that we have had a
> big
> > > >> overhaul.
> > > >>
> > > >> thanks again
> > > >>
> > > >> -Subbu
> > > >>
> > > >>
> > > >> On 2020/02/13 00:08:20, Fu Xiang  wrote:
> > > >> > Hi Pinot Community,
> > > >> >
> > > >> > I'm preparing the upcoming release from current master branch
> commit (
> > > >> > 7cca1442d7ad41705643862b7237f445e8803368
> > > >> > <
> > > >>
> > >
> https://github.com/apache/incubator-pinot/commit/7cca1442d7ad41705643862b7237f445e8803368
> > > >> >)
> > > >> > as of date: Wed Feb 12 15:58:31 PST 2020.
> > > >> >
> > > >> > Please let me know if you still have any changes wanted to get in
> by
> > > >> > tomorrow Noon.
> > > >> >
> > > >> > Best,
> > > >> >
> > > >> > Xiang
> > > >> >
> > > >>
> > > >>
> -
> > > >> 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 upcoming Pinot Release

[kishore g]

@Siddharth Teotia  Lets get the text PR merged. Will
be good to release it as experimental and collect feedback.

@Subbu Subramaniam  We have moved all the docs from RTD
to gitbook. I need to restructure a bit and it will be ready to go by the
time we make the release.
Let's call out all the major changes in 1.0.0

On Thu, Feb 13, 2020 at 9:59 AM Subbu Subramaniam 
wrote:

> Hi Xiang,
>
> Thanks for taking on the release work.
>
> I suppose the version will be 1.0.0?
>
> Please make sure that:
> 1. Either we are migrated fully to the new documentation, OR we have
> documented all new features in the existing documentation. The current
> situation is that neither of these is true. It will be unfortunate if we
> make a release with documentation in two places, neither of which is
> complete. I will be willing to help fix the doc issue. Please send out an
> email to committers (or general) providing appropriate instructions, and we
> can have the community fix the documents before the release.
> 2. The release notes lists all the incompatiblities introduced, and
> migration plans, etc.  I know of at least one incompatibility. You cannot
> upgrade from 0.1 to 1.0 without going through 0.2, because of
> incomaptibolituy introduced in
> https://github.com/apache/incubator-pinot/pull/4346 (if you have those
> queries, of course). There may be others, given that we have had a big
> overhaul.
>
> thanks again
>
> -Subbu
>
>
> On 2020/02/13 00:08:20, Fu Xiang  wrote:
> > Hi Pinot Community,
> >
> > I'm preparing the upcoming release from current master branch commit (
> > 7cca1442d7ad41705643862b7237f445e8803368
> > <
> https://github.com/apache/incubator-pinot/commit/7cca1442d7ad41705643862b7237f445e8803368
> >)
> > as of date: Wed Feb 12 15:58:31 PST 2020.
> >
> > Please let me know if you still have any changes wanted to get in by
> > tomorrow Noon.
> >
> > Best,
> >
> > Xiang
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
> For additional commands, e-mail: dev-h...@pinot.apache.org
>
>

Re: Remove index from segment

[kishore g]

It's not trivial for users to know when to add an index. It definitely
improves the experience if they can easily add/remove indexes. Regarding
storage, indexes can be quite big depending on the cardinality for e.g. inv
index on something like memberId is not very useful.

On Tue, Feb 11, 2020 at 5:07 PM Mayank Shrivastava 
wrote:

> Subbu, I think the proposal is to reduce the storage cost, which is why I
> asked how often is that seen (outside LinkedIn).
>
> Sent from my iPhone
>
> > On Feb 11, 2020, at 3:38 PM, Subbu Subramaniam 
> wrote:
> >
> > I believe we do not map the index if it is not sset in the table
> config, so the index is not loaded.
> >
> > The cost on storage exists, but hopefully is a lot smaller than memory.
> >
> > -Subbu
> >
> >> On 2020/02/11 22:37:13, 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
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
> For additional commands, e-mail: dev-h...@pinot.apache.org
>
>

Remove index from segment

[kishore g]

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.

Re: Convert dictionary encoded into raw

[kishore g]

Any idea on what should be the threshold?

Good point about the variable-length column, should we rely on a bloom
filter instead?

On Tue, Feb 11, 2020 at 2:14 PM Siddharth Teotia
 wrote:

> Yes. Especially if the data is fixed width and high cardinality then
> dictionary encoding is not going to be very useful.
>
> May be for fixed width, we should create dictionary only if cardinality is
> below a certain threshold?
>
> For variable width, whether cardinality is high or low, dictionary
> encoding will improve filter processing if column is used heavily in
> filters. So may be for variable width we should always create dictionary
> unless indicated otherwise in table config?
> ________
> From: kishore g 
> Sent: Tuesday, February 11, 2020 2:10 PM
> To: dev@pinot.apache.org 
> Subject: Convert dictionary encoded into raw
>
> As of today, we apply dictionary encoding for all columns by default. We
> should probably move a hybrid approach where we decide the encoding based
> on the data profile. For e.g. if the cardinality of the column is very high
> (which is the case for metrics), dictionary encoding does not provide a lot
> of value.
>
> Thoughts?
>

Convert dictionary encoded into raw

[kishore g]

As of today, we apply dictionary encoding for all columns by default. We
should probably move a hybrid approach where we decide the encoding based
on the data profile. For e.g. if the cardinality of the column is very high
(which is the case for metrics), dictionary encoding does not provide a lot
of value.

Thoughts?

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

[kishore g]

+1

On Mon, Nov 18, 2019 at 7:47 PM Olivier Lamy  wrote:

> +1
>
> On Tue, 19 Nov 2019 at 3:49 am, Subbu Subramaniam 
> wrote:
>
> > Hi all,
> >
> > This is a call for vote to the release Apache Pinot (incubating) version
> > 0.2.0.
> >
> > Apache Pinot (incubating) is a distributed columnar storage engine that
> can
> > ingest data in realtime and serve analytical queries at low latency.
> >
> > Pinot community has voted and approved this release.
> >
> > Vote threads:
> >
> >
> https://lists.apache.org/thread.html/302ea5dd91e731eaaf9ce3881e027613ebc76a8c01472c0517b56e89@%3Cdev.pinot.apache.org%3E
> >
> >
> https://lists.apache.org/thread.html/3d785c502905b23f1d4d1da8718501a7cb4ef8245dd665fe99bf6daf@%3Cdev.pinot.apache.org%3E
> >
> > Result thread:
> >
> >
> https://lists.apache.org/thread.html/c425825f7d9da198adfbc5c5633dd0300f77f0ce3f9b88dba92dbe60@%3Cdev.pinot.apache.org%3E
> >
> > The release candidate:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.2.0-rc0
> >
> > Git tag for this release:
> > https://github.com/apache/incubator-pinot/tree/release-0.2.0-rc0
> >
> > Git hash for this release:
> > f8e1980c4160ac7fd2686d9edefab9ac0a825c5b
> >
> > The artifacts have been signed with key: B530034C, which can be
> > found in the following KEYS file.
> > https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS
> >
> > Release notes:
> > https://github.com/apache/incubator-pinot/releases/tag/release-0.2.0-rc0
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachepinot-1003
> >
> > Documentation on verifying a release candidate:
> >
> >
> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
> >
> >
> > The vote will be open for at least 72 hours or until necessary number of
> > votes are reached.
> >
> > Please vote accordingly,
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Thanks,
> > Apache Pinot (incubating) team
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
> > For additional commands, e-mail: dev-h...@pinot.apache.org
> >
> > --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>

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

[kishore g]

+1

Verified signatures. Updated wiki on Prerequistes needed to verify
signatures on Mac.
Quickstart works good.
http://localhost:9000/query/ is the wrong url. It has additional / in the
end that breaks the css. Not a blocker but something to fix in the next
release.

thanks

On Wed, Nov 13, 2019 at 1:49 PM Seunghyun Lee  wrote:

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

Pinot web console

[kishore g]

https://github.com/claudemamo/kafka-web-console

How about having something like this for Pinot?

Re: [MENTORS] Unapproved releases

[kishore g]

Thanks Justin. I will take a look at it. Olivier, we might need your
expertise here.

On Fri, Feb 8, 2019 at 2:24 PM Justin Mclean  wrote:

> Hi,
>
> Sorry to bother you again, but It seems this is not sinking in. I can see
> you have just marked a release candidate as a release here. [1] Mentors can
> you please deal with this.
>
> Thanks,
> Justin
>
> 1. https://github.com/apache/incubator-pinot/releases
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
> For additional commands, e-mail: dev-h...@pinot.apache.org
>
>

Re: You incubator report missing a few answers

[kishore g]

We haven’t added any new committers.

On Sun, Feb 3, 2019 at 6:31 PM Subbu Subramaniam 
wrote:

> Hi Justin,
>
> I believe we have not made any changes to PPMC after the initiation, but
> @kishoreg may have more information.
>
> I have updated the answer with this info. And yes, the mentors have been
> helpful, I filled that in as well.
>
> -Subbu
> PS: By mistake I ended up updating Jan 2019 report first, and then updated
> the Feb report as well.
> --
> *From:* Justin Mclean 
> *Sent:* Saturday, February 2, 2019 9:36 PM
> *To:* dev@pinot.apache.org
> *Subject:* You incubator report missing a few answers
>
> Hi,
>
> Could you please answer rtes following two questions in your report:
>
> When were the last committers or PPMC members elected?
>
> Have your mentors been helpful and responsive or are things falling
> through the cracks? In the latter case, please list any open issues
> that need to be addressed.
>
> Thanks,
> Justin
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
> For additional commands, e-mail: dev-h...@pinot.apache.org
>
>

Re: Requesting a review for updating license & notice information

[kishore g]

I think that should work. Olivier, do you see any issues with that?

On Wed, Jan 23, 2019 at 5:51 PM Seunghyun Lee  wrote:

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

Re: Podling Report Reminder - January 2019

[kishore g]

Subbu sent one to the private list.

On Thu, Dec 27, 2018 at 3:12 PM Felix Cheung 
wrote:

> Another reminder since we are less than one week away from the deadline.
>
> --
> *From:* Felix Cheung 
> *Sent:* Friday, December 21, 2018 8:07 PM
> *To:* dev@pinot.apache.org; g.kish...@gmail.com
> *Subject:* Re: Podling Report Reminder - January 2019
>
> Hi - quick reminder please see below.
>
> Report is due Wed January 02 -- Podling reports due by end of day
>
> Best to kick off discussions soon. Happy holidays!
>
>
> 
> From: jmcl...@apache.org
> Sent: Friday, December 21, 2018 4:47 PM
> To: d...@pinot.incubator.apache.org
> Subject: Podling Report Reminder - January 2019
>
> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 16 January 2019, 10:30 am PDT.
> 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, January 02).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> * Your project name
> * A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> * A list of the three most important issues to address in the move
> towards graduation.
> * Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> * How has the community developed since the last report
> * How has the project developed since the last report.
> * How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://wiki.apache.org/incubator/January2019
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> 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: Incubator Podling Report (Due 5th December)

[kishore g]

Yes, please go ahead. Thanks a lot.

On Wed, Dec 5, 2018 at 8:20 AM Felix Cheung 
wrote:

> Hi - just the quick note that the report is due today.
>
> Justin has sent a separate reminder. It’s important to put some quick
> status on this.
>
> For example, from what I know:
>
> - source repo migrated
> - email list setup - dev@ traffic is a bit light
> - website in progress
> - no change to committer & PPMC
> - ? contributor growth
>
> If dev@ is ok with this summary I can also write this into the wiki page
> as the project report.
>
>
> --
> *From:* Felix Cheung 
> *Sent:* Monday, December 3, 2018 9:58 AM
> *To:* dev@pinot.apache.org; kishore g; dev@pinot.apache.org;
> jmcl...@apache.org
> *Subject:* Re: Incubator Podling Report (Due 5th December)
>
> Process info here
> https://incubator.apache.org/guides/ppmc.html#podling_status_reports
>
> It’s a wiki page
> https://wiki.apache.org/incubator/December2018
>
>
> ________
> From: Subbu Subramaniam 
> Sent: Monday, December 3, 2018 9:39 AM
> To: kishore g; dev@pinot.apache.org; jmcl...@apache.org
> Subject: Re: Incubator Podling Report (Due 5th December)
>
> What is involved here?
>
> Having never done one before, I have no idea. Is there a template for the
> report?
>
> thanks
>
> -Subbu
> 
> From: kishore g 
> Sent: Sunday, December 2, 2018 2:57 PM
> To: dev@pinot.apache.org
> Subject: Re: Incubator Podling Report (Due 5th December)
>
> Subbu, do you want to take a stab at this?
>
> On Sun, Dec 2, 2018 at 12:30 PM Justin Mclean  wrote:
>
> > Hi,
> >
> > The incubator PMC would appreciated if you could complete the podling
> > report on time it's due on 5th December in a few days. It takes time to
> > prepare the incubator report, have your mentors sign off the report and
> for
> > the board to review it, so it's best if you can get it in early.
> >
> > Thanks,
> > Justin
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
> > For additional commands, e-mail: dev-h...@pinot.apache.org
> >
> >
>

Re: Incubator Podling Report (Due 5th December)

[kishore g]

Subbu, do you want to take a stab at this?

On Sun, Dec 2, 2018 at 12:30 PM Justin Mclean  wrote:

> Hi,
>
> The incubator PMC would appreciated if you could complete the podling
> report on time it's due on 5th December in a few days. It takes time to
> prepare the incubator report, have your mentors sign off the report and for
> the board to review it, so it's best if you can get it in early.
>
> Thanks,
> Justin
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
> For additional commands, e-mail: dev-h...@pinot.apache.org
>
>

Fwd: Time To Propose Your ApacheCon 2019 Project Summit

[kishore g]

FYI

-- Forwarded message -
From: Rich Bowen 
Date: Tue, Nov 27, 2018 at 6:30 AM
Subject: Time To Propose Your ApacheCon 2019 Project Summit
To: plann...@apachecon.com 


Save the date: ApacheCon North America will be held in Las Vegas, at the
Flamingo Hotel, September 9th through 12th, 2019. This is our 20th
anniversary event, and we really want you, your project, and its
community, to be involved.

If you want to be part of making this event happen, please join the
privately-archived planners@ mailing list by sending email to
planners-subscr...@apachecon.com from your apache.org email address.

A call for presentations will be announced soon. You should start giving
some thought to what story your project wants to tell at this event, and
working with your project community to craft presentations around that
story.

We will have a number of spaces for projects to conduct project summits,
hackathons, or mini-conferences, lasting anywhere from a half day to the
entire four days of the event.

If your project, or group of several related projects, would like to
claim an entire track (one, two, or three days of content) and craft
that story yourselves, please propose your track or summit here:
https://goo.gl/forms/lczPlXTmGNIsRf823

The deadline for proposing a project/topic event is January 7th, (The
first Monday of the new year) so that we can reflect these topics in the
CFP.

If your project holds your own standalone events(s) please consider
co-locating with ApacheCon this coming year. We’ll help you promote your
event, both as part of ApacheCon, and as its own brand. You get the best
of both worlds - you get your own event, with control of your content,
and you get to be part of a larger convention with a broader audience.

This is your conference, and we are counting on you to step up and make
it yours.

Stay tuned for more information, on the planners list, and on our
Twitter account @apachecon. And we look forward to seeing you to see you
in Vegas in September!

Rich Bowen, VP Conferences, and the ApacheCon Planners

-- 
@apachecon
http://apachecon.com/
plann...@apachecon.com

Re: Podling Report Reminder - November 2018

[kishore g]

Thanks Justin. I will take care of this today.

On Sat, Nov 3, 2018 at 3:48 PM Justin Mclean  wrote:

> Hi,
>
> The incubator PMC would appreciated if you could complete the podling
> report on time it's due on  7th November in a few days. It takes time to
> prepare the incubator report, have your mentors sign off the report and for
> the board to review it, so it's best if you can get it in early.
>
> Thanks,
> Justin
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
> For additional commands, e-mail: dev-h...@pinot.apache.org
>
>

Test

[kishore g]