Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-6301

Return the wrong result while using Spider engine with 'where' and 'order'

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 10.0.10-galera
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      We are using InnoDB as the remote DB server which stores the physical data ( With Galera Cluster)
      And in front of that , there is another cluster of servers which is built with Spider Engine table. We found that while using 'where' and 'order by' together in select, the returned resultsets are always null(for varchar column) or 0 (int/float/timestamp column) if the column is not mentioned in where and order by. For example, a statement like

       select name,createUserId,updateUserId,fabId.price,createTime  from product where price>0 and fabId=1 order by createTime

      The value of 'name'/'createUserId'/'updateUserId' will be null/0 but others will have its original value.

      We have no idea if this is bug of Spider engine or anything related to mariaDB. The origin of database (the remote DB server) will not have this problem if the statement is executed there.
      Please help on this issue or let us know if this problem is not about mariaDB. Thanks!

      Attached is the snap shot of version information.
      If any information insufficient, please let us know and we will provide ASAP.

        Attachments

          Activity

            People

            Assignee:
            Kentoku Kentoku Shiba
            Reporter:
            Ann_Chi Ann Chi
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration