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):

If I set:

camel.component.twitter-search.xxx

The camel-twitter component should be added to the set of dependencies automatically.

Also because the new property-binding mechanism goes in error otherwise.

We should inspect direct properties and property-files.
We may extend the search also to linked secrets and configmaps.

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