Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • data-discovery data-discovery
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 26
    • Issues 26
    • List
    • Boards
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

Un arrêt de service aura lieu le lundi 27 mars de 17h à 21h pour maintenance.
Il ne sera plus possible d’utiliser forgemia ni d’accéder aux dépôts (git, container, packages…) pendant cette période.

  • urgi-is
  • data-discoverydata-discovery
  • Issues
  • #83
Closed
Open
Issue created Mar 04, 2022 by Exbrayat Cédric@cedricDeveloper

brc4env indexing

Currently, when starting the backend for brc4env, the application expects Elastic Search to have an index named brc4env-dev-.... But when trying to index the data with

docker run -t --volume $(pwd)/data:/opt/data/ --volume /tmp/bulk:/tmp/bulk/ --network=container:elasticsearch registry.forgemia.inra.fr/urgi-is/docker-rare/data-discovery-loader:latest -host elasticsearch -app brc4env -env dev

then the indexing fails because there is no data/brc4env.

Is it normal? Maybe brc4env uses the same data as rare?

In that case, maybe the spring property for the brc4env ES index should be rare-dev and not brc4env-dev? https://forgemia.inra.fr/urgi-is/data-discovery/-/blob/story/faidare-fusion/backend/src/main/resources/application.yml#L109

Assignee
Assign to
Time tracking