jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Phillips (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-687) Configurable API/Provider Default Page Size
Date Tue, 02 Sep 2014 18:45:20 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118512#comment-14118512

Andrew Phillips commented on JCLOUDS-687:

> Why are we duplicating service side logic (that will vary from service to service and
deployment to > deployment) in the clients?

Agree very much with this sentiment. If we are already providing client-side defaults and
are doing this inconsistently, I definitely see the possibility for improving that.

If, on the other hand, we're here looking to expose functionality (i.e. the ability to set
a default page size) that is only supported by some APIs, I would rather we handle this as
we do most other API-specific options and make this one of the parameters you can pass to
an {{*Options}} class.

If we need default for the overloaded versions of those calls that *don't* take an {{*Options}}
parameter, I'm open for any of the suggested solutions, assuming we feel we indeed have a
problem and a need here.

I'd agree with [~everett-toews] that trying to choose a *global* default that works across
API calls that may have completely different cost profiles sounds tricky, so would probably
lean towards a configurable per-API or even per-call default here.

Any data we have indicating that the current situation is actually a problem would be very
useful, though.

> Configurable API/Provider Default Page Size
> -------------------------------------------
>                 Key: JCLOUDS-687
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-687
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-core
>    Affects Versions: 1.6.0, 1.7.0, 1.8.0
>            Reporter: Jeremy Daggett
>            Assignee: Jeremy Daggett
>            Priority: Minor
>              Labels: jclouds, openstack
>             Fix For: 2.0.0
> Each OpenStack API has a default page size that can be returned by the service. The page
sizes differ between APIs and there should be a way to reflect this in API/provider configuration.
The page size is typically used in the list/get related operations.
> The opportunity arises to expand this to all APIs that have a default page size by introducing
a new constant "PROPERTY_PAGE_SIZE" or "PROPERTY_DEFAULT_PAGE_SIZE" to the {{org.jclouds.Constants}}

This message was sent by Atlassian JIRA

View raw message