Feature/csvstream

[quadri00]

csv stream puahed to main for review

[edsonesf]

IMHO, the current implementation does not meet the goal of the class/methods that were defined in the design document.

Blackboard: Team_5_GroupProjectProposal_2025_as_submitted.docx

[edsonesf]

Do you need to push this output file to the repo?
It does not look related or required.

[edsonesf]

Why hard code it?

The stream could process anything, not only this use case.

[edsonesf]

We should not generate a large CSV file here.
The repository already has many sample CSV files at main/src/main/resources/sample-csvs

Check these:

• snakes_count_10000.csv
• hw_25000.csv
• mlb_players.csv

[edsonesf]

Tests are empty

[bogdansharp]

Good for the Start!

I suggest integrating your CsvStream class with the existing CSV library. Its main role is to be a lightweight wrapper around CsvReader and provide a Java Stream<Row> interface to make processing rows easy.

A minimal recommended API could look like this:

public final class CsvStream implements Closeable {

    private CsvStream(CsvReader reader);

    /** Wraps an existing CsvReader into a CsvStream */
    public static CsvStream from(CsvReader reader);

    /** Opens a CSV file with the given configuration */
    public static CsvStream fromPath(Path path, CsvConfig config) throws Exception;

    /** Opens a CSV file with configuration and explicit headers */
    public static CsvStream fromPath(Path path, CsvConfig config, Headers headers) throws Exception;

    /** Returns a Stream of Row objects for lazy processing */
    public Stream<Row> stream();

    /** Closes the underlying CsvReader */
    public void close();
}

How a user would use CsvStream:

Path file = Paths.get("data.csv");
CsvConfig config = CsvConfig.builder().setHasHeader(true).build();

try (CsvStream csvStream = CsvStream.fromPath(file, config)) {
    csvStream.stream()
             .filter(row -> row.get("age").asInt() > 30)
             .forEach(row -> System.out.println(row.get("name")));
}
// CsvStream automatically closes the underlying CsvReader

Key Points for Implementation:

• CsvStream should wrap a CsvReader internally.
• stream() should lazily read rows so you don’t load the entire file into memory.
• close() should release resources from the underlying CsvReader.
• Use try-with-resources when consuming CsvStream to ensure proper cleanup.

[edsonesf]

Working on it, to continue from @quadri00 version and implement @bogdansharp suggestions.

[edsonesf]

Lots of commits too, let me squash it.

[edsonesf]

Local build pass:

mvn test
...
[INFO] Results:
[INFO] 
[INFO] Tests run: 447, Failures: 0, Errors: 0, Skipped: 0
[INFO] 
[INFO] 
[INFO] --- jacoco:0.8.12:report (report) @ csv-data-processor ---
[INFO] Loading execution data file /home/edson/Documents/ATU/SoftwareDevelopment/ATU-SoftDev-Grp5Project/target/jacoco.exec
[INFO] Analyzed bundle 'csv-data-processor' with 50 classes
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  3.083 s
[INFO] Finished at: 2025-12-03T23:34:05Z
[INFO] ------------------------------------------------------------------------