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

Behavioral differences between MariaDB and ColumnStore for few functions

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 1.0.0
    • 1.0.4
    • None
    • None
    • 2016-19, 2016-20, 2016-21

    Description

      Build tested:
      mscadmin> getsoft
      getsoftwareinfo Thu Jun 2 08:36:01 2016

      Name : mariadb-columnstore-platform Relocations: (not relocatable)
      Version : 1.0 Vendor: MariaDB Corporation Ab
      Release : 0 Build Date: Fri 27 May 2016 03:07:53 PM CDT
      Install Date: Mon 30 May 2016 10:07:40 AM CDT Build Host: srvbuilder
      Group : Applications Source RPM: mariadb-columnstore-1.0-0.src.rpm

      POWER
      POW
      EXP
      DIV
      COT

      When supplied with crazily large or small values as parameters for the above functions, MariaDB returns a value out of range error, where Columnstore returns a value, which may or may not be correct.

      Here is a sample error msg From MariaDB:

      ERROR 1690 (22003) at line 1: DOUBLE value is out of range in 'pow(`qrepd01`.`datatypetestm`.`CBIGINT`,(-(3) * `qrepd01`.`datatypetestm`.`CIDX`))'

      As for cot(0), which is a divided-by-zero case, MariaDB returns an out of range error, where Columnstore returns NULL.

      Could this behavioral difference caused by a settings in the my.cnf file?

      For now, we are treating these differences as known/expected differences.

      Attachments

        Issue Links

          Activity

            People

              dleeyh Daniel Lee (Inactive)
              dleeyh Daniel Lee (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.