[
https://issues.apache.org/jira/browse/PHOENIX-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17804394#comment-17804394
]
ASF GitHub Bot commented on PHOENIX-7167:
-----------------------------------------
shahrs87 commented on PR #1779:
URL: https://github.com/apache/phoenix/pull/1779#issuecomment-1881554449
There are 2 failing tests but both are known to be flaky. Ignoring them and
merging this PR. [Jenkins build link
](https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1779/3/testReport/)
```
org.apache.phoenix.end2end.QueryTimeoutIT.testQueryTimeout
org.apache.phoenix.jdbc.LoggingHAConnectionLimiterIT.testActivityLogsOnUpsertWhenFailures
```
> 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)
