Azure / Azure/MachineLearningNotebooks

ParallelRunStep output file rows clobber each other

Offen
#1,743 8 Kommentare 2 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Jupyter Notebook
Sterne
4.4k
Forks
2.6k
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

Very recently, a process that had been fine for months is failing at a pandas read_csv step, when we try to import the dataset created from a ParallelRunStep. The issue seems to be that two rows are merged in the output file, and so a row is longer than expected.

We expect 70 columns in our data. When this happens, one row in the file has more than 70. The number varies (we've seen 2 failures, one had 137 columns, one 100).

In the bad row, it's clear that the second row data comes in in the middle of a row. The first field from the next row is squished onto some field in the middle of the previous row. This is like the following (if our dataset had 3 fields)

we expect:
1 blue balloon
2 yellow car
3 red shirt

but we see instead:
1 blue ballo2 yellow car
3 red shirt

In both of our 2 failures so far the row position and specific case differed (no not the same rows each time). But we saw only one bad row per run (and we had very large files).

We can work around by ignoring bad rows when we do the read_csv, but this is definitely an Azure bug.

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.