Opened 3 months ago

Closed 5 weeks ago

Last modified 4 weeks ago

#2789 closed enhancement (fixed)

Global max feature query limit in web tier

Reported by: jng Owned by: jng
Priority: low Milestone: 3.1.2
Component: Map Agent Version:
Severity: trivial Keywords:
Cc: External ID:

Description

Add support for a new optional GlobalMaxFeatureQueryLimit? property in webconfig.ini

When set, and greater than 0 it will be the upper limit of any mapagent operation that returns features. Mainly:

  • QUERYMAPFAETURES
  • SELECTFEATURES
  • GETWFSFEATURE

This value will take precedence over any limit specified. For example, if GlobalMaxFeatureQueryLimit?=20 and QUERYMAPFEATURES passed maxFeatures=21, the operation will return at most data for 20 features.

Change History (3)

comment:1 Changed 3 months ago by jng

Summary: Global max feature query limitGlobal max feature query limit in web tier

comment:2 Changed 5 weeks ago by jng

Resolution: fixed
Status: assignedclosed

In 9483:

Implement global max feature query limits in web tier through new webconfig.ini options:

Where specified, they will apply a global maximum limit for that operation, taking precedence over whatever operation-specific limit (eg. maxFeatures) that may be specified.

By default these values are not set, resulting in unbounded results as it currently is.

Fixes #2789

comment:3 Changed 4 weeks ago by jng

In 9489:

Merged revision(s) 9483-9484 from branches/3.1/MgDev:
Implement global max feature query limits in web tier through new webconfig.ini options:

Where specified, they will apply a global maximum limit for that operation, taking precedence over whatever operation-specific limit (eg. maxFeatures) that may be specified.

By default these values are not set, resulting in unbounded results as it currently is.

Fixes #2789
........
#2789: Add missing file
........

Note: See TracTickets for help on using tickets.