You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@streampipes.apache.org by GitBox <gi...@apache.org> on 2023/02/19 20:31:44 UTC

[GitHub] [streampipes] bossenti created a discussion: Intention of `maximumAmountOfResults` for data lake measurement API

GitHub user bossenti created a discussion: Intention of `maximumAmountOfResults` for data lake measurement API

What's the intention behind the `maximumAmountOfResults` query parameter for data lake measurements?
There is already the parameter `limit` which allows me to restrict the number of returned results.
Contrastively, `maximumAmountOfResults` simply returns `TOO_MUCH_DATA` when there are more data records then the specified amount. 

GitHub link: https://github.com/apache/streampipes/discussions/1318

----
This is an automatically sent email for dev@streampipes.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@streampipes.apache.org


[GitHub] [streampipes] tenthe added a comment to the discussion: Intention of `maximumAmountOfResults` for data lake measurement API

Posted by GitBox <gi...@apache.org>.
GitHub user tenthe added a comment to the discussion: Intention of `maximumAmountOfResults` for data lake measurement API

This is set by the client. (e.g. for data explorer widgets in `BaseDataExplorerWidgetDirective.TOO_MUCH_DATA_PARAMETER`)

GitHub link: https://github.com/apache/streampipes/discussions/1318#discussioncomment-5118738

----
This is an automatically sent email for dev@streampipes.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@streampipes.apache.org


[GitHub] [streampipes] bossenti added a comment to the discussion: Intention of `maximumAmountOfResults` for data lake measurement API

Posted by GitBox <gi...@apache.org>.
GitHub user bossenti added a comment to the discussion: Intention of `maximumAmountOfResults` for data lake measurement API

But where is `maximumAmountOfResults` set? 
It isn't done by the user, is it? 

GitHub link: https://github.com/apache/streampipes/discussions/1318#discussioncomment-5079470

----
This is an automatically sent email for dev@streampipes.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@streampipes.apache.org


[GitHub] [streampipes] tenthe added a comment to the discussion: Intention of `maximumAmountOfResults` for data lake measurement API

Posted by GitBox <gi...@apache.org>.
GitHub user tenthe added a comment to the discussion: Intention of `maximumAmountOfResults` for data lake measurement API

Hi @bossenti,
this is a good question and in fact this is not described very clearly.

The limit can be set by the user to retrieve only a certain amount of data:
![grafik](https://user-images.githubusercontent.com/5279561/220680842-3057c401-4b48-4193-b4a9-79da913eb08e.png)

With the parameter `maximumAmountOfResults` you can make sure that not too much data is loaded into the browser.
Should this be the case, the user will receive a warning message.


GitHub link: https://github.com/apache/streampipes/discussions/1318#discussioncomment-5078808

----
This is an automatically sent email for dev@streampipes.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@streampipes.apache.org


[GitHub] [streampipes] tenthe edited a comment on the discussion: Intention of `maximumAmountOfResults` for data lake measurement API

Posted by GitBox <gi...@apache.org>.
GitHub user tenthe edited a comment on the discussion: Intention of `maximumAmountOfResults` for data lake measurement API

This is set by the client. (e.g. for data explorer widgets in `BaseDataExplorerWidgetDirective.TOO_MUCH_DATA_PARAMETER`)
The main idea was that a client can decide how much data it can handle.

GitHub link: https://github.com/apache/streampipes/discussions/1318#discussioncomment-5118738

----
This is an automatically sent email for dev@streampipes.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@streampipes.apache.org