Hello, Tim, You are right. We encode some chars of the image path location when we save the image in the Datalake [1]. This was necessary that the can images via an http route [2].
I think the easiest way would be to change the encoding. Maybe we should encode with '%2F', this is the encoding for slashes. But I am not sure if we can still access the images with [2]. Do you have another idea? The best solution would be a solution where the encoding can be removed. Johannes [1] https://github.com/apache/incubator-streampipes-extensions/blob/dev/streampipes-sinks-internal-jvm/src/main/java/org/apache/streampipes/sinks/internal/jvm/datalake/DataLake.java [2] https://github.com/apache/incubator-streampipes/blob/dev/streampipes-rest/src/main/java/org/apache/streampipes/rest/impl/datalake/DataLakeResourceV3.java On 2020/11/24 14:24:21, udeho <[email protected]> wrote: > Hi all, > > For a small object detection use case I have stored some images in the > internal data lake to label them with the labeling tool. > I discovered that the use of underscores in the data lake identifier prevents > the user from accessing the images later in the data explorer and the > labeling tool. > As far as I can see, the underscore is already used as a delimiter in the > http-request, which leads to a conflict if the identifier also contains an > underscore. > > Best regards, > Tim > >
