Toroidals commented on issue #12901: URL: https://github.com/apache/hudi/issues/12901#issuecomment-2696964958
> > The base path in the logs is the same. > > [hudi/hudi-sync/hudi-hive-sync/src/main/java/org/apache/hudi/hive/HiveSyncTool.java](https://github.com/apache/hudi/blob/1e364d19880af711ca7b622af654660b58801852/hudi-sync/hudi-hive-sync/src/main/java/org/apache/hudi/hive/HiveSyncTool.java#L243) > > Line 243 in [1e364d1](/apache/hudi/commit/1e364d19880af711ca7b622af654660b58801852) > > if (tableExists && !FSUtils.comparePathsWithoutScheme(syncClient.getBasePath(), syncClient.getTableLocation(tableName))) { > [@Toroidals](https://github.com/Toroidals) as shown in the code, the log "basepath is updated" will be printed only when the current hudi base path is not equal with the one in hive metastore, but unfortunately these two paths are not printed in the log, maybe you can print them in your env to check if there is unexpected problem there.  I tried to print the logs and found that the BasePath is different. syncClient.getTableLocation(tableName) has the HDFS namenode cluster name, while syncClient.getBasePath() omits it, resulting in the comparison returning false. However, this issue didn't exist in version 0.15.0. It's hard to notice if you don't look closely. I will try to modify the configuration to resolve this issue. Thank you for your support. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
