Given the many +1's here, I've moved the PR to deprecate 3.4 to "ready for
review", https://github.com/apache/iceberg/pull/14099

> Does it mean we will stop back-porting PRs to Spark 3.4 for 1.11?

Not necessarily. There's a lot of Spark 3.4 backports already,
https://github.com/apache/iceberg/commits/main/spark/v3.4
I suggest we continue to backport for consistency and then stop right after
the 1.11 release.

Best,
Kevin Liu

On Fri, Sep 19, 2025 at 6:18 AM Amogh Jahagirdar <[email protected]> wrote:

> +1
>
> On Fri, Sep 19, 2025 at 2:03 AM Péter Váry <[email protected]>
> wrote:
>
>> +1
>>
>> Eduard Tudenhöfner <[email protected]> ezt írta (időpont: 2025.
>> szept. 19., P, 8:56):
>>
>>> +1 on deprecating Spark 3.4
>>>
>>> On Thu, Sep 18, 2025 at 8:36 AM Steve <[email protected]> wrote:
>>>
>>>> +1
>>>>
>>>> On Wed, Sep 17, 2025 at 22:52 Jean-Baptiste Onofré <[email protected]>
>>>> wrote:
>>>>
>>>>> +1
>>>>>
>>>>> I agree about the plan to "announce" the deprecation in 1.11 and
>>>>> remove 1.12, it gives time for users to "adapt".
>>>>>
>>>>> Regards
>>>>> JB
>>>>>
>>>>> On Wed, Sep 17, 2025 at 10:31 PM Kevin Liu <[email protected]>
>>>>> wrote:
>>>>> >
>>>>> > Hi everyone,
>>>>> >
>>>>> > I’d like to bring up the topic of deprecating Spark 3.4 in an
>>>>> upcoming release. Anton initially suggested this during our previous dev
>>>>> list discussion about maintaining feature parity across the Spark versions
>>>>> we support for 1.10.
>>>>> >
>>>>> > Currently, we support two different Spark 3.x versions, 3.4 and 3.5.
>>>>> Spark 3.4’s last maintenance release was in October 2024, and it is now
>>>>> considered end-of-life.
>>>>> >
>>>>> > What are your thoughts on marking Spark 3.4 as deprecated in 1.11
>>>>> and removing it in 1.12?
>>>>> >
>>>>> > For reference, here's the previous discussion thread on deprecating
>>>>> Spark 3.3.
>>>>> >
>>>>> > Best,
>>>>> >
>>>>> > Kevin Liu
>>>>>
>>>>

Reply via email to