Uploaded image for project: 'GeoServer'
  1. GEOS-5977

Naming geoserver layer differently from underlying postgis table causes aggregates to be omitted in SQL queries supporting time dimension in GetCapabilities and related operations.


    • Type: Bug
    • Status: Closed
    • Priority: Low
    • Resolution: Fixed
    • Affects Version/s: 2.3.3
    • Fix Version/s: 2.8.4, 2.9-RC1
    • Component/s: PostGIS, WMS
    • Labels:


      Opening issue at request of Justin Deoliveira in geoserver list discussion.

      Naming a layer in Geoserver "Edit Layer" differently from the underlying postgis table (and/or possibly the name of the store) causes aggregate functions such as distinct(), max(), and min() to be omitted from SQL queries supporting GetCapabilities, GetMap, GetFeatureInfo on layers with a time dimension (not sure about elevation dimension).

      This causes a significant delay as the time dimension (I call it timestamp) from every database row appears to be returned for these requests, rather than distinct timestamps for GetCapabilities and max() timestamp for GetMap and GetFeautreInfo. This issue crops up for GetMap and GetFeatureInfo when one defaults to the default time coordinate in a request rather than specifying it as a parameter.

      Extensive log excerpts and discussion are provided in attachments. E-mails are from original discussion started 30 Jul 2013 on geoserver mail list.

      A quick example of the issue, though, is shown below:

      The underlying postgis table is "latest", as is the name of the store.

      If I name the layer "latest" in Geoserver "Edit Layer", I see the following query upon a GetCapabilities:

      12 Aug 16:36:08 DEBUG - CREATE CONNECTION
      12 Aug 16:36:08 DEBUG - SELECT distinct("timestamp") FROM "public"."latest"
      12 Aug 16:36:09 DEBUG

      If I rename the layer in Geoserver to something else ... "latestxxx", while leaving the postgis layer & store as "latest", I see the following query:

      12 Aug 16:37:09 DEBUG - CREATE CONNECTION
      12 Aug 16:37:09 DEBUG - SELECT "timestamp" FROM "public"."latest"
      12 Aug 16:37:16 DEBUG

      So, the distinct() aggregate does seem to be disappearing if the layer name is not the same as the store/table name. Response slows significantly as all timestamps are returned, not just the distinct ones, when compiling the GetCapabilities response.


          Issue links



              • Assignee:
                removed Former user (Inactive)
              • Votes:
                1 Vote for this issue
                3 Start watching this issue


                • Created: