[Geoserver-devel] [JIRA] (GEOS-9165) App-schema indexes makes query without correct maxFeatures number on "rows" parameter to Apache Solr

GeoServer GeoServer Developer
1

Fernando Miño created an issue

GeoServer / BugGEOS-9165

App-schema indexes makes query without correct maxFeatures number on “rows” parameter to Apache Solr

Issue Type:

BugBug

Assignee:

Unassigned

Components:

Application schema

Created:

25/Mar/19 2:37 AM

Priority:

MediumMedium

Reporter:

Fernando Miño

During the getting IDs roundtrip, appschema-indexes makes a Solr query with a max rows (rows parameter) of 1000 as default instead the correct one (1 for example).

Using a WFS query with startIndex and count parameters as:

<wfs:GetFeature service="WFS" version="2.0.0" startIndex="1" count="1"
  xmlns:st="http://www.stations.org/1.0"
  xmlns:wfs="http://www.opengis.net/wfs/2.0"
  xmlns:fes="http://www.opengis.net/fes/2.0"
  xmlns:gml="http://www.opengis.net/gml/3.2">
  <wfs:Query typeNames="st:Station" srsName="EPSG:4326">
    <fes:Filter>
      <fes:PropertyIsLike wildCard="*" singleChar="." escapeChar="\">
        <fes:ValueReference>st:Station/st:observation/st:Observation/st:description</fes:ValueReference>
        <fes:Literal>*wind*</fes:Literal>
      </fes:PropertyIsLike>
    </fes:Filter>
  </wfs:Query>
</wfs:GetFeature>

Appschema-indexes builds a query using rows=1000 instead 1 as seen on logs:

Apache solr logs:

2019-03-23 21:00:24.064 INFO  (qtp225493257-17) [   x:meteo2] o.a.s.c.S.Request [meteo2]  webapp=/solr path=/select params={q=*:*&omitHeader=true&group.limit=0&start=1&sort=id+asc&fq=observation_description:/.{1,1}*wind.{1,1}*/+&rows=1000&wt=javabin&version=2&group.field=station_id&group=true} hits=3 status=0 QTime=2

On Geoserver side an integration test for this is required.

Add Comment

Add Comment

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#100099-sha1:9206a61)

Atlassian logo