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

NULLS FIRST/NULL LAST should not impact whether GROUP BY is order preserving

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 4.8.0
    • 4.9.0, 4.8.2
    • None
    • None

    Description

      This may be related to PHOENIX-3451 but the behavior is different so filing it separately.

      Steps to repro:
      CREATE TABLE IF NOT EXISTS TEST.TEST (
      ORGANIZATION_ID CHAR(15) NOT NULL,
      CONTAINER_ID CHAR(15) NOT NULL,
      ENTITY_ID CHAR(15) NOT NULL,
      SCORE DOUBLE,
      CONSTRAINT TEST_PK PRIMARY KEY (
      ORGANIZATION_ID,
      CONTAINER_ID,
      ENTITY_ID
      )
      ) VERSIONS=1, MULTI_TENANT=TRUE, REPLICATION_SCOPE=1, TTL=31536000;
      CREATE INDEX IF NOT EXISTS TEST_SCORE ON TEST.TEST (CONTAINER_ID, SCORE DESC, ENTITY_ID DESC);

      UPSERT INTO test.test VALUES ('org1','container1','entityId6',1.1);
      UPSERT INTO test.test VALUES ('org1','container1','entityId5',1.2);
      UPSERT INTO test.test VALUES ('org1','container1','entityId4',1.3);
      UPSERT INTO test.test VALUES ('org1','container1','entityId3',1.4);
      UPSERT INTO test.test VALUES ('org1','container1','entityId2',1.5);
      UPSERT INTO test.test VALUES ('org1','container1','entityId1',1.6);

      SELECT DISTINCT entity_id, score
      FROM test.test
      WHERE organization_id = 'org1'
      AND container_id = 'container1'
      ORDER BY score DESC

      Notice that the returned results are not returned in descending score order. Instead they are returned in descending entity_id order. If I remove the DISTINCT or remove the secondary index the result is correct.

      Attachments

        1. PHOENIX-3452_v3.patch
          46 kB
          chenglei
        2. PHOENIX-3452_v2.patch
          14 kB
          chenglei

        Activity

          People

            comnetwork chenglei
            jpalmert Joel Palmert
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: