|
|
Steve Ikeoka created an issue |
|
Issue Type: |
|
|---|---|
|
Affects Versions: |
2.22.3, 2.23.0 |
|
Assignee: |
|
|
Components: |
CSW, JDBCConfig |
|
Created: |
16/May/23 6:31 PM |
|
Priority: |
|
|
Reporter: |
Medium|
When using JDBC Configuration, CSW GetRecords requests are very slow when the request filter contains both spatial and non-spatial components even when removing the spatial part of the filter would execute very quickly. The CSW module is internally modifying the filter before passing it to the JDBC Configuration catalog in a way that prevents JDBC Configuration from being able to split the supported part of the filter into a database query so it has to load the entire catalog from the database and evaluate the filter in memory. No spatial filter would be very fast: constraint=dc:identifier=‘foo’ Appending a spatial filter makes the request very slow: constraint=dc:identifier=‘foo’ AND INTERSECTS(ows:BoundingBox,POINT(0 0)) |
|
|
|
Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS |
|
|
This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100225-sha1:6805d32) |
|
|
|
