From c201ed2f7be85ce26c42f9b8ef9de2fba5eb4cad Mon Sep 17 00:00:00 2001
From: gitea_admin <admin@gitea.local>
Date: Wed, 11 Mar 2026 14:38:12 +0000
Subject: [PATCH] Update wiki Home page for google-bigquery-sql

---
 Home.md | 39 +++++++++++++++++++++++++--------------
 1 file changed, 25 insertions(+), 14 deletions(-)

diff --git a/Home.md b/Home.md
index 93a012c..729445d 100644
--- a/Home.md
+++ b/Home.md
@@ -1,21 +1,32 @@
-# Deploy the Project on CamelX Platform
+# Google BigQuery Standard SQL
 
-Deploy on CamelX Platform in three steps
+Access Google Cloud BigQuery service using SQL queries.
 
-## Step 1: Create a release
-From the project space, click on **"Create a release"**
+## Metadata
 
-The new version is automatically available in the list
+| Property | Value |
+|----------|-------|
+| Scheme | `google-bigquery-sql` |
+| Support Level | Stable |
+| Labels | cloud,messaging |
+| Version | 4.10.2 |
 
-## Step 2: Deploy
-Click on **"Deploy"**
+## Maven Dependency
 
-- **Version:** Select the desired release
-- **Environment:** Choose `Development`, `Staging`, or `Production` 
-- **Configuration:** Select the configuration source
-- **Resources:** Set CPU and Memory
+```xml
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-google-bigquery</artifactId>
+    <version>4.10.2</version>
+</dependency>
+```
 
-## Step 3: Expose
-Enable **"Expose"**
+## Endpoint Properties
 
-Choose an **API Gateway** (Internal, Public, etc.)
+| Name | Type | Required | Default | Description |
+|------|------|----------|---------|-------------|
+| `projectId` | string | ✓ |  | Google Cloud Project Id |
+| `queryString` | string | ✓ |  | BigQuery standard SQL query |
+| `connectionFactory` | object |  |  | ConnectionFactory to obtain connection to Bigquery Service. If not provided the default one will be used |
+| `lazyStartProducer` | boolean |  | `false` | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
+| `serviceAccountKey` | string |  |  | Service account key in json format to authenticate an application as a service account to google cloud platform |