Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-2125

ORDER BY on full PK on salted table does not work

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.5.0
    • Fix Version/s: 4.5.0
    • Labels:
      None

      Description

      Ordering by the full PK on a salted table does not work

      REPRO:

      --create a salted table with 2 pk fields
      CREATE TABLE IF NOT EXISTS TEST_TABLE (
      PK1 CHAR(15) NOT NULL,
      PK2 CHAR(15) NOT NULL
      CONSTRAINT PK PRIMARY KEY
      (
      PK1,
      PK2
      )
      ) SALT_BUCKETS=16;

      --insert data
      UPSERT INTO TEST_TABLE (PK1, PK2) VALUES ('FOO','BAR1-oiwnefin');
      UPSERT INTO TEST_TABLE (PK1, PK2) VALUES ('FOO','BAR2-qoosdfpin');
      UPSERT INTO TEST_TABLE (PK1, PK2) VALUES ('FOO','BAR3*)&&)*(@)');
      UPSERT INTO TEST_TABLE (PK1, PK2) VALUES ('FOO','BAR4 .');

      --do a quick query to verify the data in field PK2 is not completely in order
      --(salting + round robin should hopefully have thrown at least 2 rows out of order)
      SELECT * FROM TEST_TABLE

      --running this query, you can see that the rows are now properly ordered
      SELECT * FROM TEST_TABLE ORDER BY PK2

      --this query is logically identical to the previous SELECT statement with ordering,
      – but as you can see it's actually identical to the first SELECT statement (without ordering)
      SELECT * FROM TEST_TABLE ORDER BY PK1, PK2

      --clean up if you like
      DROP TABLE IF EXISTS TEST_TABLE CASCADE;

        Attachments

        1. PHOENIX-2125.patch
          8 kB
          Samarth Jain

          Activity

            People

            • Assignee:
              samarthjain Samarth Jain
              Reporter:
              rangent Brian Esserlieu
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: