BlueBrain / BlueBrain/nexus

Add the possibility to define the ES document output format

Open
#2,507 0 comments 0 reactions 0 assignees View on GitHub
delta feature
Dominant language
Scala
Stars
301
Forks
76
PR merge metrics
No merged PRs in 30d

Description

In `ElasticSearchView` would be quite useful to control what JSON-LD algorithm is applied in order to generate the final Document that is going to be indexed.

Currently we index each resource as posted by the client (adding the metadata fields as compacted). However, some clients might want to have a degree of uniformity across their data in order to be able to run queries easily.

One proposal could be:

```json
{
"outputAlgorithm": "compacted|expanded|none",
"outputContext": {...}
}
```
the `outputContext` could be optional, using the context of each of the resources otherwise to perform compaction/expansion

This affects, for example: @jonathanlurie @pgetta

Contributor guide

Open the contributing guide

Research direction

Start by locating ElasticSearchView and tracing how posted resources are transformed before indexing. Clarify the supported outputAlgorithm values and optional outputContext behavior; done means indexed documents can consistently use the requested compacted, expanded, or unchanged format.

Written by the indexing model from the issue text.

Assessment

Tech stack
elasticsearch, scala
Domain
search
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.