sdap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Frank Greguska (JIRA)" <>
Subject [jira] [Updated] (SDAP-127) ID should be unique in SOLR schema
Date Tue, 24 Jul 2018 18:11:00 GMT


Frank Greguska updated SDAP-127:
    Component/s: nexus

> ID should be unique in SOLR schema
> ----------------------------------
>                 Key: SDAP-127
>                 URL:
>             Project: Apache Science Data Analytics Platform
>          Issue Type: Improvement
>          Components: nexus
>            Reporter: Frank Greguska
>            Priority: Major
> The "solr_id_s" field is currently the "uniqueKey" for the schema:
> This is fine but a lot of the algorithms depend on the simple "id" field for working
with tiles (the id field is the same as solr_id_s but without the prefix used for document
> If possible, the "id" field should also be marked as unique so that it is impossible
to generate tiles with identical "id"s.
> This problem was found because of SLCP ice shelf data where 2 variables from the same
granule were being ingested. The ID is generated from the granule name and section spec and
an optional 'salt' value. In this case no salt was used (incorrectly) so the tiles were generated
with identical "id"s but no error occurred because they had different dataset names which
caused the "solr_id_s" field to be unique.
> Not sure if it is possible to have more than one unique field in a SOLR schema.

This message was sent by Atlassian JIRA

View raw message