morningman commented on issue #47948: URL: https://github.com/apache/doris/issues/47948#issuecomment-2692284425
> 1. What is the idea behind supporting these 3 new features? Does this mean we can federate queries to Snowflake/DB? > If so, why? Is it to help migrate away from Databricks and Snowflake onto VeloDB? > • Support Snowflake Iceberg table engine. > • Support Databricks Uniform DeltaLake table engine. > • Support Unity Catalog. > 2. I am happy to see these 2 features: • IAM Role authentication > Query Optimizer • Data lineage information interface: Provide data lineage tracking capabilities > 3. Execution plan tweaking can be a very powerful feature, but in the past I have seen that it can also cause engine crashes. > How is it made safe? > > 5. Plan Management - Execution plan fixing: Support plan controllability. 1. Yes. Since both Snowflake and Databricks supported Iceberg table format, and open sourced their catalog (Polaris and Unity), I think we can easily access the data on them, and to help user either migrate their data from one to each other, or simply do the federate quries 3. if the engine crashed after plan tweaking, I am sure that is bug so we need to fix it. But what we try to do is to make the query plan more stable, to avoid plan changing after irrelevant features being introduced -- 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: commits-unsubscr...@doris.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org For additional commands, e-mail: commits-h...@doris.apache.org
