I remember checking with Uber team a while back (forget if Haibo or Yupeng), I
was told that Uber uses Presto to query Pinot, so it should not matter?
Regards,
Mayank
________________________________
From: Yupeng Fu <yupeng...@gmail.com>
Sent: Friday, February 19, 2021 3:33 PM
To: dev@pinot.apache.org <dev@pinot.apache.org>
Cc: Ujwala Tulshigiri <ujw...@uber.com>; Girish Baliga <bal...@uber.com>;
Yupeng Fu <yup...@uber.com>
Subject: Re: Removing PQL endpoint
+1 to what Ting suggested. The Presto to SQL migration from Uber side still
needs a few more months.
Alternatively, could we have a config to disable (and deprecate) the endpoint
first, with the default value disabled? So the endpoint removal can be done
together with the PQL cleanup.
Thanks,
On Fri, Feb 19, 2021 at 3:13 PM TING CHEN <tingc...@uber.com.invalid> wrote:
Hi Sidd,
Uber still uses PQL extensively with a few hundred tables and dozens of use
cases. It takes us time to move out of PQL. End of Feb is too tight for us to
complete the migration process. Can you postpone the removal of the query
endpoints at least to the end of June so that we can complete the migration?
Thanks,
Ting
On Thu, Feb 18, 2021 at 4:06 PM Siddharth Teotia <steo...@linkedin.com.invalid>
wrote:
Hi All,
It's been a while since Pinot has moved to SQL compliant syntax and semantics.
Calcite SQL compiler has allowed us to move to standard SQL syntax and we will
continue to leverage it for parsing, compiling and optimizing queries as more
complex query functionality is added.
However, with legacy PQL code existing, we need to put double effort when
adding new query functionality to ensure it works for both PQL and SQL. It
hurts dev productivity. Since SQL is the path forward, we need to start
removing PQL from Pinot codebase.
Please see this issue created in August last year
https://github.com/apache/incubator-pinot/issues/5807<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fincubator-pinot%2Fissues%2F5807&data=04%7C01%7Cmshrivas%40linkedin.com%7C51f2c6f692984884b0a508d8d52edb7d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637493744639315649%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=IfTQ%2FLvlzQfKOmNDHrVgRTHDH6cE2Bwb3YHYLd7g2a0%3D&reserved=0>
proposing deprecation of PQL.
As a first step, we would be removing the PQL query endpoint on broker (/query)
and controller (/pql) by end of Feb. This will ensure that users can't use PQL
to query Pinot. The follow-up cleanup of PQL from the engine (parser, execution
engine) will be a subsequent task.
Please let us know if you have any questions.
Thanks
Sidd
--
--Yupeng
