Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-3987

ColumnStore returns opaque error messages and has no means to raise SQL session warnings from PrimProc.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.5, 1.4.4
    • Fix Version/s: None
    • Component/s: ExeMgr, PrimProc
    • Labels:
      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

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              drrtuy Roman
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated: