You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Rushabh Shah (Jira)" <ji...@apache.org> on 2024/01/08 17:52:00 UTC

[jira] [Resolved] (PHOENIX-7167) Last DDL Timestamp is set to null in connection which bootstraps System tables

     [ https://issues.apache.org/jira/browse/PHOENIX-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rushabh Shah resolved PHOENIX-7167.
-----------------------------------
    Resolution: Fixed

> Last DDL Timestamp is set to null in connection which bootstraps System tables
> ------------------------------------------------------------------------------
>
>                 Key: PHOENIX-7167
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-7167
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Palash Chauhan
>            Assignee: Palash Chauhan
>            Priority: Major
>
> When trying to create SYSTEM.CATALOG table, a PTable object is bootstrapped in the client cache which is then overridden by what the server returns. When the table is not found (i.e. this is the first connection), LAST_DDL_TIMESTAMP ends up being null because of this code block:
> {code:java}
> .setLastDDLTimestamp(result.getTable() != null ?
>                                 result.getTable().getLastDDLTimestamp() : null) {code}
> This leads to NPE when client tries to validate timestamp for SYSTEM.CATALOG table.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)