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.

Sign up for GitHub

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

Jump to bottom

Finalize Elastic IndexModel #69

Open
davidblasby opened this issue Nov 18, 2024 · 2 comments
Open

Finalize Elastic IndexModel #69

davidblasby opened this issue Nov 18, 2024 · 2 comments

Comments

@davidblasby
Copy link
Contributor

davidblasby commented Nov 18, 2024 •
edited
Loading

There are some differences between the geonetwork-mircoservices IndexModel and the GN5 IndexModel. Also, some differences with GN4.

These need to be resolved and the GN5 IndexModel finalized.

See #17
@davidblasby davidblasby converted this from a draft issue Nov 18, 2024
This was referenced Nov 18, 2024
Open
Open
@fgravin
Copy link
Member

fgravin commented Nov 22, 2024

To have a great model, a recommendation here would be to use Elasticsearch pipelines to avoid overheads within schema mappings to Elasticsearch.

We would have a core model, within only raw properties, and all computed properties (computed from raw properties) would be in the ES pipelines. This would avoid to duplicate codes in all schemas and will help building a cleaner model IMO.

We use that for geonetwork-ui concerns and it works pretty well 👌

@davidblasby
Copy link
Contributor Author

@fgravin interesting. Could you say more about how you’ve done this? This this something for gn5?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
GeoNetwork 5
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fgravin @davidblasby