vinothchandar commented on pull request #2410: URL: https://github.com/apache/hudi/pull/2410#issuecomment-755524721
>Engine can not be tied to client/writing, but can engine become a standalone module? Potentially. We can consider this again, when we think about the additional abstractions needed to make more code move from flink-client, java-client etc back into client-common? That said, the problem here is that FSUtils is in `hudi-common`. Alternatively we can move `FSUtils` & the `FileSystemBackedTableMetadata` to client-common? Seems like FSUtils not really called in hudi-common at all?  But, `FileSystemBackedTableMetadata` is used by the query side as well and has to be in `hudi-common`. So we can make a new class inside `client-common` that does parallelized `getAllPartitionPaths()`? wdyt? @umehrot2 ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
