Questions, bugs, and contributions

Ask usage questions in GitHub Q&A. Discuss feature ideas in Ideas.

For a bug, open an issue with the package/version, .NET runtime, input format, a minimal sanitized input sample, reader/profile configuration, expected and actual results, and the exception/stack trace. Mention encoding, line endings, headers, and whether the input is compressed or non-seekable when relevant. Do not include credentials or sensitive production records.

For a feature or documentation issue, use a descriptive natural-language title and explain the intended behavior. Repository maintainers use one change-type label: bug, new-feature, or enhancement; docs can be an additional topic label.

See contributing guidance before implementing a change. Include focused validation and documentation with the pull request.

Getting started
Format guides
Arrow input formats
Inspect and prepare input
Reading data
Partitioning and indexing
Configuration
Validation and diagnostics
Performance
Integrations