Thanks for the suggestion.
Both documentation and expansion time warnings are added in
https://github.com/apache/beam/pull/34563 .
Yi
On Mon, Mar 31, 2025 at 2:43 PM Kenneth Knowles wrote:
> One way that you might be able to reach some users is to issue a warning
> in the code for SqlTransform
One way that you might be able to reach some users is to issue a warning in
the code for SqlTransform.expand(), with the deprecation timeline. Maybe
this is under "etc" but I wanted to mention it because the other items were
all documentation.
Kenn
On Mon, Mar 31, 2025 at 1:34 PM Yi Hu via dev w
Thanks for inputs! From discussion we have agreed on moving forward
Next step:
- Draft PR to note the deprecation status in Documentation, including
CHANGES, Javadoc, etc
- The earliest release to stop publishing ZetaSQL artifacts is pushed
further, not earlier than 1 full quarter before the nex
+1 to this deprecation. Thanks for putting together a clear summary.
FWIW it also has significantly worse performance than Calcite SQL dialect,
since it calls out to a ZetaSQL subprocess for most calculations, and that
is less optimized than Beam's Fn API.
Kenn
On Tue, Mar 25, 2025 at 4:18 PM Ro
I'm in favor of deprecating this and cleaning it up, but it depends on
usage. I suspect it is low (or possibly non-existent, especially as there's
little upside to moving away from the default). I cc'd user@ just in case
anyone wants to chime in there. This may be a good thing to add to our
release
Hi everyone,
I would like to bring up discussion for deprecating Beam SQL's ZetaSQL
component [1].
Beam SQL currently serves with two SQL dialects (i) Apache Calcite and (ii)
ZetaSQL dialects, see documentation [2] due to the following reasons
- Developments in Beam for ZetaSQL dialect effectivel
