ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: Why SQL_PUBLIC is appending to Cache name while using JDBC thin driver
Date Mon, 09 Oct 2017 18:21:45 GMT
On Mon, Oct 9, 2017 at 1:27 AM, Vladimir Ozerov <vozerov@gridgain.com>
wrote:

> Hi Dima,
>
> To maintain unique cache names across the cluster.
>

Why not simply check for uniqueness at creation time? Why introduce some
automatic prefix?


>
> On Mon, Oct 9, 2017 at 7:34 AM, Dmitriy Setrakyan <dsetrakyan@apache.org>
> wrote:
>
> > Cross-sending to dev@
> >
> > Why do we need to append SQL_PUBLIC_ to all table names?
> >
> > D.
> >
> > ---------- Forwarded message ----------
> > From: Denis Magda <dmagda@gridgain.com>
> > Date: Sun, Oct 8, 2017 at 7:01 AM
> > Subject: Re: Why SQL_PUBLIC is appending to Cache name while using JDBC
> > thin driver
> > To: "user@ignite.apache.org" <user@ignite.apache.org>
> >
> >
> > Hi Austin,
> >
> > Yes, it will be possible to pass a cache name you like into CREATE TABLE
> > command in 2.3. The release should be available in a couple of weeks.
> > Follow our announcements.
> >
> > Denis
> >
> >
> > On Saturday, October 7, 2017, austin solomon <
> austin.solomon007@gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > > I am using Ignite version 2.2.0, and I have created a table using
> > > IgniteJdbcThinDriver.
> > >
> > > When I checked the cache in Ignite Visor I'm seeing
> > SQL_PUBLIC_{TABLE-NAME}
> > > is appended.
> > > Is their a way to get rid of this.
> > >
> > > I want to remove the SQL_PUBLIC from the cache name.
> > >
> > > Thanks,
> > > Austin
> > >
> > >
> > >
> > > --
> > > Sent from: http://apache-ignite-users.70518.x6.nabble.com/
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message