As discussed in this thread, PQL endpoints have been deprecated in 0.7.0
release. Yupeng is working on the release.
Please let us know if the team got a chance to discuss PQL migration
at Uber before 1.0/graduation (planned for April) so that at least PQL
endpoints can be removed in 1.0
On Mon,
I think 1.0 is targeted for April. Yupeng / Ting, can you please confirm if
this timeline works ?
On Fri, Feb 19, 2021 at 9:32 PM Mayank Shrivastava
wrote:
> Yupeng, From what I understand we are targeting graduation this quarter,
> with 1.0. Does that work for Uber?
>
> Cheers
> Mayank
>
> On
Yupeng, From what I understand we are targeting graduation this quarter, with
1.0. Does that work for Uber?
Cheers
Mayank
> On Feb 19, 2021, at 9:10 PM, Yupeng Fu wrote:
>
>
> Sidd, from this year we release off the master every a few weeks and don't
> wait for the next Pinot release.
>
>
Sidd, from this year we release off the master every a few weeks and don't
wait for the next Pinot release.
+1 to Kishore's suggestion. It's a common practice for Apache projects to
deprecate a feature and remove it in the next major version.
Yupeng
On Fri, Feb 19, 2021 at 7:30 PM kishore g
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
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
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.
Thanks Xiang.
Hi Ting,
Will this PR help expedite the move to SQL at Uber?
Cheers,
Mayank
> On Feb 19, 2021, at 5:41 PM, Xiang Fu wrote:
>
-
To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
For additional commands,
eng Fu mailto:yupeng...@gmail.com>>
> Sent: Friday, February 19, 2021 3:33 PM
> To: dev@pinot.apache.org <mailto:dev@pinot.apache.org> <mailto:dev@pinot.apache.org>>
> Cc: Ujwala Tulshigiri mailto:ujw...@uber.com>>; Girish
> Baliga mailto:bal...@uber.com>&
query Pinot, so it should not
> matter?
>
> Regards,
> Mayank
> --
> *From:* Yupeng Fu
> *Sent:* Friday, February 19, 2021 3:33 PM
> *To:* dev@pinot.apache.org
> *Cc:* Ujwala Tulshigiri ; Girish Baliga ;
> Yupeng Fu
> *Subject:* Re: Re
Tulshigiri ; Girish Baliga ;
Yupeng Fu
Subject: Re: Removing PQL endpoint
+1 to what Ting suggested. The Presto to SQL migration from Uber side still
needs a few more months.
Alternatively, could we have a config to disable (and deprecate) the endpoint
first, with the default value disabled? So
+1 to what Ting suggested. The Presto to SQL migration from Uber side still
needs a few more months.
Alternatively, could we have a config to disable (and deprecate) the
endpoint first, with the default value disabled? So the endpoint removal
can be done together with the PQL cleanup.
Thanks,
Hi Sidd,
Uber still uses PQL extensively with a few hundred tables and dozens of
use cases. It takes us time to move out of PQL. End of Feb is too tight for
us to complete the migration process. Can you postpone the removal of the
query endpoints at least to the end of June so that we can
Hi All,
It's been a while since Pinot has moved to SQL compliant syntax and semantics.
Calcite SQL compiler has allowed us to move to standard SQL syntax and we will
continue to leverage it for parsing, compiling and optimizing queries as more
complex query functionality is added.
However,
14 matches
Mail list logo
