generated from camel.apache.org/component
Update wiki Home page for google-bigquery
parent
6c0aec47a1
commit
35eddebca5
41
Home.md
41
Home.md
@ -1,21 +1,34 @@
|
|||||||
# Deploy the Project on CamelX Platform
|
# Google BigQuery
|
||||||
|
|
||||||
Deploy on CamelX Platform in three steps
|
Google BigQuery data warehouse for analytics.
|
||||||
|
|
||||||
## Step 1: Create a release
|
## Metadata
|
||||||
From the project space, click on **"Create a release"**
|
|
||||||
|
|
||||||
The new version is automatically available in the list
|
| Property | Value |
|
||||||
|
|----------|-------|
|
||||||
|
| Scheme | `google-bigquery` |
|
||||||
|
| Support Level | Stable |
|
||||||
|
| Labels | cloud,bigdata |
|
||||||
|
| Version | 4.10.2 |
|
||||||
|
|
||||||
## Step 2: Deploy
|
## Maven Dependency
|
||||||
Click on **"Deploy"**
|
|
||||||
|
|
||||||
- **Version:** Select the desired release
|
```xml
|
||||||
- **Environment:** Choose `Development`, `Staging`, or `Production`
|
<dependency>
|
||||||
- **Configuration:** Select the configuration source
|
<groupId>org.apache.camel</groupId>
|
||||||
- **Resources:** Set CPU and Memory
|
<artifactId>camel-google-bigquery</artifactId>
|
||||||
|
<version>4.10.2</version>
|
||||||
|
</dependency>
|
||||||
|
```
|
||||||
|
|
||||||
## Step 3: Expose
|
## Endpoint Properties
|
||||||
Enable **"Expose"**
|
|
||||||
|
|
||||||
Choose an **API Gateway** (Internal, Public, etc.)
|
| Name | Type | Required | Default | Description |
|
||||||
|
|------|------|----------|---------|-------------|
|
||||||
|
| `projectId` | string | ✓ | | Google Cloud Project Id |
|
||||||
|
| `datasetId` | string | ✓ | | BigQuery Dataset Id |
|
||||||
|
| `tableId` | string | | | BigQuery table id |
|
||||||
|
| `connectionFactory` | object | | | ConnectionFactory to obtain connection to Bigquery Service. If not provided the default one will be used |
|
||||||
|
| `useAsInsertId` | string | | | Field name to use as insert id |
|
||||||
|
| `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 |
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user