Opened 9 years ago

Closed 8 years ago

#1236 closed defect (fixed)

WCPS1.5_Error when parsing "pow" operator

Reported by: Bang Pham Huu Owned by:
Priority: major Milestone: 10.0
Component: undecided Version: development
Keywords: WCPS 2.0, error with pow operator Cc: Dimitar Misev, Alex Dumitru, Vlad Merticariu
Complexity: Medium

Description

WCPS query

for c in (mr) return encode( pow( c[i(100:110),j(100:110)], -0.5 ), "csv" )

returns error in WCPS 1.5

<ows:Exception exceptionCode="RuntimeError">
<ows:ExceptionText>
petascope.wcps2.error.managed.processing.WCPSProcessingError : 
A parsing error occurred at position=1:29. 
Offending symbol is=[@9,29:31='pow',<53>,1:29]. Parser message=no viable alternative at input 'pow'.
</ows:ExceptionText>
</ows:Exception>
</ows:ExceptionReport>

while WCPS returns rasql query 

select csv(pow(c[100:110,100:110], -0.5)) from mr AS c where oid(c)=45569

and values

Change History (2)

comment:1 by Bang Pham Huu, 9 years ago

same with
77-pow_operation_int.test

for c in (mr) return encode( pow( c[i(100:110),j(100:110)], 2 ), "csv" )

and 78-pow_operation_float.test

for c in (mr) return encode( pow( c[i(100:110),j(100:110)], 1.85 ), "csv" )

    <ows:Exception exceptionCode="RuntimeError">
        <ows:ExceptionText>petascope.wcps2.error.managed.processing.WCPSProcessingError : A parsing error occurred at position=1:29. Offending symbol is=[@9,29:31='pow',&lt;53&gt;,1:29].
 Parser message=no viable alternative at input 'pow'.</ows:ExceptionText>
    </ows:Exception>
Last edited 9 years ago by Bang Pham Huu (previous) (diff)

comment:2 by Bang Pham Huu, 8 years ago

Resolution: → fixed
Status: new → closed

patch was accepted, close ticket.

Note: See TracTickets for help on using tickets.