Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improvements to WFS indexing: dashboard and map widget #2573

Merged
merged 5 commits into from
Feb 23, 2018

Conversation

jahow
Copy link
Member

@jahow jahow commented Feb 21, 2018

This PR adds a little polish to the WFS indexing system:

  • a list of ongoing indexing jobs is now available in admin/dashboard
    This is still very raw data, taken directly from the ElasticSearch index. We will have to make a more robust system in the future with start/stop controls and finer status (hint @fxprunayre).
    image

  • fix for WFS indexing not working #2498

  • bonus: a functional heatmap (backported from a customer fork):
    image

Still a lot more to do on this topic, both on the frontend and backend, but hopefully this PR will make the system a bit more suitable for basic use.

@jahow
Copy link
Member Author

jahow commented Feb 21, 2018

@fgravin can you please review this PR? thanks

Copy link
Member

@fgravin fgravin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for contribution

@fgravin fgravin merged commit 496da0d into geonetwork:3.4.x Feb 23, 2018
@fxprunayre fxprunayre added this to the 3.4.2 milestone Apr 30, 2018
@fxprunayre
Copy link
Member

Would it make sense to move that to the harvesting section as this is about harvesting remote content ?

@jahow
Copy link
Member Author

jahow commented May 7, 2018

Would it make sense to move that to the harvesting section as this is about harvesting remote content ?

Why not, the reason why I didn't do that is because to me this is more about indexing than harvesting (i.e. replicating a dataset).

Also, as I understand it, the Status interface is generally used for monitoring activities (regular visits to make sure everything works as intended), whereas the Harvesting interface is more of a setup one, where the user might go a few times to adjust settings and then leave it alone.

At any rate, moving this view should be virtually effortless.

@jahow jahow deleted the wfs-indexing-dashboard branch December 4, 2018 12:47
@josegar74 josegar74 mentioned this pull request Mar 11, 2019
51 tasks
@etorresmoya
Copy link

etorresmoya commented Oct 22, 2020

Good day, I am using Geonetwork 3.10.4 and elasticsearch 7.9.2 and I have the same problem, I can't use the wfs filter, i can fixed the remote index error in dashboard status "Remote index module is not installed in your catalogue installation. Add 'es' to the spring.profiles.active in WEB-INF/web.xml to activate it", but i can't use the wfs filter. I am not a developer, i am a single user, but this situation is too difficult, please I need some help. I used tools in dashboard "(beta) remote index and i received this error "IOException and i receive this error:

Error during removal. Errors is '"Incorrect HTTP method for uri [/_delete_by_query] and method [POST], allowed: [GET, HEAD, DELETE, PUT]"'.".

Please i need some orientation.

Best regards.

Enrique T
error remote index wfs geontework 3 10 4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants