Skip to main content

Output

Save data from your workflow to files.

Sockets

SocketDirectionDescription
inputInputData to save

The Output tool has no output sockets - it's a terminal node in the workflow.

Supported Formats

CSV

Comma-separated values and other delimited text files.

Writing Modes:

ModeDescriptionBest For
SinkStreaming write, memory efficientLarge datasets
WriteCollects all data first, then writesWhen you need specific write options

CSV Options:

OptionDefaultDescription
Destination(required)Path for the output file
Separator,Field delimiter
Include HeadertrueWrite column names as first row
Quote Character"Character used to quote fields
Quote StylenecessaryWhen to quote fields
Line Terminator\nEnd-of-line character(s)
Null Value(empty)String to represent null values
Date Format(ISO)Format for date columns
Datetime Format(ISO)Format for datetime columns
Float Precision(full)Decimal places for floats

Parquet

Columnar binary format, efficient for analytics.

Writing Modes:

ModeDescriptionBest For
SinkStreaming writeLarge datasets
WriteCollects all data firstWhen you need specific write options

Parquet Options:

OptionDefaultDescription
Destination(required)Path for the output file
CompressionzstdCompression algorithm (zstd, snappy, lz4, gzip, none)
Compression Level(default)Compression level (algorithm-specific)
Row Group Size(default)Rows per row group
StatisticstrueWrite column statistics

IPC / Arrow

Apache Arrow's native binary format (.arrow, .ipc, .feather). Fastest format for read/write operations.

Writing Modes:

ModeDescriptionBest For
SinkStreaming writeLarge datasets, memory efficiency
WriteCollects all data firstSmall datasets

IPC Options:

OptionDefaultDescription
Destination(required)Path for the output file (.arrow, .ipc, or .feather)
CompressionuncompressedCompression (uncompressed, lz4, or zstd)
When to Use IPC/Arrow
  • Intermediate files: Use IPC for temporary data between pipeline stages
  • Cross-application sharing: IPC works with DuckDB, Spark, R, Julia, and other Arrow-compatible tools
  • Maximum speed: IPC has the fastest read/write performance of any format
  • Memory efficiency: Files can be memory-mapped for efficient access

Excel

Microsoft Excel spreadsheet files (.xlsx).

Writing Mode:

Excel only supports eager writing (data is collected before writing). There is no streaming sink support.

Excel Options:

OptionDefaultDescription
Destination(required)Path for the output file (.xlsx)
WorksheetSheet1Name of the worksheet to create
Table Name(empty)Optional name for the Excel table object
Table StyleTable Style Medium 4Excel table style (e.g., "Table Style Medium 9")
Include HeadertrueWrite column names as header row
AutofiltertrueEnable autofilter dropdown in header
AutofitfalseAuto-calculate column widths to fit content
Hide GridlinesfalseHide worksheet gridlines
Float Precision3Decimal places for float numbers
Sheet Zoom100%Zoom level (10-400%)
Freeze Panes(none)Cell position to freeze (e.g., "A2" freezes top row)
Excel Table Styles

Excel table styles provide professional formatting. Popular options include:

  • Light styles (1-21): Subtle, minimalist
  • Medium styles (1-28): Balanced, good for most uses
  • Dark styles (1-11): High contrast, bold headers
  • None: Plain data without table formatting

You can also enter any custom Excel table style name. See the full visual reference below.

Click to view all Excel table styles

Excel Table Styles Reference

Avro

Apache Avro binary format (.avro). Row-based format for big data ecosystems.

Writing Mode:

Avro only supports eager writing (data is collected before writing). There is no streaming sink support.

Avro Options:

OptionDefaultDescription
Destination(required)Path for the output file (.avro)
CompressionuncompressedCompression (uncompressed, snappy, or deflate)
Schema Name(empty)Optional name for the Avro schema
Avro Use Cases

Use Avro when:

  • Integrating with Hadoop, Kafka, or Spark pipelines
  • Schema evolution is important for your data workflow
  • Interoperability with Java/JVM ecosystems is required

For maximum performance within Sigilweaver, prefer IPC/Arrow or Parquet.

Configuration

  1. Add an Output tool to the canvas
  2. Connect an input wire from an upstream tool
  3. Select the output format (CSV, Excel, Parquet, IPC/Arrow, JSON, or Avro)
  4. Choose the destination path
  5. Configure format-specific options as needed

Examples

Saving to CSV

  1. Wire data into the Output tool
  2. Select "CSV" as the output format
  3. Enter the destination file path (e.g., /path/to/output.csv)
  4. Adjust options like separator or header as needed

Saving to Parquet

  1. Wire data into the Output tool
  2. Select "Parquet" as the output format
  3. Enter the destination file path (e.g., /path/to/output.parquet)
  4. Choose compression (zstd recommended for balance of speed and size)

Saving to IPC/Arrow

  1. Wire data into the Output tool
  2. Select "IPC / Arrow" as the output format
  3. Enter the destination file path (e.g., /path/to/output.arrow)
  4. Choose compression if needed (uncompressed is fastest, zstd for smaller files)

Saving to Excel

  1. Wire data into the Output tool
  2. Select "Excel" as the output format
  3. Enter the destination file path (e.g., /path/to/output.xlsx)
  4. Optionally configure worksheet name, table styling, and formatting options
  5. Use freeze panes to keep headers visible when scrolling

Saving to Avro

  1. Wire data into the Output tool
  2. Select "Avro" as the output format
  3. Enter the destination file path (e.g., /path/to/output.avro)
  4. Choose compression (uncompressed for speed, snappy or deflate for smaller files)

Notes

  • Destination directories are created automatically if they don't exist
  • Sink mode is recommended for large datasets to minimize memory usage (CSV, Parquet, IPC, JSON/NDJSON)
  • Excel and Avro do not support streaming - data is collected before writing
  • IPC/Arrow is the fastest format - use it when speed is critical
  • Excel files are best for business reporting and sharing with non-technical users
  • Overwriting: Existing files at the destination path will be overwritten
  • Execution: Output tools only write files when the workflow is executed (not during preview)