Hi,
Any update on the issue?
On 11 July 2017 at 16:01, chapurlatn wrote:
> Sorry if the message appears twice.
> I figured out my account was not ready to post when I send my first message
> :
>
> Hi,
>
> I think the scheduler processor does not match the expected processor
> interface. This re
* Do Stuff! */
}
catch { case e:Exception => Logger.error("I poked, I failed!", e) }
}, "* * * * *")}
Thanks,
R
On 7 June 2017 at 16:01, Alexey Goncharuk
wrote:
> Hi Raul,
>
> Do you observe this exception under some specific events, like topo
Hi,
We are trying to deploy a service as cluster singleton in our environment.
We are using ignite scheduler as a cron for this purpose, however we are
getting NPE for ignite version 2.0.0, hence unable to proceed with our
version upgrade. Below is the log information for the exception.
Environme
>
> Hi,
>
> I am trying to work out what the best approach would be for the following
> problem?
>
> Conditions:
>
>1. You have a river of data flowing at a varying rate into a cache,
>the cache holds the last N minuets of data.
>2. The river of data has to be analyzed as fast as possib
Hi,
Could you please paste the OSGi imports of the bundle that contains the
Activator?
Could you also post a full stacktrace?
Thanks.
On 3 Nov 2016 19:31, "Denis Magda" wrote:
> *Raul*, could you assist with this issue?
>
> —
> Denis
>
> On Nov 3, 2016, at 8:3
Auto flush / flushing is a characteristic of all streamers, that's why you
won't find it explained explicitly in the docs of specific streamers, but
in the general streamer one.
If I understand correctly, flushing controls when the changes in the
streamer will be sent to the grid (can someone conf
Hi,
I see you're using clientMode=true.
Could you try setting a low autoFlushFrequency on the streamer, say of
value 1 (ms)?
dataStreamer.autoFlushFrequency(1);
Cheers,
Raúl.
Support,
Given the following:
Background:
JBoss ESB 4.12(JMS messaging)
Apache Ignite 1.5 final
1. To begin,
On Thu, Mar 3, 2016 at 6:02 PM, Dmitriy Setrakyan
wrote:
> Raul, Yes to both questions.
>
Great, do we state it in the website? I think I might have missed it.
*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http:
Incidentally,
1. Do we *fully* implement the JSR-107 specification?
2. Can we assert that we fully pass the TCK, and that we satisfy the
requirements referenced by the the license in this regard?
@Edward – thanks for passing on the message from your legal dept.
Cheers,
Raúl.
On Thu, Mar 3, 2016
Ultimately it depends on the architecture of your application or use case.
If you are considering deploying a set of "central" or dedicated Ignite
nodes, it makes little sense to embed Ignite into an app on those nodes –
you may run it standalone.
If your architecture is fully decentralised, you ca
Yep, although this is not a message-oriented pattern, but rather a RPC call
and an implementation of the "Command Message" integration pattern.
I was under the impression that the OP wanted to send message/data across,
not necessarily invoke a discrete action per message type...
@kcheng – when I
Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Thu, Jan 7, 2016 at 12:32 PM, Raul Kripalani wrote:
> Take into account that Ignite topics, by nature, are a broadcast channel,
> which means that
On Mon, Dec 28, 2015 at 4:58 PM, Nikita Ivanov wrote:
> Pretty cool indeed. Does it basically use GitHub APIs underneath for the
> stats?
>
It clones the Git repo and runs its own analytics to my knowledge.
Regards,
*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration,
Hey guys,
I took some time to configure our project on OpenHub and we're now live
with analytics!
https://www.openhub.net/p/apache-ignite
Regards,
*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http:/
Hello users, Hello team!
The Apache Ignite PMC is pleased to announce that the project now has an
official chatroom on Gitter: https://gitter.im/apacheignite/ignite.
Come join us there! All you need is a Github account.
We've updated the Ignite website accordingly:
https://ignite.apache.org/comm
Correct. In unit tests we normally use
IgniteDataStreamer.autoFlushFrequency(10) to decrease the flush period to
10ms.
Maybe try to do the same to discard a flushing problem – like Valentin
suggested.
*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messa
Did you try setting the Streamer's allowOverwrite option?
It would be interesting to see your code for further help.
Regards,
Raúl.
On 13 Oct 2015 09:02, "Andrew" wrote:
> Hi, all.
>
> I'm new to Ignite, and testing write behind with data streamer.
> I made a cache using write-behind and then p
17 matches
Mail list logo
