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

Restricting security on layers breaks aggregate visitor optimizations in JDBC stores

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Medium
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.8.4, 2.9-RC1
    • Component/s: Main, WPS
    • Labels:
      None

      Description

      Normally processes such as PagedUnique and Aggregate run as optimized sql statements, but applying security restrictions on the layers makes them fall back on data loading and in memory aggregatation insetad.

      This is due to DecoratingFeatureCollection not delegating down the visit method (which is the right decision) and subclasses not taking measures to check if the visitor can be passed down, or not.

      https://github.com/geoserver/geoserver/blob/master/src/main/src/main/java/org/geoserver/security/decorators/SecuredSimpleFeatureCollection.java is one of those, but retyping (used in renames) and reprojecting/forcecrs collections are also causing the problem.

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                aaime Andrea Aime
                Reporter:
                aaime Andrea Aime
              • Votes:
                1 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: