Filter limiting code should check what filters are active before giving up
because the filters are too many
-----------------------------------------------------------------------------------------------------------
Key: GEOT-1525
URL: http://jira.codehaus.org/browse/GEOT-1525
Project: GeoTools
Issue Type: Improvement
Components: core render
Affects Versions: 2.5-M0, 2.4-RC0
Reporter: Andrea Aime
Assignee: Jesse Eichar
Priority: Critical
Fix For: 2.4-RC1, 2.5-M1
The streaming renderer tries to combine filters in order to avoid multiple
queries on the database. This is done in processRuleForQuery.
The logic is unfortunately too simplistic, in that it considers the amount of
filters available without checking if a filter is active or not at the current
scale level.
This may result in major performance slowdowns in maps that have many scale
related filters like road network ones (just like the one we're using
on sigma.openplans.org, for example), because it would mean all of the data
would be loaded instead of just the data we need, especially in zoomed
out renderings where most of the stuff is hidden.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
