Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Fix
-
1.4.4, 1.5.3
-
None
Description
As of mentioned versions MCS returns cryptic messages if expection is raised in BPP::execute().
Here is the example how MCS fails trying to call Row::getIntValue() from a non-int column.
May 7 11:41:05 drrtuy-devel-1 PrimProc[27208]: 05.910856 |0|0|0| W 28 CAL0000: floor: datatype of decimal
|
....
|
May 7 11:41:05 drrtuy-devel-1 Calpont[27296]: 05.912941 |0|0|0| E 00 CAL0000: /data/mdb-server/storage/columnstore/dbcon/joblist/batchprimitiveprocessor-jl.cpp@739: assertion 'in.length() > offset' failed
|
May 7 11:41:05 drrtuy-devel-1 joblist[27296]: 05.913128 |4|0|0| C 05 CAL0000: st: 0 TupleBPS::receiveMultiPrimitiveMessages() caught an exception: IDB-2035: An internal error occurred. Check the error log file & contact support.
|
There are no means to raise a warning from PrimProc. It is important for wide-decimals when MCS has to reduce the value down MAX_INT executing operation. Right now it does it w/o notifying the user.
Attachments
Issue Links
- relates to
-
MCOL-641 Full DECIMAL support in ColumnStore
-
- Closed
-