> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/10.2-data-integration/pdi-transformation-steps-reference-overview/orc-output/options-orc-output-reuse/options-tab-orc-output-reuse.md).
# Options tab
The following options in the **Options** tab define how the ORC output file will be created.
| Field | Description |
| ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Compression** | Specifies which codec is used to compress the ORC output file:
No compression is used (default).
Writes the data blocks using the deflate algorithm, as specified in RFC 1951, and typically implemented using the zlib library.
Writes the data blocks using LZO encoding, which works well for CHAR and VARCHAR columns that store very long character strings.
Using Google's Snappy compression library, writes the data blocks that are followed by the 4-byte, big-endian CRC32 checksum of the uncompressed data in each block.
|
| **Stripe size (MB)** | Defines the stripe size in megabytes. An ORC file has one or more stripes. Each stripe is composed of rows of data, an index of the data, and a footer containing metadata about the stripe’s contents. Large stripe sizes enable efficient reads from HDFS. The default is 64.See for additional information. |
| **Compress size (KB)** | Defines the number of kilobytes in each compression chunk. The default is 256. |
| **Inline Indexes** | If checked, rows are indexed when written for faster filtering and random access on read. |
| **Rows between entries** | Defines the stride size or number of rows between index entries (must be greater than or equal to 1000). The stride size is the block of data that can be skipped by the ORC reader during a read operation based on the indexes. The default is 10000. |
| **Include date in file name** | Adds the system date to the filename with format \`\` (`20181231` for example). |
| **Include time in file name** | Adds the system time to the filename with format `HHmmss` (`235959` for example). |
| **Specify date time format** | Select to specify the date time format using the dropdown list. |
\*\*Important:\*\* Due to licensing constraints, ORC does not ship with LZO compression libraries; these must be manually installed on each node if you want to use LZO compression.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.pentaho.com/pdia-data-integration/10.2-data-integration/pdi-transformation-steps-reference-overview/orc-output/options-orc-output-reuse/options-tab-orc-output-reuse.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.