ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Valentin Kulichenko <valentin.kuliche...@gmail.com>
Subject Re: IGNITE-1192 Implementation (Integration with Spring Data)
Date Mon, 08 Aug 2016 21:06:35 GMT
Eduard,

It's up to you :) I'm just saying that we should split the big task into
smaller ones.

-Val

On Mon, Aug 8, 2016 at 3:57 AM, Eduard Shangareev <
eduard.shangareev@gmail.com> wrote:

> Hi, Valentin.
> I am going to close these ticket with some prototype and create new ones
> (maybe, with umbrella one).
>
> Will it work?
>
> On Sat, Aug 6, 2016 at 8:03 AM, Valentin Kulichenko <
> valentin.kulichenko@gmail.com> wrote:
>
> > Hi Eduard,
> >
> > This is too much information :)
> >
> > I think you should create separate tickets for different aspects of
> Spring
> > Data integration and use IGNITE-1192 only as an umbrella, because
> otherwise
> > it will be flooded by comments. This will allow to implement this
> > functionality step by step and track the progress better.
> >
> > Agree?
> >
> > -Val
> >
> > On Fri, Aug 5, 2016 at 4:17 AM, Eduard Shangareev <
> > eduard.shangareev@gmail.com> wrote:
> >
> > > So there is no async support for query, therefore we can't support
> > futures
> > > as return type (paragraph 2).
> > >
> > > On Thu, Aug 4, 2016 at 6:08 PM, Eduard Shangareev <
> > > eduard.shangareev@gmail.com> wrote:
> > >
> > > > I have looked at Querydsl and QbE and I think their support should be
> > > > postponed.
> > > >
> > >
> >
>

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