#987 closed defect (fixed)

WCST Update fail leaves database incosistent

Reported by: mdumitru Owned by: vmerticariu
Priority: critical Milestone:
Component: undecided Version: development
Keywords: Cc:
Complexity: Medium

Description

Example of the error after the update failed:
Service Call: http://localhost:8080/rasdaman/ows?service=WCS&version=2.0.1&request=UpdateCoverage&coverageId=AvgLandTemp&subset1=Lat(-90.0,90.0)&inputCoverageRef=file:///tmp/082a101f_6526_4ddc_ae70_b2b71c5eea1f.gml&subset3=ansi("2000-02-01T00:00:00+00:00")&subset2=Long(-180.0,180.0)
Error Code: InvalidCoverageConfiguration?
Error Text: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ows:ExceptionReport version="2.0.0"

xsd:schemaLocation="http://www.opengis.net/ows/2.0 http://schemas.opengis.net/ows/2.0/owsExceptionReport.xsd"
xmlns:ows="http://www.opengis.net/ows/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink">
<ows:Exception exceptionCode="InvalidCoverageConfiguration">

<ows:ExceptionText>Coverage 'AvgLandTemp? has a wrong number of coefficients for axis 5 (12) and is not consistent with its rasdaman `sdom' (11).</ows:ExceptionText>

</ows:Exception>

</ows:ExceptionReport>

Change History (3)

comment:1 Changed 20 months ago by pbaumann

  • Priority changed from major to critical

comment:2 Changed 20 months ago by vmerticariu

  • Status changed from new to accepted

comment:3 Changed 19 months ago by dmisev

  • Resolution set to fixed
  • Status changed from accepted to closed

Patch has been applied as far as I know.

Note: See TracTickets for help on using tickets.