GetLog does not respect maxFeatures

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.6.0-beta3
  • Fix Version/s: 1.6.0-beta4
  • Component/s: Versioning
  • Labels:
    None

Issue Links

depends upon

Bug - A problem which impairs or prevents the functions of the product. GEOT-1519 GetLog needs a way to limit the number of returned log rows

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Improvement - An improvement or enhancement to an existing feature or task. GEOT-1524 Make the log order is dependent on the revision order

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is superceded by

Improvement - An improvement or enhancement to an existing feature or task. GEOS-1416 Implement order in GetLog using toFeatureVersion and fromFeatureVersion order

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrea Aime added a comment -

The issue is a bit more convoluted that the title states. GetLog does not have a maxFeatures attribute at all

Show
Andrea Aime added a comment - The issue is a bit more convoluted that the title states. GetLog does not have a maxFeatures attribute at all
Hide
Permalink
Andrea Aime added a comment -

This means the schema has to be changed, then the model re-generated (with the correct version of EMF, the same used generating the old bindings, which is 2.2.1 whilst Eclipse 3.3 ships with 2.3), then the binding fixed, then the VersioningFeatureStore interface must be changed as well because there is no place where a maxFeatures can be specified

Show
Andrea Aime added a comment - This means the schema has to be changed, then the model re-generated (with the correct version of EMF, the same used generating the old bindings, which is 2.2.1 whilst Eclipse 3.3 ships with 2.3), then the binding fixed, then the VersioningFeatureStore interface must be changed as well because there is no place where a maxFeatures can be specified
Hide
Permalink
Andrea Aime added a comment -

Committed a first version that supports maxFeatures. Keeping it open because I'm not sure I've full captured Tim needs.

Show
Andrea Aime added a comment - Committed a first version that supports maxFeatures. Keeping it open because I'm not sure I've full captured Tim needs.
Hide
Permalink
Chris Holmes added a comment -

Geos-1416 now holds tracks the rest of the client side needs.

Show
Chris Holmes added a comment - Geos-1416 now holds tracks the rest of the client side needs.

People

  • Assignee:
    Andrea Aime
    Reporter:
    Andrea Aime
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: