bhj in adaptive execution 5. Coalesce and Repartition Hint for SQL Queries Solution for Big Result Sets Typically, when a user submits a SELECT query to Spark SQL engine, the Driver calls collect to trigger Since v1.4.0-incubating, Kyuubi supports incremental collection mode, it is a solution for big result sets. This feature is disabled in default, you can turn on it by setting the configuration kyuubi.operation big_result_query.sql --incremental=true is required for beeline client, otherwise, the entire result sets is fetched and buffered before being displayed, which may cause client side OOM. Change incremental

bhj in adaptive execution 5. Coalesce and Repartition Hint for SQL Queries Solution for Big Result Sets Typically, when a user submits a SELECT query to Spark SQL engine, the Driver calls collect to trigger Since v1.4.0-incubating, Kyuubi supports incremental collection mode, it is a solution for big result sets. This feature is disabled in default, you can turn on it by setting the configuration kyuubi.operation big_result_query.sql --incremental=true is required for beeline client, otherwise, the entire result sets is fetched and buffered before being displayed, which may cause client side OOM. Change incremental

bhj in adaptive execution 5. Coalesce and Repartition Hint for SQL Queries Solution for Big Result Sets Typically, when a user submits a SELECT query to Spark SQL engine, the Driver calls collect to trigger Since v1.4.0-incubating, Kyuubi supports incremental collection mode, it is a solution for big result sets. This feature is disabled in default, you can turn on it by setting the configuration kyuubi.operation big_result_query.sql --incremental=true is required for beeline client, otherwise, the entire result sets is fetched and buffered before being displayed, which may cause client side OOM. Change incremental

bhj in adaptive execution 5. Coalesce and Repartition Hint for SQL Queries Solution for Big Result Sets Typically, when a user submits a SELECT query to Spark SQL engine, the Driver calls collect to trigger Since v1.4.0-incubating, Kyuubi supports incremental collection mode, it is a solution for big result sets. This feature is disabled in default, you can turn on it by setting the configuration kyuubi.operation big_result_query.sql --incremental=true is required for beeline client, otherwise, the entire result sets is fetched and buffered before being displayed, which may cause client side OOM. Change incremental

bhj in adaptive execution 5. Coalesce and Repartition Hint for SQL Queries Solution for Big Result Sets Typically, when a user submits a SELECT query to Spark SQL engine, the Driver calls collect to trigger Since v1.4.0-incubating, Kyuubi supports incremental collection mode, it is a solution for big result sets. This feature is disabled in default, you can turn on it by setting the configuration kyuubi.operation big_result_query.sql --incremental=true is required for beeline client, otherwise, the entire result sets is fetched and buffered before being displayed, which may cause client side OOM. Change incremental

(DRA) in Kyuubi How To Use Spark Adaptive Query Execution (AQE) in Kyuubi Solution for Big Result Sets Gluten Deploy Kyuubi On Kubernetes Requirements To deploy Kyuubi on Kubernetes, you’d better have AQE Best Practices for Applying AQE to Kyuubi Spark Known issues References Solution for Big Result Sets Incremental collection Use in single connections Change incremental collection mode in session Gluten Hint for SQL Queries [https://issues.apache.org/jira/browse/SPARK-24940] Solution for Big Result Sets Typically, when a user submits a SELECT query to Spark SQL engine, the Driver calls collect to trigger

(DRA) in Kyuubi How To Use Spark Adaptive Query Execution (AQE) in Kyuubi Solution for Big Result Sets Deploy Kyuubi On Kubernetes Requirements If you want to deploy Kyuubi on Kubernetes, you’d better AQE Best Practices for Applying AQE to Kyuubi Spark Known issues References Solution for Big Result Sets Incremental collection Use in single connections Change incremental collection mode in session How Hint for SQL Queries [https://issues.apache.org/jira/browse/SPARK-24940] Solution for Big Result Sets Typically, when a user submits a SELECT query to Spark SQL engine, the Driver calls collect to trigger

(DRA) in Kyuubi How To Use Spark Adaptive Query Execution (AQE) in Kyuubi Solution for Big Result Sets Deploy Kyuubi On Kubernetes Requirements If you want to deploy Kyuubi on Kubernetes, you’d better AQE Best Practices for Applying AQE to Kyuubi Spark Known issues References Solution for Big Result Sets Incremental collection Use in single connections Change incremental collection mode in session How Hint for SQL Queries [https://issues.apache.org/jira/browse/SPARK-24940] Solution for Big Result Sets Typically, when a user submits a SELECT query to Spark SQL engine, the Driver calls collect to trigger

(DRA) in Kyuubi How To Use Spark Adaptive Query Execution (AQE) in Kyuubi Solution for Big Result Sets Deploy Kyuubi On Kubernetes Requirements If you want to deploy Kyuubi on Kubernetes, you’d better AQE Best Practices for Applying AQE to Kyuubi Spark Known issues References Solution for Big Result Sets Incremental collection Use in single connections Change incremental collection mode in session How Hint for SQL Queries [https://issues.apache.org/jira/browse/SPARK-24940] Solution for Big Result Sets Typically, when a user submits a SELECT query to Spark SQL engine, the Driver calls collect to trigger

(DRA) in Kyuubi How To Use Spark Adaptive Query Execution (AQE) in Kyuubi Solution for Big Result Sets Deploy Kyuubi On Kubernetes Requirements If you want to deploy Kyuubi on Kubernetes, you’d better AQE Best Practices for Applying AQE to Kyuubi Spark Known issues References Solution for Big Result Sets Incremental collection Use in single connections Change incremental collection mode in session How Hint for SQL Queries [https://issues.apache.org/jira/browse/SPARK-24940] Solution for Big Result Sets Typically, when a user submits a SELECT query to Spark SQL engine, the Driver calls collect to trigger