Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
dotstatsuite-core-data-access
dotstatsuite-core-data-access
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 12
    • Issues 12
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 3
    • Merge requests 3
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • SIS-CC
  • Stat Suite
  • dotstatsuite-core-data-accessdotstatsuite-core-data-access
  • Issues
  • #40

Closed
Open
Created Sep 05, 2019 by jean-baptiste nonin@j3an-baptisteOwner

[NSI data plugin] Internal error when invalid dimension code provided in query filter

En error occurs in DimPredicate when an inavlid code is passed in the filter and Internal Error is displayed. This occurs when only invalid code is provided, but also happens when any of the codes are invalid (see the exaples below).

RI implementation ignores the invalid codes if there are at least one valid one for a dimension, and acts like only the valid ones were provided. But in case there are only invalid codes, returns 404 Not found error.

Question to clarify before fixing the issue: Is the RI behaviour OK, or should we raise error in case of invalid code in query filter expression?

Examples from DotStatV8 (AA is the inavlid code)
http://dotstatcor-dev1.main.oecd.org/NSIWebserviceDissemination/rest/data/UNSD,DF_SDG,0.3/AA............

http://dotstatcor-dev1.main.oecd.org/NSIWebserviceDissemination/rest/data/UNSD,DF_SDG,0.3/A+AA............

Examples from RI (FF is the invalid code)
http://dotstatcor-dev1.main.oecd.org/RI_NsiWebService/rest/data/MA_3,NER_PRIMARY,1.0/.FF./?startPeriod=2000&endPeriod=2018

http://dotstatcor-dev1.main.oecd.org/RI_NsiWebService/rest/data/MA_3,NER_PRIMARY,1.0/.FF+F./?startPeriod=2000&endPeriod=2018

First work done as of 06/01/2018 and remaining work status

  • Jens opened an issue at the SDMX-TWG: https://github.com/sdmx-twg/sdmx-rest/issues/64
  • In Dotstat data plugin, the issue is still present, the error is “500 Internal server error”.
  • RI implementation: we can be almost sure that the NSI WS behaves the same way. This needs to be checked and if this issue is still present in their implementation, then a JIRA ticket should be created for ESTAT.
Assignee
Assign to
Release .Stat Suite .NET v3.2.0
Milestone
Release .Stat Suite .NET v3.2.0
Assign milestone
Time tracking
None
Due date
None