Mailing-List: contact user-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <1503095698101-16310.post@n6.nabble.com>
References: <1502402902313-16113.post@n6.nabble.com> <CAFkXquTUp1wS-e00Tyjxu+fnQfA7J5bCuxdJv1tOVd6BeRV8LA@mail.gmail.com>
 <1502755776904-16188.post@n6.nabble.com> <1502757029571-16189.post@n6.nabble.com>
 <CAFkXquSdSXqYMKSXcqb0-4ZX-azfPCnUjV3R7crG69qG8GeBMQ@mail.gmail.com>
 <CAFkXquRUgpctrgW-SeOtcgfht0hG5DZYtQeKbtPniSdfi2rUkw@mail.gmail.com>
 <1502843336640-16213.post@n6.nabble.com> <CAFkXquSrcBCWY4hMnr=w5BE8BKvTr5UJLZA2-r52yZmhD34cdw@mail.gmail.com>
 <1503010596265-16270.post@n6.nabble.com> <CAFkXquSKrBzJGBfpcas2NyzAH4D2bG97STG4u6_N4Zn-L33uQA@mail.gmail.com>
 <1503095698101-16310.post@n6.nabble.com>
From: Jessie Lin <jessie.jianwei.lin@gmail.com>
Date: Fri, 18 Aug 2017 17:13:02 -0700
Message-ID: <CAFkXquTV1FHjUSVxH4UNPzzRLPUXbJu8OFG-ouC+hDEorbT=0g@mail.gmail.com>
Subject: Re: Streaming test
To: user@ignite.apache.org
Content-Type: multipart/alternative; boundary="001a114476ccf12fd20557101bf7"
archived-at: Sat, 19 Aug 2017 00:13:16 -0000

--001a114476ccf12fd20557101bf7
Content-Type: text/plain; charset="UTF-8"

Hi Val, thank you getting back.  The source type will be different, and the
client will deal with the difference in a preprocess that's unique to that
data source. Once that's done, it'll be ready for a standard
transformation. So we can encapsulate it in a single service or callable.

Thanks for explaining the difference between client and servers. It
clarifies things and make sense.
We wanted to build different type of clients to accommodate the differences
in the data sources.

Does this make sense? what kind of solutions would you suggest?

Jessie


On Fri, Aug 18, 2017 at 3:34 PM, vkulichenko <valentin.kulichenko@gmail.com>
wrote:

> If data sources are different, then transformations are different as well,
> no? If so, how are you going to encapsulate them in a single service? I
> would really appreciate a concrete example, it might make this much easier.
> I'm probably missing something now.
>
> Difference between clients and servers is the same is in other systems.
> Servers store data, run services and computations, etc. while clients are
> only used to interact with the cluster.
>
> -Val
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Streaming-test-tp14039p16310.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

--001a114476ccf12fd20557101bf7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Val, thank you getting back.=C2=A0 The source type will=
 be different, and the client will deal with the difference in a preprocess=
 that&#39;s unique to that data source. Once that&#39;s done, it&#39;ll be =
ready for a standard transformation. So we can encapsulate it in a single s=
ervice or callable.<div><br></div><div>Thanks for explaining the difference=
 between client and servers. It clarifies things and make sense.</div><div>=
We wanted to build different type of clients to accommodate the differences=
 in the data sources.</div><div><br></div><div>Does this make sense? what k=
ind of solutions would you suggest?</div><div><br></div><div>Jessie</div><d=
iv><br></div><div><br></div></div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Fri, Aug 18, 2017 at 3:34 PM, vkulichenko <span dir=3D"=
ltr">&lt;<a href=3D"mailto:valentin.kulichenko@gmail.com" target=3D"_blank"=
>valentin.kulichenko@gmail.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">If data sources are different, then transformations are diffe=
rent as well,<br>
no? If so, how are you going to encapsulate them in a single service? I<br>
would really appreciate a concrete example, it might make this much easier.=
<br>
I&#39;m probably missing something now.<br>
<br>
Difference between clients and servers is the same is in other systems.<br>
Servers store data, run services and computations, etc. while clients are<b=
r>
only used to interact with the cluster.<br>
<br>
-Val<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href=3D"http://apache-ignite-users.70518.x=
6.nabble.com/Streaming-test-tp14039p16310.html" rel=3D"noreferrer" target=
=3D"_blank">http://apache-ignite-users.<wbr>70518.x6.nabble.com/Streaming-<=
wbr>test-tp14039p16310.html</a><br>
<div class=3D"HOEnZb"><div class=3D"h5">Sent from the Apache Ignite Users m=
ailing list archive at Nabble.com.<br>
</div></div></blockquote></div><br></div>

--001a114476ccf12fd20557101bf7--