This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regen_bot
in repository https://gitbox.apache.org/repos/asf/camel.git
omit e983c632627 Regen for commit 5162d38f3528e507947b046830d46382f6b0efa8
add 8d91377e498 CAMEL-18393 Camel-bigquery: NPE if select * is requested
(#8162)
add da4edf1e41a Regen for commit 8d91377e49831e4ab883d123d1804b08a77ef374
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 (e983c632627)
\
N -- N -- N refs/heads/regen_bot (da4edf1e41a)
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:
.../google/bigquery/sql/GoogleBigQuerySQLProducer.java | 10 ++++++++--
.../camel-google-bigquery/src/test/resources/sql/delete.sql | 2 +-
.../camel-google-bigquery/src/test/resources/sql/insert.sql | 2 +-
3 files changed, 10 insertions(+), 4 deletions(-)
