WFS indexing / Align with sextant #3205
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cmangeat
reviewed
Oct 29, 2018
...harvester/src/main/java/org/fao/geonet/harvester/wfsfeatures/worker/EsWFSFeatureIndexer.java
Show resolved
Hide resolved
...harvester/src/main/java/org/fao/geonet/harvester/wfsfeatures/worker/EsWFSFeatureIndexer.java
Show resolved
Hide resolved
...harvester/src/main/java/org/fao/geonet/harvester/wfsfeatures/worker/EsWFSFeatureIndexer.java
Outdated
Show resolved
Hide resolved
|
I'll take a look ASAP. Basically we want the files to be the same as in sextant, which is where most of the WFS filter/indexing work was done, right? |
Yep. |
fxprunayre
changed the title
workarounds refine error messaging when report saved do not go further when failure at es report initialisation time infer wfs version from geotools sources rather than from parameters default to GML3 for datasources, not taken into account when wfs 1.0.0 leverage wfs datasources timeout to 3000s
… of the default 4 applies by GeometryJSON) and optionnaly apply a precision model to reduce the geometry complexity and avoid to build invalid geometry when removing decimals. This may create a simplified geometry above the equivalent displayed in WMS. Set those values depending on the WFS harvested.
…operty file on startup. Not filtered on build.
…S 6.4.x needs to be URL encoded.
This was introduced by https://github.com/camptocamp/sextant-geonetwork/commit/e5ede11b419e4f0fcc0bf8c4e420aabb9dd8ff60 featureAttributeToDocumentFieldNames was shared in a EsWFSFeatureIndexer singleton. Changing scope to prototype to have one instance on each harvest.
…d to (probably fixed in?) Sextant.
* Add support for index type * Limit proxy to the index we are using (and not all the ES cluster) * WFS indexing / Add support for CDATA
fxprunayre
force-pushed
the
feature/wfsharvester/align-with-sextant
branch
from
1fbbd5c
to
d94d719
Compare
Filtering is done by adding an 'include' criteria on the bucket aggregation for the facet.
+ fix to labels for fields only in app profile
jahow
approved these changes
Nov 22, 2018
fxprunayre
added a commit
that referenced
this pull request
Dec 17, 2018
Related to #3205 which now encode URL and feature type name to support ES 6.4+ and to point to the correct index containing features (and not to the ES cluster root only).
fxprunayre
added a commit
that referenced
this pull request
Dec 17, 2018
Related to #3205 which now encode URL and feature type name to support ES 6.4+ and to point to the correct index containing features (and not to the ES cluster root only).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes:
Those changes are backported from Ifremer Sextant.
Future tasks: