You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
A file scan extracting an archive cannot also include the filename #8598
A File Scan with Extract on, Include Filename on, and any attribute type that reads the file line by line cannot run. It fails building its first tuple.
The two halves disagree about how many fields a row has. FileScanSourceOpDesc.sourceSchema prepends a filename column whenever Include Filename is set, so the schema is two columns wide. FileScanUtils.createTuplesFromFile only carries the entry's name in its single-value branch: the line-by-line branch emits the value alone, whatever the flag says. Enforcing a one-field tuple against a two-column schema throws.
Include Filename is only offered when Extract is on, so every configuration that reaches this combination is one the panel invites.
Expected: either the line-by-line branch carries the entry name it was asked for, or the schema stops declaring a column the rows will not hold.
How to reproduce?
Build a zip holding one text file, point a File Scan at it with extract and outputFileName both true and the attribute type left at string, and drain FileScanSourceOpExec. The schema reads filename, line; the first tuple carries one field.
SCHEMA = Schema[Attribute[name=filename, type=string], Attribute[name=line, type=string]]
ENFORCED = Failure(org.apache.texera.amber.core.tuple.TupleBuildingException: Tuple does not have the same number of attributes as schema. Missing attributes are List(Attribute[name=line, type=string]))
Activity
fix(operator): name the file each line came from when a file scan was…
feat(workflow-operator): export the line sources and the URL fetcher …