palashc commented on code in PR #1807: URL: https://github.com/apache/phoenix/pull/1807#discussion_r1476548989
########## phoenix-core-client/src/main/java/org/apache/phoenix/schema/MetaDataClient.java: ########## @@ -898,9 +898,9 @@ public MetaDataMutationResult updateCache(PName tenantId, List<String> functionN * @return true if the PTable contained by result was modified and false otherwise * @throws SQLException if the physical table cannot be found */ - private boolean addColumnsAndIndexesFromAncestors(MetaDataMutationResult result, Long resolvedTimestamp, - boolean alwaysAddAncestorColumnsAndIndexes, - boolean alwaysHitServerForAncestors) + private boolean addColumnsIndexesAndLastDDLTimestampsFromAncestors(MetaDataMutationResult result, Long resolvedTimestamp, Review Comment: Good point. I just verified with a test that a new client will not be able to populate the map for both indexes and view indexes. I created a table, view and view-index using client-1. Then I queried the view using client-2. In client2's cache, view index is not populated with the map. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@phoenix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org