While fixing GEOT-6310 <https://osgeo-org.atlassian.net/projects/GEOT/issues/GEOT-6310> over the last few weeks, I added a "fix" for this issue (PR-2453 <https://github.com/geotools/geotools/pull/2453>) which basically stops the WFS 2.0.0 client setting MaxFilter as it is unable to handle the fact that it can't process some (all?) filters on the server - I suspect this is in fact a common bug across all the ContentStore based DataStores but I'm unwilling to go there at present.
This also led me to a bunch of other issues in the wfs-ng datastore which make chunks of it essentially unusable for any large remote dataset. If it wasn't for the fact GeoServer builds on top of it I would propose kicking it out of the build to discourage people from using it. I'll look at logging some improvements against it but without funding I doubt I will have the inclination to look at them. If any one else would like to take a look at the problem (or at least check it exists please jump in) - If not I may try to look to see if it is an issue next weekend. Cheers Ian -- Ian Turton
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
