Skip to content

Bad error message when wildcard matches no files with xml-files #1306

@mschoeb

Description

@mschoeb

What did you expect to happen?

Should be the nice exception with line number, good message etc.

How can we reproduce it (as minimally and precisely as possible)?

run xml-files("asdf/*")

Anything else we need to know?

The issue comes from spark .wholeTextFiles, but its a transformation so it doesnt get evalauted until later. What we need to do to fix this is somehow check before if it matches any files. We already do the check

 if (!FileSystemUtil.exists(uri, context.getRumbleRuntimeConfiguration(), getMetadata())) {

and this works for paths like xml-files("asdf"), there it fails in the right way. But if the path contains a wildcard, we accept it in any case.

I think the best solution would be to expand FileSystemUtil.exists to check if any file matches in case it contains a wildcard.

RumbleDB version

1.22.0

OS version

No response

Related Software versions

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions