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
Often enough, when I am debugging in LP-ETL, I use Textholder to put my debugging data in. This works fine for text-based formats such as RDF , CSV, XML and JSON. It does not work for binary files such as XLSX, even though the use case is the same.
Therefore, a new component, file holder, would be useful. It would allow me to upload a file, and it would store it (probably as hex64binary) in the configuration, the same way TextHolder does for texts.
There is a risk that a user will upload large files, making the pipelines and configurations large, but it is the same risk as with TextHolder where one can also input a large text, making everything slow.
Without such component, I must upload the file either to the LP-ETL server, or somewhere downloadable, which is quite a hassle for simple debugging.
The text was updated successfully, but these errors were encountered:
Often enough, when I am debugging in LP-ETL, I use Textholder to put my debugging data in. This works fine for text-based formats such as RDF , CSV, XML and JSON. It does not work for binary files such as XLSX, even though the use case is the same.
Therefore, a new component, file holder, would be useful. It would allow me to upload a file, and it would store it (probably as hex64binary) in the configuration, the same way TextHolder does for texts.
There is a risk that a user will upload large files, making the pipelines and configurations large, but it is the same risk as with TextHolder where one can also input a large text, making everything slow.
Without such component, I must upload the file either to the LP-ETL server, or somewhere downloadable, which is quite a hassle for simple debugging.
The text was updated successfully, but these errors were encountered: