¶ Description
Upload a table into Aleria database.
¶ Parameters
¶ Standard tab
Parameters:
- Connection
- Database name (you may paste aleria link here)
- Login/user
- Password
- Inspect database
- Table Name
- Operation
- Write all columns
¶ Advanced tab
Parameters:
- BULK operations: number of rows in one go
- Number of "Insert"s per transaction (0 = auto-commit)
- Allow "strange" characters in Column's Names
- Error Management
- Status Column Name
- In case of Error
- Write all rows
¶ About
Upload/insert rows from the pipeline into an Aleria (green UI) platform database.
This writer is the Aleria-only twin of our PostgreSQL “upsert/insert” actions: the server and port are managed by Aleria, so you only provide the Database, User, and Password (or paste an Aleria DB link).
¶ When to use
- You have a pipeline table and want to insert/bulk-load it into a table hosted in Aleria.
- You need fast loads using CSV copy semantics.
- You want simple error handling and batching controls.
Target of this box is to write data into Aleria’s DB (so it becomes immediately available to downstream Aleria apps/AI features). It is not a reader.
¶ Inputs & outputs
- Input: a tabular dataset (the rows you want to write).
- Output: the same rows flow through; optionally a Status column can be added to indicate write result (see Error management).
¶ Quick start (typical insert)
-
Database name – paste the Aleria DB name or a full Aleria DB link/URL.
-
Login/user and Password – supply your Aleria DB credentials.
- Get them from your Aleria admin (Workspace ➜ Databases ➜ Connection / Credentials).
-
Click Inspect database (🔍) to verify connection and list tables.
-
Table Name – enter the target table (must already exist).
-
Operation – keep
insert (CSV Copy)for the fastest load. -
(Optional) Set Write all columns on if you want to write every incoming column; otherwise ensure only target columns are present.
-
Run the pipeline.
Column mapping: the action writes by column name. Make sure incoming column names match the destination table names (case-sensitive rules follow the DB settings).
¶ Parameters
¶ Connection
| Field | What it is |
|---|---|
| Database name (you may paste aleria link here) | The Aleria database identifier, or a full Aleria DB connection link. Host/port are embedded/managed by Aleria. |
| Login/user | Aleria database user. |
| Password | Password for the user. |
| Inspect database | Tests connectivity and lists schemas/tables to help you verify your target. |
¶ Target & operation
| Field | What it is |
|---|---|
| Table Name | Destination table to receive the rows (must exist). |
| Operation | insert (CSV Copy) — bulk insert using high-speed CSV copy. (Other modes may appear in future revisions.) |
| Write all columns | If on, every incoming column is written (must exist on target). If off, provide only the subset present on the target. |
¶ Advanced
| Field | What it is / Guidance |
|---|---|
| BULK operations: number of rows in one go | Chunk size for batching rows before sending. Start with 5k–50k; increase for large, stable loads. |
| Number of “Insert”s per transaction (0 = auto-commit) | Group multiple batches into a single transaction. 0 lets the action auto-commit. For large loads, try 0 or 1–5 depending on rollback needs. |
| Allow “strange” characters in Column’s Names | Permits non-alphanumeric characters (only enable if your schema truly needs it). |
| Error Management — Status Column Name | Name of a column to append/return that carries write status (e.g., Postgre_Status_1). |
| Error Management — In case of Error | Behavior on errors. only abort on critical error is safest for long loads. |
| Write all rows | If on, processes every row, even if some error statuses are reported. Turn off if you prefer a strict fail-fast behavior. |
¶ Credentials — where to get them (Aleria)
- In Aleria UI, open your Workspace / Project.
- Go to Databases ➜ select your database.
- Copy the database name or DB link; grab User and Password (or request them from your admin).
- Paste the DB link/name into Database name and the credentials into Login/user and Password.
Security tip: Prefer dedicated service accounts with least-privilege (INSERT permission on the target table).
¶ Best practices & tips
-
Schema alignment: ensure names and types match; cast in the pipeline if needed.
-
Primary keys & constraints: for pure inserts, unset unique constraints or ensure no duplicates.
-
Performance:
- Use
insert (CSV Copy)for the fastest path. - Start with BULK = 10,000; adjust based on memory/network.
- Keep Inserts per transaction = 0 for simpler recovery, or bump to 2–5 when you need transactional grouping.
- Use
-
Error visibility: set a Status Column Name to trace per-row outcomes in downstream steps.
-
Strange column names: avoid turning this on unless legacy schemas force it—it can reduce portability.
¶ Common pitfalls
- Table does not exist — create it first in Aleria.
- Mismatched columns — rename input fields or select only the matching set.
- Permission denied — user lacks INSERT on target table; ask admin.
- Timeouts on huge loads — reduce BULK size or increase retries (if exposed in your build).
¶ Example
Goal: Load curated customer rows into public.customers_hist.
-
Database:
aleria://my-workspace/my-db -
User:
pipeline_writer/ Password:•••••• -
Table Name:
public.customers_hist -
Operation:
insert (CSV Copy) -
Advanced:
- BULK = 20000
- Inserts per transaction = 0
- Status Column Name = Aleria_Status
- In case of Error = only abort on critical error
-
Run — verify
Aleria_Status = OKon output.
¶ Notes & limitations
- This action targets Aleria environments only; host/port are implicit in the Aleria DB link.
- Current build focuses on insert semantics. If you need merge/upsert or delete behaviors, use dedicated actions when they become available in Aleria.
