Current behavior:
All the SQL activities either don't support Insert or are specific to a usecase

Expected behavior:
to be able to insert to a sql database in an activity

What is the motivation / use case for changing the behavior?
many workflows/pipelines require logging to a database

Additional information you deem important (e.g. I need this tomorrow):

File: examples/routes.groovy

Logs:

[1] 2020-12-03 16:41:56,092 WARN  [org.apa.cam.com.tim.TimerConsumer] (Camel (camel-1) thread #0 - timer://groovy) Error processing exchange. Exchange[19B282B64B1E822-0000000000000003]. Caused by: [groovy.lang.MissingPropertyException - No such property: DELEGATE_FIRST for class: org.apache.camel.k.loader.groovy.dsl.BeansConfiguration]: groovy.lang.Mis

Tell us about the problem you're trying to solve

When specifying a Dataset_id, the Google UI often includes the project_id in its naming like this: project_id:dataset_id

Describe the solution you’d like

In the BigQuery destination code, we could accept both syntax:

• project_id:dataset_id
• dataset_id

So it's smoother for the end user whether project_id is specified or not?

Is your feature request related to a problem? If yes, please describe the problem.
Currently our playground is without any code sharing capabilities.

Describe the solution you'd like to see.
Allow to share the playground with a certain query by adding the query as a base64 in the URL.

Were you inspired by anything else, that you have experienced?
Inspired by https://sandcastle