Skip to content

Conversation

carenini
Copy link

…instead of reading them from file or from remote url.

RecordsFactory can accept a Map<named_stream,InputStream>, where named_stream has the format "label://sourcename" and match with the source value in the mapping file.

This way the RML mapper works accepting a mapping file plus a map of named inputs, and can work with in-memory data instead of fetching from pre-defined file/url locations.

…instead of reading them from file or from remote url.

RecordsFactory can accept a Map<named_stream,InputStream>, where named_stream has the format "label://sourcename" and match with the source value in the mapping file.
@pheyvaer
Copy link
Collaborator

pheyvaer commented Jul 2, 2019

Hi @carenini

We understand the need to support InputStreams directly, but we advice against encoding that information directly in rml:source with something like label://sourcename, because the semantics are limited. I know that we also use rml:source for local files and remote files, but we are also looking into improving the description in those cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants