Just forced this push to change the commit message from "[CALCITE-2787] Json aggregate calls with different null clause get incorrectly merged during converting from SQL to relational algebra” to "[CALCITE-2787] JSON aggregate calls with different null clause get incorrectly merged during converting from SQL to relational algebra”.
> On Feb 28, 2019, at 00:13, hon...@apache.org wrote: > > This is an automated email from the ASF dual-hosted git repository. > > hongze pushed a change to branch master > in repository https://gitbox.apache.org/repos/asf/calcite.git. > > > discard 5ada462 [CALCITE-2787] Json aggregate calls with different null > clause get incorrectly merged during converting from SQL to relational algebra > new 82ab280 [CALCITE-2787] JSON aggregate calls with different null > clause get incorrectly merged during converting from SQL to relational algebra > > 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 (5ada462) > \ > N -- N -- N refs/heads/master (82ab280) > > 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. > > The 3234 revisions listed above as "new" are entirely new to this > repository and will be described in separate emails. The revisions > listed as "add" were already present in the repository and have only > been added to this reference. > > > Summary of changes:
