rishii-19-works commented on issue #3344: URL: https://github.com/apache/polaris/issues/3344#issuecomment-3713767674
Thanks for laying out the broader vision — that’s very helpful, and the example makes the use case clear. To keep this manageable for an initial step, I’d suggest starting with a scoped “bootstrap” capability: pointing Polaris at a given root location containing existing Parquet files and creating an Iceberg (or Paimon) table by generating the required metadata and manifests from those files. This would be a one-time operation, without continuous monitoring or event-based updates. Follow-ups like directory tree discovery, S3/Lambda-based maintenance, and mixed ingestion paths could then build on top of that foundation incrementally. If that sounds reasonable, I can focus first on the bootstrap/table-creation piece and share a concrete design proposal before moving into implementation. -- 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]
