Reject negative ignore_rows and ignore_columns in CSVDocumentCleaner

[Premvkmishra]

Related Issues

• fixes CSVDocumentCleaner silently discards data for negative ignore counts #13074

Proposed Changes:

In CSVDocumentCleaner.__init__, negative values for ignore_rows or ignore_columns were stored unvalidated. In _clean_df, pandas iloc[ignore_rows:, ignore_columns:] treated negative integers as offsets from the end of the DataFrame, leading to silent data loss without restoring ignored sections.

• Added validation in CSVDocumentCleaner.__init__ to raise a ValueError if ignore_rows < 0 or ignore_columns < 0, matching the style of CSVDocumentSplitter and DocumentSplitter.
• Updated :raises ValueError: entry in the component __init__ docstring and updated parameter descriptions in docs-website/docs/pipeline-components/preprocessors/csvdocumentcleaner.mdx.
• Created a reno release note with fixes and upgrade sections.

How did you test it?

• Added unit tests (test_negative_ignore_rows_raises, test_negative_ignore_columns_raises, and test_negative_ignore_values_raise_from_dict) in test/components/preprocessors/test_csv_document_cleaner.py.
• Ran unit tests via hatch run test:unit test/components/preprocessors/test_csv_document_cleaner.py (24 passed).
• Executed a mutation check to confirm the new tests fail when validation is omitted and pass when restored.
• Verified hatch run test:types (mypy) and hatch run fmt (ruff).

Notes for the reviewer

• Validation is performed strictly in __init__ before attribute assignment.
• Zero (0) and positive values behave unchanged.

Checklist

• I have read the contributors guidelines and the code of conduct.
• I have updated the related issue with new insights and changes.
• I have added unit tests and updated the docstrings.
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test: and added ! in case the PR includes breaking changes.
• I have documented my code.
• I have added a release note file, following the contributors guidelines.
• I have run pre-commit hooks and fixed any issue.

[vercel]

@Premvkmishra is attempting to deploy a commit to the deepset Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.

[HaystackBot]

Hi @Premvkmishra, thanks a lot for your contribution! 🙏

We noticed that the Contributor License Agreement (CLA) check (license/cla) hasn't passed yet, so we've temporarily moved this PR to draft and paused the review assignment.

To get your PR reviewed, please sign the CLA via the link in the license/cla check below (or in the CLA bot comment). As soon as the check turns green, this PR will automatically be marked ready for review again and a reviewer will be re-assigned.

[HaystackBot]

Hi @Premvkmishra, just a friendly reminder: this PR is still in draft because the Contributor License Agreement (CLA) hasn't been signed yet. We'd love to review your contribution! Please sign the CLA via the link in the license/cla check, and this PR will automatically be marked ready for review.

[HaystackBot]

Thanks for signing the CLA, @Premvkmishra! 🎉 This PR is now ready for review again and the reviewer has been re-assigned.