dev  

Messages by Thread

• [VOTE] SPIP: Constraints in DSv2 Anton Okolnychyi
  • Re: [VOTE] SPIP: Constraints in DSv2 Gengliang Wang
  • Re: [VOTE] SPIP: Constraints in DSv2 Denny Lee
  • Re: [VOTE] SPIP: Constraints in DSv2 huaxin gao
  • Re: [VOTE] SPIP: Constraints in DSv2 L. C. Hsieh
  • Re: [VOTE] SPIP: Constraints in DSv2 Ángel Álvarez Pascua
  • Re: [VOTE] SPIP: Constraints in DSv2 Anton Okolnychyi
  • Re: [VOTE] SPIP: Constraints in DSv2 Ángel Álvarez Pascua
  • Re: [VOTE] SPIP: Constraints in DSv2 Gengliang Wang
  • Re: [VOTE] SPIP: Constraints in DSv2 Wenchen Fan
  • Re: [VOTE] SPIP: Constraints in DSv2 Ángel Álvarez Pascua
  • Re: [VOTE] SPIP: Constraints in DSv2 Ángel Álvarez Pascua
  • Re: [VOTE] SPIP: Constraints in DSv2 Chao Sun
  • Re:Re: [VOTE] SPIP: Constraints in DSv2 beliefer
  • Re: Re: [VOTE] SPIP: Constraints in DSv2 Anton Okolnychyi
  • Re: [VOTE] SPIP: Constraints in DSv2 Wenchen Fan
  • Re: [VOTE] SPIP: Constraints in DSv2 Szehon Ho
  • Re: [VOTE] SPIP: Constraints in DSv2 DB Tsai
  • Re: [VOTE] SPIP: Constraints in DSv2 Peter Toth
  • Re: [VOTE] SPIP: Constraints in DSv2 Yuming Wang
  • Re: [VOTE] SPIP: Constraints in DSv2 Anurag Mantripragada
  • Re: [VOTE] SPIP: Constraints in DSv2 Zhou Jiang
  • Re: [VOTE] SPIP: Constraints in DSv2 Jules Damji
  • Re: [VOTE] SPIP: Constraints in DSv2 serge rielau . com
  • Re: [VOTE] SPIP: Constraints in DSv2 Jungtaek Lim
  • Re: [VOTE] SPIP: Constraints in DSv2 Hyukjin Kwon
• [SPARK-51264][SQL][JDBC] JDBC write keeps driver connection open unnecessarily Ángel Álvarez Pascua
• [VOTE] Release Spark 4.0.0 (RC3) Wenchen Fan
  • Re: [VOTE] Release Spark 4.0.0 (RC3) Rozov, Vlad
  • Re: [VOTE] Release Spark 4.0.0 (RC3) Bobby
  • Re: [VOTE] Release Spark 4.0.0 (RC3) Ángel Álvarez Pascua
  • Re: [VOTE] Release Spark 4.0.0 (RC3) Bobby
  • Re: [VOTE] Release Spark 4.0.0 (RC3) Ángel Álvarez Pascua
  • Re: [VOTE] Release Spark 4.0.0 (RC3) Yang Jie
  • Re: [VOTE] Release Spark 4.0.0 (RC3) Hyukjin Kwon
  • Re: [VOTE] Release Spark 4.0.0 (RC3) Wenchen Fan
  • Re: [VOTE] Release Spark 4.0.0 (RC3) huaxin gao
