phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <>
Subject [jira] [Created] (PHOENIX-4265) NPE when hinting index on table with ROW_TIMESTAMP
Date Mon, 02 Oct 2017 16:15:01 GMT
James Taylor created PHOENIX-4265:

             Summary: NPE when hinting index on table with ROW_TIMESTAMP
                 Key: PHOENIX-4265
             Project: Phoenix
          Issue Type: Improvement
            Reporter: James Taylor

See email discussion here:

I'm not able to repro with this unit test:
    public void testIndexHintOnTableWithRowTimestamp() throws Exception {
        Connection conn = DriverManager.getConnection(getUrl());
        try {
            conn.createStatement().execute("CREATE IMMUTABLE TABLE t1 (k1 TIMESTAMP not null,
k2 bigint not null, v bigint, constraint pk primary key (k1 row_timestamp,k2 ))");
            conn.createStatement().execute("CREATE INDEX idx ON t1 (v)");
            conn.createStatement().execute("SELECT /*+ INDEX(T1 IDX) */ K1,K2,V FROM t1 WHERE
v = 5");
        } finally {

FYI, due to the inability to keep an index in sync when there's a ROW_TIMESTAMP column, as
of 4.12 we're disallowing the creation of mutable secondary indexes when a table has a ROW_TIMESTAMP
column. Usually, since the timestamp is part of the row key, the data table can be declared
IMMUTABLE. In this case, the index would still be allowed.

This message was sent by Atlassian JIRA

View raw message