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

timestamp selected from CTE that uses a columnstore join intermitantly returns zero date

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • 6.4.6
    • 22.08.7
    • ExeMgr
    • None
    • columnstore 1:10.7.7-6.4.6+maria~ubu2004
      mariadb Ver 15.1 Distrib 10.7.6-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2

    Description

      Current:
      as a user selecting a timestamp from a CTE, which is composed of an innodb table and a columnstore table joined together, the resulting select data yields a zero date stamp intermittently.

      Expectation:
      as a user selecting a timestamp from a CTE, which is composed of an innodb table and a columnstore table joined together, the resulting select data should include a valid timestamp.

      Notes
      Attached is a schema setup query that includes some clear sample data. The second file is my sample query that reproduces the bug. As a user, I can execute the select used for the CTE without issue. As a user executing the select from the cte, I get the bad data out on and off.

      Im also attaching timestamped screenshots showing where the query results are with timestamp and then immediately show the zero timestamp. Mariadb version and columnstore version noted.

      Please let me know if you need additional details.

      Best,
      George

      Attachments

        Activity

          People

            David.Hall David Hall (Inactive)
            georgeb George Birnbaum
            Gagan Goel Gagan Goel (Inactive)
            Daniel Lee Daniel Lee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 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.