• Re: Contribution to Spark SQL: new data type TIME Max Gekk
• [RESULT][VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Hyukjin Kwon
  • Re: [RESULT][VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Mark Hamstra
  • Re: [RESULT][VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Wenchen Fan
  • Re: [RESULT][VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Hyukjin Kwon
  • Re: [RESULT][VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Jungtaek Lim
  • Re: [RESULT][VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Jungtaek Lim
• [VOTE][RESULT][FINAL] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Jungtaek Lim
• Re: [VOTE][RESULT] Single-pass Analyzer for Catalyst Ángel Álvarez Pascua
• [PROPOSE] Fix the procedural steps on the incorrect config fixes Jungtaek Lim
• Re: [DISCUSS] New Spark Connect Client repository for Swift language Martin Grund
  • Re: [DISCUSS] New Spark Connect Client repository for Swift language Dongjoon Hyun
  • Re: [DISCUSS] New Spark Connect Client repository for Swift language Martin Grund
  • Re: [DISCUSS] New Spark Connect Client repository for Swift language Mich Talebzadeh
• [DISCUSS] Involve any hack / workaround to not include vendor name in migration logic Jungtaek Lim
  • Re: [DISCUSS] Involve any hack / workaround to not include vendor name in migration logic Jungtaek Lim
  • Re: [DISCUSS] Involve any hack / workaround to not include vendor name in migration logic Jungtaek Lim
  • Re: [DISCUSS] Involve any hack / workaround to not include vendor name in migration logic Mark Hamstra
  • Re: [DISCUSS] Involve any hack / workaround to not include vendor name in migration logic Jungtaek Lim
  • Re: [DISCUSS] Involve any hack / workaround to not include vendor name in migration logic Mich Talebzadeh
  • Re: [DISCUSS] Involve any hack / workaround to not include vendor name in migration logic Jungtaek Lim
• [ANNOUNCE] Apache Sedona 1.7.1 released Jia Yu
• [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Mark Hamstra
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Mark Hamstra
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Holden Karau
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Holden Karau
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Mich Talebzadeh
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Jungtaek Lim
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Holden Karau
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Jungtaek Lim
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Wenchen Fan
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Wenchen Fan
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Holden Karau
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Jungtaek Lim
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Jungtaek Lim
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Jungtaek Lim
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Dongjoon Hyun
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Jungtaek Lim
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Yuanjian Li
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Hyukjin Kwon
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Jungtaek Lim
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Jungtaek Lim
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Holden Karau
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Jungtaek Lim
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Jungtaek Lim
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Jungtaek Lim
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Mich Talebzadeh
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Dongjoon Hyun
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Jungtaek Lim
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Jungtaek Lim
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Jungtaek Lim
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Wenchen Fan
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Wenchen Fan
  • Re: [VOTE] Technical Justification for the veto of the "Retain migration logic..." code change proposal is not valid Reynold Xin
• RE: Re: [Discuss] SPIP: Support NanoSecond Timestamps 谭琦
  • Re: Re: [Discuss] SPIP: Support NanoSecond Timestamps Wenchen Fan
  • Re: Re: [Discuss] SPIP: Support NanoSecond Timestamps Szehon Ho
  • Re: [Discuss] SPIP: Support NanoSecond Timestamps DB Tsai
  • Re: [Discuss] SPIP: Support NanoSecond Timestamps Dongjoon Hyun
  • Re: [Discuss] SPIP: Support NanoSecond Timestamps Zhou Jiang
  • Re: [Discuss] SPIP: Support NanoSecond Timestamps Sakthi
  • Re: [Discuss] SPIP: Support NanoSecond Timestamps Reynold Xin
  • Re: [Discuss] SPIP: Support NanoSecond Timestamps serge rielau . com
  • Re: [Discuss] SPIP: Support NanoSecond Timestamps Reynold Xin
  • Re: [Discuss] SPIP: Support NanoSecond Timestamps Gengliang Wang
  • Re: [Discuss] SPIP: Support NanoSecond Timestamps serge rielau . com
  • RE: Re: [Discuss] SPIP: Support NanoSecond Timestamps 谭琦
  • RE: Re: [Discuss] SPIP: Support NanoSecond Timestamps Qi Tan
  • Re: Re: [Discuss] SPIP: Support NanoSecond Timestamps Qi Tan
• [VOTE][RESULT] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Jungtaek Lim
  • Re: [VOTE][RESULT] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Mark Hamstra
  • Re: [VOTE][RESULT] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Jungtaek Lim
  • Re: [VOTE][RESULT] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Mark Hamstra
  • Re: [VOTE][RESULT] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Jungtaek Lim
  • Re: [VOTE][RESULT] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Jungtaek Lim
  • Re: [VOTE][RESULT] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Mark Hamstra
  • Re: [VOTE][RESULT] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Jungtaek Lim
  • Re: [VOTE][RESULT] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Jungtaek Lim
  • Re: [VOTE][RESULT] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Mark Hamstra
  • Re: [VOTE][RESULT] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Sean Owen
  • Re: [VOTE][RESULT] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Mark Hamstra
  • Re: [VOTE][RESULT] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Mich Talebzadeh
  • Re: [VOTE][RESULT] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Holden Karau
  • Re: [VOTE][RESULT] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Ángel Álvarez Pascua
  • Re: [VOTE][RESULT] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Jungtaek Lim
  • Re: [VOTE][RESULT] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Mark Hamstra
  • Re: [VOTE][RESULT] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Jungtaek Lim
  • Re: [VOTE][RESULT] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Ángel Álvarez Pascua
  • Re: [VOTE][RESULT] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Jungtaek Lim
  • Re: [VOTE][RESULT] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Mark Hamstra
• Code formatting tech debt Rob Reeves
  • Re: Code formatting tech debt Asif Shahid
  • Re: Code formatting tech debt Rob Reeves
• Unsubscribe 朱静
  • Unsubscribe Aditya Gunjal
  • Unsubscribe Aswin Rajasekharan
  • Unsubscribe Stan Zhai
  • Unsubscribe bruce COTTMAN
  • Unsubscribe Pranshul Goyal
  • Unsubscribe Ramin Orujov
  • Unsubscribe Susham kumar reddy Yerabolu
  • Unsubscribe Tình Trần
  • Unsubscribe Zac Wang
  • Unsubscribe Ramin Orujov
  • Unsubscribe Ramin Orujov
  • Unsubscribe Ratnesh Mishra
  • Unsubscribe bruce COTTMAN
  • Unsubscribe Jaskaran singh
  • Unsubscribe Huibo Peng
  • Unsubscribe Yujung Dong
  • unsubscribe Zhu, Zhenya
  • Unsubscribe Alan Paulsen
  • Unsubscribe Subhasis Mukherjee
  • Unsubscribe Jeremy Chung
  • Unsubscribe bruce COTTMAN
  • Unsubscribe Gunturu Manohar
  • Unsubscribe Jeremy Chung
  • unsubscribe Sachin Jain
  • unsubscribe David Clark`
  • Unsubscribe bruce COTTMAN
  • unsubscribe Ashutosh Samantaray
  • Unsubscribe bruce COTTMAN
  • unsubscribe bruce COTTMAN
  • Unsubscribe bruce COTTMAN
  • Unsubscribe bruce COTTMAN
  • unsubscribe Murali Krishna Pamulapati
  • Unsubscribe Edu Chana
  • unsubscribe Szegedi Istvan
  • Unsubscribe Subhasis Mukherjee
  • Unsubscribe [email protected]
  • Unsubscribe Subhasis Mukherjee
  • Unsubscribe Subhasis Mukherjee
  • Unsubscribe Subhasis Mukherjee
  • Unsubscribe Subhasis Mukherjee
  • Unsubscribe Subhasis Mukherjee
  • Re: Unsubscribe Lisa N. Cao
  • Re: Unsubscribe Subhasis Mukherjee
  • Unsubscribe Subhasis Mukherjee
  • Fwd: Unsubscribe Subhasis Mukherjee
  • Re: Unsubscribe Subhasis Mukherjee
  • Fwd: Unsubscribe Subhasis Mukherjee
  • Fwd: Unsubscribe Subhasis Mukherjee
  • Re: Unsubscribe Subhasis Mukherjee
  • Re: Unsubscribe Subhasis Mukherjee
  • Re: Unsubscribe Subhasis Mukherjee
  • Re: Unsubscribe Subhasis Mukherjee
  • Re: Unsubscribe Chandra Sekar Narayanan
  • Re: Unsubscribe Nicholas Chammas
  • unsubscribe David Frank via dev
  • unsubscribe Xianzhe Ma via dev
• Re: [VOTE] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Mridul Muralidharan
  • Re: [VOTE] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Mridul Muralidharan
  • Re: [VOTE] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Dongjoon Hyun
  • Re: [VOTE] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Jungtaek Lim
  • Re: [VOTE] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Jungtaek Lim
  • Re: [VOTE] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Jungtaek Lim
  • Re: [VOTE] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Jungtaek Lim
  • Re: [VOTE] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Dongjoon Hyun
  • Re: [VOTE] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Jungtaek Lim
  • Re: [VOTE] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Jungtaek Lim
  • Re: [VOTE] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Jungtaek Lim
  • Re: [VOTE] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Jungtaek Lim
  • Re: [VOTE] Retain migration logic of incorrect `spark.databricks.*` configuration in Spark 4.0.x Jungtaek Lim

• Later messages