korowa opened a new pull request, #13677:
URL: https://github.com/apache/datafusion/pull/13677
## Which issue does this PR close?
<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases. You can
link an issue to this PR using the GitHub syntax. For example `Closes #123`
indicates that this PR will close issue #123.
-->
Closes #12328.
## Rationale for this change
<!--
Why are you proposing this change? If this is already explained clearly in
the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand your
changes and offer better suggestions for fixes.
-->
At this moment DF is unable to properly identify ranges after file
repartitioning for CSV files with custom line terminator (bound calculation
function considers only `\n` as a line separating character).
Test failures are caused by `target_partitions = 4` (default for Datafusion
sqllogictests engine/runner) and `set repartition_file_min_size = 1` in
`csv_files.slt` executed before failing test -- these two settings trigger scan
repartitioning, which is not supported.
## What changes are included in this PR?
<!--
There is no need to duplicate the description in the issue here but it is
sometimes worth providing a summary of the individual changes in this PR.
-->
File scan repartitioning functions used for plain-text files (CSV and NDJson
-- though json reader don't have line separator option in its API) now aware of
line terminator character.
## Are these changes tested?
<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code
If tests are not included in your PR, please explain why (for example, are
they covered by existing tests)?
-->
Sqllogictests for single-thread reading and repartitioned reading of CSV
with custom line separator.
## Are there any user-facing changes?
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
No.
<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
