Hi Johannes,

thank you for your hint. I simply looked in a branch that does not contain the 
image categorize component [1]. Sorry for this misinformation. I will correct 
this on the Confluence page.
I will also have a look at the component. And of course, the properties 
"labels" and "pageSum" are not obsolete in this context.

Regards,
Daniel

[1] 
https://github.com/apache/incubator-streampipes/tree/STREAMPIPES-319/ui/src/app/core-ui/image
 

-----Ursprüngliche Nachricht-----
Von: Johannes Tex <t...@apache.org> 
Gesendet: Dienstag, 10. August 2021 20:09
An: dev@streampipes.apache.org
Betreff: Re: Harmonization of Data Lake Query Result

Hi Daniel,

the attributes "labels" and "pageSum", which you call obsolete in your 
proposals , are used in [1]. Maybe that is also obsolete ;)

Johnnaes

[1] 
https://github.com/apache/incubator-streampipes/blob/master/ui/src/app/core-ui/image/image-categorize/image-categorize.component.ts

On 2021/08/10 11:20:58, Daniel Ebi <e...@fzi.de> wrote: 
> Hi all,
> 
> As part of the refactoring and integration of the Data Lake REST API into the 
> Data Explorer, it has turned out that it makes sense to harmonize the return 
> type of Data Lake queries first. Consequently, I have already drafted two 
> proposals for the alignment of DataResult, GroupedDataResult and PageResult 
> classes.
> I've created a new page in Confluence for these drafts, so that we can 
> discuss further ideas (both conceptually and in terms of naming) there in the 
> comments [1].
> 
> The page is thematically divided into two parts. First, I have put together a 
> brief overview of the status quo of the return type of Data Lake queries. 
> Then follows a part with the two proposals, which differ only slightly from 
> each other.
> 
> It would be great if you leave me feedback and your ideas for adjustments 
> there in the comments, so that we can discuss the ideas together before 
> implementation.
> 
> Thanks and regards,
> Daniel
> 
> 
> [1] 
> https://cwiki.apache.org/confluence/display/STREAMPIPES/Harmonization+of+Data+Lake+Query+Result
> 
> 

Reply via email to