gszadovszky commented on issue #3006: URL: https://github.com/apache/parquet-java/issues/3006#issuecomment-2747058693
I'm not sure I completely understand the use case. Configurable, "under the hood" caching only makes sense if we think it improves the workflow when parquet-java is used more like a black box. Also, we probably want to expose such configs to the end users to fine tune the engine based on their data? But in this case we would need some analysis to prove caching really improves performance. In the other hand if caching is not generally useful but in some specific scenarios where some custom code takes place at parquet-java level, I would vote on making `ParquetFileReader` extensible or even implement the caching mechanism that can be used/adjusted from the java API directly. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
