kes sense to provide a runtime Jar.
>>>>>>
>>>>>> I could be convinced otherwise, but I'm skeptical.
>>>>>>
>>>>>> Ryan
>>>>>>
>>>>>> On Tue, Dec 7, 2021 at 7:52 PM Jack Ye wrote:
&
t;>> releasing Nessie and AWS modules in
>>>>>> https://github.com/apache/iceberg/issues/1887. In summary:
>>>>>>
>>>>>> 1. The iceberg- package is always added to the engine
>>>>>> runtimes to avoid the need for users to load them ma
gt;> Otherwise
>>>>> the vendor dependencies are marked as provided and not bundled in the
>>>>> runtime jar.
>>>>>
>>>>> However, Aliyun is proposing a different approach, which:
>>>>> 1. Does not include th
cies, so user just need to specify 1 additional jar to
>>>> use the vendor
>>>>
>>>> AWS did not choose the approach proposed by Aliyun because AWS users
>>>> usually maintain their own version of AWS SDK and would like to upgrade
>>>> the
proach proposed by Aliyun because AWS users
>>> usually maintain their own version of AWS SDK and would like to upgrade
>>> them independent of the AWS SDK version used by Iceberg. Although currently
>>> it takes more effort for users to specify all the compile-only
>
directly in the classpath to avoid such need in the very near
>> future, and EMR will maintain their AWS SDK version upgrade independently.
>>
>> But the approach proposed by Aliyun seems to fit the use case of Aliyun
>> users better. For more context, please read
>> ht
, and EMR will maintain their AWS SDK version upgrade independently.
>
> But the approach proposed by Aliyun seems to fit the use case of Aliyun
> users better. For more context, please read
> https://github.com/apache/iceberg/pull/3270 for the discussion between me
> and Openinx a
endor integration strategy going
forward. It could be we support both approaches, or just choose one
approach going forward. It would be great if people with similar experience
or need could provide some insights.
Best,
Jack Ye
