I am checking with a few folks (Jackie, Gonzalo, Mayank). It looks like it was merged 21 March, so it should be available. Did you have any specific questions about it?

I believe this feature is available now. Adding @Shounak Kulkarni for details.

Yeah one specific question I had was: ideally if we had a "database" construct, then we shouldn't need to set any query option or http headers. A query such as

select * from <http://my_db.my|my_db.my>_table

should be sufficient. But looks like we require:

SET database=my_db;
SELECT * FROM my_table; -- this can also be my_db.my_table

I was wondering if we plan to get rid of the query option requirement

I see. Let's wait for @Shounak Kulkarni to chime in.

Or adding @Neha Pawar in case she knows the answer.

Here's the first draft of the release notes: https://gist.github.com/ankitsultana/c195c82b26cfa7a1b873f1ab85492b6c Grammatical errors, re-ordering based on priority and other issues are expected. Do call out any major/minor issues still. Thanks. cc: @Mayank @Peter Corless

Thanks for sharing! Looking through today. Also attn: @Vik Gamov.

Hey folks, I should be able to create the pre-release on Monday. Lmk if you have any feedback on the release notes. I'll clean them up by EOD.

Hi @Ankit Sultana! An eagle-eyed reviewer spotted that there were apparently a number of issues that all pointed to the same Github PR, but only the first is accurate:

These features point to the same PR, but only the first is accurate:

• Support for SQL Formatting in Query Editor #11725

• Hash Function for UUID Primary Keys #11725

• CLP Compression Codec in Forward Indexes #11725

I could find one correct PR: • Hash Function for UUID Primary Keys #12538 I couldn't find anything matching CLP Compression Codec in Forward Indexes

Thanks! Will fix this and also review the other links for similar errors

One more thing I noted:

New Window Functions: LEAD, LAG, FIRST_VALUE, LAST_VALUE #12878 #13340

• LEAD returns the value from the next row in a frame

• LAG returns the value from the previous row in a frame

• FIRST_VALUE and LAST_VALUE return the respective extremal values in the frame

Technically, don't "LEAD" and "LAG" include an offset so you could return values from n rows next or previous in a frame?

yup this is fixed in the latest revision. I am yet to update it in gist... will do that in an hour

All issues should be fixed now. https://gist.github.com/ankitsultana/c195c82b26cfa7a1b873f1ab85492b6c I'll be creating a pre-release shortly.

Congrats! I just spotted rc0! Hope you get great feedback and test coverage. https://github.com/apache/pinot/releases/tag/release-1.2.0-rc0

I am running into issues with the release process. Fixed two of them so far but ran into another one late yesterday. Will continue working on it

Thanks @Ankit Sultana

Hey @Ankit Sultana! One thing that caused some confusion...

Improved MV and Array Function Support

• Added array sum aggregation functions for point-wise array operations #13324.

• Added support for

valueIn

MV transform function #13443.

• Fixed bug in numeric casts for MV columns in filters #13425.

• Fixed NPE in ArrayAgg when a column contains no data #13358.

• Fixed array literal handling #13345.

A lot of people (including myself) associate "MV" with materialized views, whereas "MV" in this context stands for multi-valued column. Maybe change the title as follows:

Improved Multi-Value (MV) and Array Function Support

Thoughts?

Thanks. updated

Checking in: I saw a number of +1's last week. What's the next steps for this? Are we going to spin the release this week, or were there any blockers encountered?

There was a bug reported and we decided today to add a cherry-pick and raise RC1

Thanks! Will let folks know.

Hi @Ankit Sultana! What's up with rc2? https://github.com/apache/pinot/tree/release-1.2.0-rc2

RC2 vote was raised last Saturday. Waiting for stamps from PMCs. I need two more (Xiang has provided one): https://lists.apache.org/list.html?dev@pinot.apache.org @Peter Corless: if you can help expedite the review that'd be great. I also want to complete the release asap

We have the the required votes now (3 +1 from PMCs). I'll close off the voting tomorrow morning and finish the rest of the steps asap.

Some background release tasks are ongoing which should finish in a few hours. I have updated GitHub release notes to point to the release tag (release-1.2.0). Once the background tasks are done, I'll build the docker image and complete some of the other steps. Hoping to wrap this up by tomorrow and we can make announcements tomorrow as well.

That's awesome! Let me know when the release notes go live and I'll get our social folks to share them out.

@Vik Gamov and I worked on a blog draft to cover this release for the StarTree site. Better than a draft, we have it on staging for you to view here! Final link will be different so don't share this out: https://startree-preview.vercel.app/blog/highlighting-innovation-in-apache-pinot-1-2

{Edit] @Ankit Sultana One fix I can see for the release notes is for this line: > Support for Uploading Externally Partitioned Segments for Upsert Backfill 13107 You have the link going to the files: https://github.com/apache/pinot/pull/13107/files Whereas the more useful link would go to the explanation: https://github.com/apache/pinot/pull/13107 You might want to check other PR#'s to see if that the case for any others.

archived the channel