Sending stats back to Jetty after split

[Asaf Mesika <as...@gmail.com>]

Hi,

I have a Jetty end-point which I consume (hope I'm getting the right
terminology, still I'm still learning this) - meaning it's acting as a
server accepting a POST request containing lines separated by a new-line.

I then have a streaming splitter based on new line, and then a parse-json
processor which parses the line as JSON. After that I'm sending it to a
direct end-point (which is another route).

I would like to send back stats as a response, including the number of
lines which failed parsing.

I couldn't find a way to to relay this stats from the parse-json processor
back to the original exchange which left the Jetty end-point.
Any idea?


Question 2:

I would like to extend the splitter to have a max line length, thus if
someone send 10 lines, but the 3rd is 2 mb long, then it will gracefully
skipped.
Does it exists some where other than the main camel repo?

If I would like to commit this feature back, what is the exact process I
should follow?

Thanks!

Asaf

Fwd: Sending stats back to Jetty after split

[Asaf Mesika <as...@gmail.com>]

Forwarded from the dev mailing list.

Appreciate any experienced advice / help on this question!

Thanks!

---------- Forwarded message ----------
From: Asaf Mesika <as...@gmail.com>
Date: Thu, Sep 24, 2015 at 6:17 PM
Subject: Re: Sending stats back to Jetty after split
To: "dev@camel.apache.org" <de...@camel.apache.org>


 if I will receive 10,000 messages, this strategy forces me to wait for all
of them instead of streaming them to the direct end point, thus rendering
the streaming feature of the splitter useless?


On Thursday, 24 September 2015, Claus Ibsen <cl...@gmail.com> wrote:

> The splitter supports an aggregation strategy where you can build a
> repsonse object with the splitted messages.
>
> See splitter only example on
> http://camel.apache.org/composed-message-processor.html
>
> On Thu, Sep 24, 2015 at 3:59 PM, Asaf Mesika <as...@gmail.com>
> wrote:
> > Hi,
> >
> > I have a Jetty end-point which I consume (hope I'm getting the right
> > terminology, still I'm still learning this) - meaning it's acting as a
> > server accepting a POST request containing lines separated by a new-line.
> >
> > I then have a streaming splitter based on new line, and then a parse-json
> > processor which parses the line as JSON. After that I'm sending it to a
> > direct end-point (which is another route).
> >
> > I would like to send back stats as a response, including the number of
> > lines which failed parsing.
> >
> > I couldn't find a way to to relay this stats from the parse-json
> processor
> > back to the original exchange which left the Jetty end-point.
> > Any idea?
> >
> >
> > Question 2:
> >
> > I would like to extend the splitter to have a max line length, thus if
> > someone send 10 lines, but the 3rd is 2 mb long, then it will gracefully
> > skipped.
> > Does it exists some where other than the main camel repo?
> >
> > If I would like to commit this feature back, what is the exact process I
> > should follow?
> >
> > Thanks!
> >
> > Asaf
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2nd edition: https://www.manning.com/books/ibsen2
>

Re: Sending stats back to Jetty after split

[Asaf Mesika <as...@gmail.com>]

 if I will receive 10,000 messages, this strategy forces me to wait for all
of them instead of streaming them to the direct end point, thus rendering
the streaming feature of the splitter useless?


On Thursday, 24 September 2015, Claus Ibsen <cl...@gmail.com> wrote:

> The splitter supports an aggregation strategy where you can build a
> repsonse object with the splitted messages.
>
> See splitter only example on
> http://camel.apache.org/composed-message-processor.html
>
> On Thu, Sep 24, 2015 at 3:59 PM, Asaf Mesika <asaf.mesika@gmail.com
> <javascript:;>> wrote:
> > Hi,
> >
> > I have a Jetty end-point which I consume (hope I'm getting the right
> > terminology, still I'm still learning this) - meaning it's acting as a
> > server accepting a POST request containing lines separated by a new-line.
> >
> > I then have a streaming splitter based on new line, and then a parse-json
> > processor which parses the line as JSON. After that I'm sending it to a
> > direct end-point (which is another route).
> >
> > I would like to send back stats as a response, including the number of
> > lines which failed parsing.
> >
> > I couldn't find a way to to relay this stats from the parse-json
> processor
> > back to the original exchange which left the Jetty end-point.
> > Any idea?
> >
> >
> > Question 2:
> >
> > I would like to extend the splitter to have a max line length, thus if
> > someone send 10 lines, but the 3rd is 2 mb long, then it will gracefully
> > skipped.
> > Does it exists some where other than the main camel repo?
> >
> > If I would like to commit this feature back, what is the exact process I
> > should follow?
> >
> > Thanks!
> >
> > Asaf
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2nd edition: https://www.manning.com/books/ibsen2
>

Re: Sending stats back to Jetty after split

[Claus Ibsen <cl...@gmail.com>]

The splitter supports an aggregation strategy where you can build a
repsonse object with the splitted messages.

See splitter only example on
http://camel.apache.org/composed-message-processor.html

On Thu, Sep 24, 2015 at 3:59 PM, Asaf Mesika <as...@gmail.com> wrote:
> Hi,
>
> I have a Jetty end-point which I consume (hope I'm getting the right
> terminology, still I'm still learning this) - meaning it's acting as a
> server accepting a POST request containing lines separated by a new-line.
>
> I then have a streaming splitter based on new line, and then a parse-json
> processor which parses the line as JSON. After that I'm sending it to a
> direct end-point (which is another route).
>
> I would like to send back stats as a response, including the number of
> lines which failed parsing.
>
> I couldn't find a way to to relay this stats from the parse-json processor
> back to the original exchange which left the Jetty end-point.
> Any idea?
>
>
> Question 2:
>
> I would like to extend the splitter to have a max line length, thus if
> someone send 10 lines, but the 3rd is 2 mb long, then it will gracefully
> skipped.
> Does it exists some where other than the main camel repo?
>
> If I would like to commit this feature back, what is the exact process I
> should follow?
>
> Thanks!
>
> Asaf



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2nd edition: https://www.manning.com/books/ibsen2