You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Alexey Kuznetsov <ak...@gridgain.com> on 2015/01/14 10:03:14 UTC
Third party JDBC drivers for schema load utility
Hi All!
I'm working on small GUI utility Schema load (see IGNITE-32 issue
<https://issues.apache.org/jira/browse/IGNITE-32>).
And for users usability it will be nice to provide JDBC drivers for most
popular databases (Oracle, DB2, MS SQL, ...).
But I'm afraid that providing proprietary software as part of Apache
download will violate Apache rules.
We could provide the file with collection of download links, but manual
download is inconvenient for end-user.
Please advice how we could handle this?
--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com
Re: Third party JDBC drivers for schema load utility
Posted by Dmitriy Setrakyan <ds...@gridgain.com>.
I like this approach. Alexey K., what do you think?
D.
On Wed, Jan 14, 2015 at 12:00 PM, Konstantin Boudnik <co...@apache.org> wrote:
> Yup.
>
> An ASF release is essentially a source code: signed and tagged back to a
> certain revision in the source code tree. Including binaries as a part of
> the
> release is frown upon as binaries can not be reviewed during the vote
> process,
> hence one can not guarantee the content of the release. That's esp. true
> with
> 3rd party, proprietary stuff.
>
> A nice and user-friendly way around it would be to provide a mechanism for
> a
> user to download the drivers without even leaving the UI application in
> question. Do you think it might work in your case?
>
> Cos
>
> On Wed, Jan 14, 2015 at 01:59PM, Vladimir Ozerov wrote:
> > I don't think that shipping drivers is a good idea for the following
> > reasons (skipping already mentioned licensing problems):
> >
> > 1) Some drivers targeting specific databse version.
> > 2) There could be different types of JDBC drivers available for the same
> > database (e.g. JDBC3, JDBC4, alternate implementations, etc.).
> > 3) Some drivers require installation (e.g. MS SQL requires some DLLs to
> be
> > placed in specific folder).
> > 4) We would have to bother with updating drivers along with their new
> > version releases.
> >
> > It shouldn't be a problem for a user to setup a JDBC driver manually as
> > virtually any developer knows how to do that.
> >
> > Vladimir.
> >
> > On Wed, Jan 14, 2015 at 1:03 PM, Alexey Kuznetsov <
> akuznetsov@gridgain.com>
> > wrote:
> >
> > > Hi All!
> > >
> > > I'm working on small GUI utility Schema load (see IGNITE-32 issue
> > > <https://issues.apache.org/jira/browse/IGNITE-32>).
> > >
> > > And for users usability it will be nice to provide JDBC drivers for
> most
> > > popular databases (Oracle, DB2, MS SQL, ...).
> > >
> > > But I'm afraid that providing proprietary software as part of Apache
> > > download will violate Apache rules.
> > >
> > > We could provide the file with collection of download links, but manual
> > > download is inconvenient for end-user.
> > >
> > > Please advice how we could handle this?
> > >
> > > --
> > > Alexey Kuznetsov
> > > GridGain Systems
> > > www.gridgain.com
> > >
>
Re: Third party JDBC drivers for schema load utility
Posted by Konstantin Boudnik <co...@apache.org>.
Yup.
An ASF release is essentially a source code: signed and tagged back to a
certain revision in the source code tree. Including binaries as a part of the
release is frown upon as binaries can not be reviewed during the vote process,
hence one can not guarantee the content of the release. That's esp. true with
3rd party, proprietary stuff.
A nice and user-friendly way around it would be to provide a mechanism for a
user to download the drivers without even leaving the UI application in
question. Do you think it might work in your case?
Cos
On Wed, Jan 14, 2015 at 01:59PM, Vladimir Ozerov wrote:
> I don't think that shipping drivers is a good idea for the following
> reasons (skipping already mentioned licensing problems):
>
> 1) Some drivers targeting specific databse version.
> 2) There could be different types of JDBC drivers available for the same
> database (e.g. JDBC3, JDBC4, alternate implementations, etc.).
> 3) Some drivers require installation (e.g. MS SQL requires some DLLs to be
> placed in specific folder).
> 4) We would have to bother with updating drivers along with their new
> version releases.
>
> It shouldn't be a problem for a user to setup a JDBC driver manually as
> virtually any developer knows how to do that.
>
> Vladimir.
>
> On Wed, Jan 14, 2015 at 1:03 PM, Alexey Kuznetsov <ak...@gridgain.com>
> wrote:
>
> > Hi All!
> >
> > I'm working on small GUI utility Schema load (see IGNITE-32 issue
> > <https://issues.apache.org/jira/browse/IGNITE-32>).
> >
> > And for users usability it will be nice to provide JDBC drivers for most
> > popular databases (Oracle, DB2, MS SQL, ...).
> >
> > But I'm afraid that providing proprietary software as part of Apache
> > download will violate Apache rules.
> >
> > We could provide the file with collection of download links, but manual
> > download is inconvenient for end-user.
> >
> > Please advice how we could handle this?
> >
> > --
> > Alexey Kuznetsov
> > GridGain Systems
> > www.gridgain.com
> >
Re: Third party JDBC drivers for schema load utility
Posted by Vladimir Ozerov <vo...@gridgain.com>.
I don't think that shipping drivers is a good idea for the following
reasons (skipping already mentioned licensing problems):
1) Some drivers targeting specific databse version.
2) There could be different types of JDBC drivers available for the same
database (e.g. JDBC3, JDBC4, alternate implementations, etc.).
3) Some drivers require installation (e.g. MS SQL requires some DLLs to be
placed in specific folder).
4) We would have to bother with updating drivers along with their new
version releases.
It shouldn't be a problem for a user to setup a JDBC driver manually as
virtually any developer knows how to do that.
Vladimir.
On Wed, Jan 14, 2015 at 1:03 PM, Alexey Kuznetsov <ak...@gridgain.com>
wrote:
> Hi All!
>
> I'm working on small GUI utility Schema load (see IGNITE-32 issue
> <https://issues.apache.org/jira/browse/IGNITE-32>).
>
> And for users usability it will be nice to provide JDBC drivers for most
> popular databases (Oracle, DB2, MS SQL, ...).
>
> But I'm afraid that providing proprietary software as part of Apache
> download will violate Apache rules.
>
> We could provide the file with collection of download links, but manual
> download is inconvenient for end-user.
>
> Please advice how we could handle this?
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>