You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Dmitriy Setrakyan <ds...@apache.org> on 2015/07/15 02:18:43 UTC

queue and set configuration

Igniters,

Do we still require configuring cache name for queues and sets? I thought
that we don't have that anymore. In that case, the documentation is wrong.

Can someone responsible for this fix update the documentation?

D.

Re: queue and set configuration

Posted by Yakov Zhdanov <yz...@gridgain.com>.
as well as in 1.1

--
Yakov Zhdanov, Director R&D
*GridGain Systems*
www.gridgain.com

2015-07-15 11:35 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:

> On Wed, Jul 15, 2015 at 1:34 AM, Yakov Zhdanov <yz...@apache.org>
> wrote:
>
> > Updated.
> >
>
> Was it updated in 1.2 and 1.3 versions?
>
>
> >
> > --Yakov
> >
> > 2015-07-15 3:18 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:
> >
> > > Igniters,
> > >
> > > Do we still require configuring cache name for queues and sets? I
> thought
> > > that we don't have that anymore. In that case, the documentation is
> > wrong.
> > >
> > > Can someone responsible for this fix update the documentation?
> > >
> > > D.
> > >
> >
>

Re: queue and set configuration

Posted by Dmitriy Setrakyan <ds...@apache.org>.
On Wed, Jul 15, 2015 at 1:34 AM, Yakov Zhdanov <yz...@apache.org> wrote:

> Updated.
>

Was it updated in 1.2 and 1.3 versions?


>
> --Yakov
>
> 2015-07-15 3:18 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:
>
> > Igniters,
> >
> > Do we still require configuring cache name for queues and sets? I thought
> > that we don't have that anymore. In that case, the documentation is
> wrong.
> >
> > Can someone responsible for this fix update the documentation?
> >
> > D.
> >
>

Re: queue and set configuration

Posted by Yakov Zhdanov <yz...@apache.org>.
Updated.

--Yakov

2015-07-15 3:18 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:

> Igniters,
>
> Do we still require configuring cache name for queues and sets? I thought
> that we don't have that anymore. In that case, the documentation is wrong.
>
> Can someone responsible for this fix update the documentation?
>
> D.
>