+1 (non-binding)

On Wed, Sep 24, 2025 at 8:04 AM Cheng Pan <[email protected]> wrote:

> +1 (non-binding)
>
> To Nimrod and Mich,
>
> From my understanding, the JDBC API is already a good and de facto
> abstraction layer for user to connect to the different database services
> to execute SQL, the Hive JDBC driver and the proposed Connect JDBC driver
> will use a different package name and can coexist under user's application
> classpath, the right driver will be selected automatically according to
> user provided JDBC URL, given that, I don't see much value to create an
> unified JDBC dirver that support both, this has a few benefits (stripe
> one dependency from user classpath?) but involves much efforts.
>
> Thanks,
> Cheng Pan
>
>
>
> On Sep 24, 2025, at 12:12, Jules Damji <[email protected]> wrote:
>
> +1 (non-binding)
> —
> Sent from my iPhone
> Pardon the dumb thumb typos :)
>
> On Sep 23, 2025, at 3:03 AM, Ruifeng Zheng <[email protected]> wrote:
>
> 
> +1
>
> On Tue, Sep 23, 2025 at 5:13 PM Yang Jie <[email protected]> wrote:
>
>> +1
>>
>> Jie Yang
>>
>> On 2025/09/23 05:04:14 Fu Chen wrote:
>> > +1
>> >
>> > On 2025/09/22 13:04:37 杨杰 wrote:
>> > > Hi Spark devs,
>> > >
>> > > I would like to start a vote on the SPIP: JDBC Driver for Spark
>> Connect
>> > >
>> > > Discussion thread:
>> > > https://lists.apache.org/thread/rx5pqh01c86slpqv9161hqwgm5lwxxzq
>> > > SPIP:
>> > >
>> https://docs.google.com/document/d/1Ahk4C16o1Jj1TbLg5ylzgHjvu2Ic2zTrcMuvLjqSoAQ/edit?tab=t.0#heading=h.1gf0bimgty0t
>> > > JIRA: https://issues.apache.org/jira/browse/SPARK-53484
>> > >
>> > > Please vote on the SPIP for the next 72 hours:
>> > >
>> > > [ ] +1: Accept the proposal as an official SPIP
>> > > [ ] +0
>> > > [ ] -1: I don’t think this is a good idea because
>> > >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe e-mail: [email protected]
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe e-mail: [email protected]
>>
>>
>

Reply via email to