This is an automated email from the ASF dual-hosted git repository.
amaliujia pushed a change to branch rw_beam_zetasql
in repository https://gitbox.apache.org/repos/asf/beam.git.
discard 5adf530 Merge branch 'master' into rw_beam_zetasql
discard 46c9f24 fixup: create job_PreCommit_BeamSQL_ZetaSQL.groovy.
discard 604b545 fixup: move BeamZetaSQL to a separate precommit.
discard 3d2f03c fixup: fix gradle build
discard c975bc4 fixup: fix rat
discard 8aaf327 fixup: update zetasql denpendency
discard 3c36700 [BEAM-7832] Add ZetaSQL as a dialect in BeamSQL.
add e2fd047 [BEAM-7832] Add ZetaSQL as a dialect in BeamSQL.
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (5adf530)
\
N -- N -- N refs/heads/rw_beam_zetasql (e2fd047)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.../main/java/org/apache/beam/sdk/extensions/sql/impl/BeamSqlEnv.java | 1 -
1 file changed, 1 deletion(-)
