For future reference: This bug does not appear anymore in 1.1.0
On Fri, Dec 15, 2017 at 3:25 PM, Rob Verkuylen wrote:
> Hi,
>
> After upgrading to 1.0 we're getting strange producer/broker behaviour not
> experienced on <1.0.
>
> As a test we run a single threaded producer just sending "TEST" ag
I had a similar use case of joining two streams with windows spanning days.
That didn't work out well.
For you, this approach might work better:
1. Stream Trades and put it in a Key/Value store like (Aerospike).
2. Stream Risks and in the map function you can join it with key saved in
Aerospike.
Yes you can. Since you are gonna have 2 plaintext ports you would need to
name them differently. In the broker's configuration (server.properties)
you would need to specify listeners like this:
listeners=PLAINTEXT1://:9092,PLAINTEXT2://:9093
And map the "PLAINTEXT1" and "PLAINTEXT2" to the PLAINT
Hi Damian,
thank you for the informative reply.I think this answers 95% of my
questions (or maybe 100% and I missed the explanation).
what is still unresolved is how to handle trades and risks that arrive far
apart.
Suppose we have
timeToAllowAJoin = 10 seconds
and we have
Time | Trade
Karthick,
I am suspecting that it could be the log4j.properties in your webapp is not
picked up by Tomcat, or somehow Tomcat is overriding your webapp's log4j
setup.
On Tue, May 15, 2018 at 2:19 AM, Karthick Kumar
wrote:
> Hi Andras/Kaufman,
>
> I have tried both logger properties, But it is no
