kz930 opened a new issue, #8415: URL: https://github.com/apache/texera/issues/8415
### Task Summary Nine source operators implement `StandaloneCodeGenerator`, so an exported script starts from the same data the workflow did rather than from a variable the reader has to fill in: the CSV family, JSON Lines, Arrow, plain text, and the two that read a file named at run time. A source is the one place where the script cannot simply repeat what the operator does. The engine resolves a dataset through Texera's storage and hands the operator a URI; a script has no such resolver, so it reads the file from its own directory under the name that URI ended with. That is what makes an exported script portable, and it is equally its one precondition: the data has to sit beside the script. The name is taken from the last path segment rather than by parsing the whole string as a URI, because the resolver percent-encodes the file-relative parts but leaves the repository and version names as the user typed them, and a dataset version with a space in its name makes `new URI` throw before any code is generated. Two sources are reported as unverifiable rather than exported blind. File Scan takes its filenames from an input port at run time, which a source harness has nothing to feed. URL Fetcher reads a live URL, so two runs are not required to agree and a comparison would only measure the network. Ninth of the twenty-one steps listed in #8325. It needs #8327 for the trait. -- 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]
