C++/.Net Module
Hello to all, I have a question about the new module: It will be possible to implement a cluster entirely made up of nodes in .net or C ++? Without the need for a JVM? Thank you, Regards, Gianfranco -- Gianfranco Murador Igniter and Software Engineer.
IGNITE-708
Hi Igniters, I 'm starting to implement this patch: Can you tell me if there is already a convenient method to see if the local cache was updated last time interval ? Regards, Gianfranco -- Gianfranco Murador Igniter and Software Engineer.
Re: API stability.
Hi Vladimir, I think it is better to use public APIs for creating plugis, imho Regards, Gianfranco. 2015-08-28 13:55 GMT+02:00 Vladimir Ozerov : > Igniters, > > We have several types of APIs: > 1) Public - intended for Ignite users. E.g.: IgniteCache. > 2) Private - used only by Ignite developers. E.g.: almost everything inside > "org.apache.ignite.internal". > 3) Semi-private - is not expected to be used by users, but can be used by > 3rd-party developers. E.g.: PluginProvider. > > I'd like to propose defining "stability" for p.3 type of APIs. That is. if > someone develops Ignite extensions, he might need to know what is the > probability of breaking change of that API. Nice example of such approach > is Hadoop APIs. > > The reason why I started thinking about it is "platforms" migration from > GridGain to Ignite. Currently our platforms API are far from ideal from > external developer's point of view. This was not a problem in GridGain > since the code was private, but it can become a problem in open-sourced > Ignite. > And instead of spending time on making APIs nice and clean I'd like to make > platforms work first. During this transition time it would be nice to mark > relevant APIs as "unstable" so that potential 3rd-party devs will be aware > of a risk when using them. > > Thoughts? > > Vladimir. >
Re: IGNITE-708
Hello Alexey,
I mean 'local partition map'. I am trying to investigate the issue, and in
fact,
I need some clarification about the ticket. From my understanding, It is
necessary to refresh the partitions (refreshPartitions())
only if the local partition is changed, or if a transaction has been made
on it. So if I understand I need to add logic and control
in the OnTimeOut method of the inner class . Is it correct ?
/** {@inheritDoc} */
@Override public void onTimeout() {
cctx.kernalContext().closure().runLocalSafe(new Runnable() {
@Override public void run() {
if (!busyLock.readLock().tryLock())
return;
try {
// onTimeOut we refresh always the partitions
if (started.compareAndSet(false, true))
refreshPartitions();
}
finally {
busyLock.readLock().unlock();
cctx.time().removeTimeoutObject(ResendTimeoutObject.this);
pendingResend.compareAndSet(ResendTimeoutObject.this, null);
}
}
});
}
Thank you, Regards, Gianfranco
2015-09-01 3:30 GMT+02:00 Dmitriy Setrakyan :
> On Mon, Aug 31, 2015 at 5:57 PM, Alexey Goncharuk <
> alexey.goncha...@gmail.com> wrote:
>
> > As far as I understood Yakov's point, even this message indicating that
> no
> > change happened is redundant because we have message delivery guarantees
> on
> > communication level and no messages can be lost. If a node is waiting
> for a
> > message and receives a message indicating that no change had happened, I
> am
> > not even sure how this node should react: it means that the message with
> an
> > important update somehow was not received (a bug in the code?) and the
> next
> > message indicates that no updates after the lost message were made.
> >
>
> I still would wait for a No-Change empty partition exchange message, rather
> than have no message at all (and wait for a timeout?).
>
> Yakov, can you please chime in and let us all know what you meant by that
> ticket?
>
>
> >
> > 2015-08-31 17:33 GMT-07:00 Dmitriy Setrakyan :
> >
> > > On Mon, Aug 31, 2015 at 4:58 PM, Alexey Goncharuk <
> > > alexey.goncha...@gmail.com> wrote:
> > >
> > > > Gianfranco,
> > > >
> > > > What do you mean by 'local cache' here?
> > > >
> > > > If you are talking about the local partition map, I do not think we
> > have
> > > > such a method. The background exchange that is described in the
> ticket
> > is
> > > > handled in controlled by the ResendTimeoutObject inner class in
> > > > GridCachePartitionExchangeManager. I cannot recall any cases when
> this
> > > > exchange would be needed from the top of my head, but it looks like
> you
> > > > need to do some investigation and code digging to check whether the
> > > > background exchange can be indeed safely removed :)
> > > >
> > >
> > > Alexey, I actually think that this ticket is named wrongly. After
> looking
> > > at the description, it seems that Yakov is suggesting that we do not
> send
> > > the exchange message if there are no changes to the exchange. Perhaps,
> we
> > > should be still sending something indicating that no change happened,
> > > otherwise, other nodes will hang forever waiting for the exchange to
> > > complete.
> > >
> > > Am I wrong in my understanding?
> > >
> > >
> > >
> > > >
> > > > 2015-08-28 5:58 GMT-07:00 Gianfranco Murador :
> > > >
> > > > > Hi Igniters,
> > > > > I 'm starting to implement this patch:
> > > > > Can you tell me if there is already a convenient method to see if
> the
> > > > local
> > > > > cache was updated last time interval ?
> > > > > Regards, Gianfranco
> > > > >
> > > > >
> > > > > --
> > > > > Gianfranco Murador
> > > > > Igniter and Software Engineer.
> > > > >
> > > >
> > >
> >
>
Re: IGNITE-708
Thank you , all.
2015-09-01 12:21 GMT+02:00 Yakov Zhdanov :
> In my view, Alex has 100% understanding on what is hapenning. Let's remove
> background exchange if partition map does not change. Gianfranco, I don't
> think you should account for transactions. Only updates to partition
> topology matters. Younger nodes should send local updates to the oldest.
> The oldest one should spread partitions after some delay buffering possible
> updates or similar messages from other nodes.
>
> Hope this helps!
> On Sep 1, 2015 11:14, "Gianfranco Murador"
> wrote:
>
> > Hello Alexey,
> > I mean 'local partition map'. I am trying to investigate the issue, and
> in
> > fact,
> > I need some clarification about the ticket. From my understanding, It is
> > necessary to refresh the partitions (refreshPartitions())
> > only if the local partition is changed, or if a transaction has been made
> > on it. So if I understand I need to add logic and control
> > in the OnTimeOut method of the inner class . Is it correct ?
> >
> > /** {@inheritDoc} */
> > @Override public void onTimeout() {
> > cctx.kernalContext().closure().runLocalSafe(new Runnable() {
> > @Override public void run() {
> > if (!busyLock.readLock().tryLock())
> > return;
> >
> > try {
> >// onTimeOut we refresh always the partitions
> > if (started.compareAndSet(false, true))
> > refreshPartitions();
> > }
> > finally {
> > busyLock.readLock().unlock();
> >
> > cctx.time().removeTimeoutObject(ResendTimeoutObject.this);
> >
> > pendingResend.compareAndSet(ResendTimeoutObject.this, null);
> > }
> > }
> > });
> > }
> >
> > Thank you, Regards, Gianfranco
> >
> > 2015-09-01 3:30 GMT+02:00 Dmitriy Setrakyan :
> >
> > > On Mon, Aug 31, 2015 at 5:57 PM, Alexey Goncharuk <
> > > alexey.goncha...@gmail.com> wrote:
> > >
> > > > As far as I understood Yakov's point, even this message indicating
> that
> > > no
> > > > change happened is redundant because we have message delivery
> > guarantees
> > > on
> > > > communication level and no messages can be lost. If a node is waiting
> > > for a
> > > > message and receives a message indicating that no change had
> happened,
> > I
> > > am
> > > > not even sure how this node should react: it means that the message
> > with
> > > an
> > > > important update somehow was not received (a bug in the code?) and
> the
> > > next
> > > > message indicates that no updates after the lost message were made.
> > > >
> > >
> > > I still would wait for a No-Change empty partition exchange message,
> > rather
> > > than have no message at all (and wait for a timeout?).
> > >
> > > Yakov, can you please chime in and let us all know what you meant by
> that
> > > ticket?
> > >
> > >
> > > >
> > > > 2015-08-31 17:33 GMT-07:00 Dmitriy Setrakyan >:
> > > >
> > > > > On Mon, Aug 31, 2015 at 4:58 PM, Alexey Goncharuk <
> > > > > alexey.goncha...@gmail.com> wrote:
> > > > >
> > > > > > Gianfranco,
> > > > > >
> > > > > > What do you mean by 'local cache' here?
> > > > > >
> > > > > > If you are talking about the local partition map, I do not think
> we
> > > > have
> > > > > > such a method. The background exchange that is described in the
> > > ticket
> > > > is
> > > > > > handled in controlled by the ResendTimeoutObject inner class in
> > > > > > GridCachePartitionExchangeManager. I cannot recall any cases when
> > > this
> > > > > > exchange would be needed from the top of my head, but it looks
> like
> > > you
> > > > > > need to do some investigation and code digging to check whether
> the
> > > > > > background exchange can be indeed safely removed :)
> > > > > >
> > > > >
> > > > > Alexey, I actually think that this ticket is named wrongly. After
> > > looking
> > > > > at the description, it seems that Yakov is suggesting that we do
> not
> > > send
> > > > > the exchange message if there are no changes to the exchange.
> > Perhaps,
> > > we
> > > > > should be still sending something indicating that no change
> happened,
> > > > > otherwise, other nodes will hang forever waiting for the exchange
> to
> > > > > complete.
> > > > >
> > > > > Am I wrong in my understanding?
> > > > >
> > > > >
> > > > >
> > > > > >
> > > > > > 2015-08-28 5:58 GMT-07:00 Gianfranco Murador >:
> > > > > >
> > > > > > > Hi Igniters,
> > > > > > > I 'm starting to implement this patch:
> > > > > > > Can you tell me if there is already a convenient method to see
> if
> > > the
> > > > > > local
> > > > > > > cache was updated last time interval ?
> > > > > > > Regards, Gianfranco
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Gianfranco Murador
> > > > > > > Igniter and Software Engineer.
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Anyone faced this issue while writing unit tests. Please help
Hi chandresh, What are you trying to achieve? It seems you have not set an appropriate dependencies in your project .What version of log4j are you using? Regards, Gianfranco 2015-09-15 12:54 GMT+02:00 chandresh pancholi < chandreshpancholi...@gmail.com>: > Hi Igniters, > > I am facing this issue and i guess i am missing some dependency. > Please help!! > junit.framework.AssertionFailedError: *Exception in constructor: > testStormStreamer (java.lang.NoSuchMethodError: > org.apache.log4j.Category.getParent()Lorg/apache/log4j/Category*; > at > > org.apache.ignite.testframework.junits.logger.GridTestLog4jLogger.addConsoleAppenderIfNeeded(GridTestLog4jLogger.java:325) > at > > org.apache.ignite.testframework.junits.logger.GridTestLog4jLogger.(GridTestLog4jLogger.java:136) > at > > org.apache.ignite.testframework.junits.logger.GridTestLog4jLogger.(GridTestLog4jLogger.java:117) > at > > org.apache.ignite.testframework.junits.GridAbstractTest.(GridAbstractTest.java:185) > at > > org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.(GridCommonAbstractTest.java:106) > at > > org.apache.ignite.stream.storm.StormIgniteStreamerSelfTest.(StormIgniteStreamerSelfTest.java:14) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:422) > at junit.framework.TestSuite.createTest(TestSuite.java:63) > at junit.framework.TestSuite.addTestMethod(TestSuite.java:310) > at junit.framework.TestSuite.addTestsFromTestCase(TestSuite.java:153) > at junit.framework.TestSuite.(TestSuite.java:132) > at > > org.apache.ignite.stream.storm.IgniteStormStreamerSelfTestSuite.suite(IgniteStormStreamerSelfTestSuite.java:14) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > > org.junit.internal.runners.SuiteMethod.testFromSuiteMethod(SuiteMethod.java:35) > at org.junit.internal.runners.SuiteMethod.(SuiteMethod.java:24) > at > > org.junit.internal.builders.SuiteMethodBuilder.runnerForClass(SuiteMethodBuilder.java:11) > at > > org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59) > at > > org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26) > at > > org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59) > at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:26) > at > > com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:41) > at > > com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:212) > at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:68) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140) > ) > junit.framework.AssertionFailedError: Exception in constructor: > testStormStreamer (java.lang.NoSuchMethodError: > org.apache.log4j.Category.getParent()Lorg/apache/log4j/Category; > at > > org.apache.ignite.testframework.junits.logger.GridTestLog4jLogger.addConsoleAppenderIfNeeded(GridTestLog4jLogger.java:325) > at > > org.apache.ignite.testframework.junits.logger.GridTestLog4jLogger.(GridTestLog4jLogger.java:136) > at > > org.apache.ignite.testframework.junits.logger.GridTestLog4jLogger.(GridTestLog4jLogger.java:117) > at > > org.apache.ignite.testframework.junits.GridAbstractTest.(GridAbstractTest.java:185) > at > > org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.(GridCommonAbstractTest.java:106) > at > > org.apache.ignite.stream.storm.StormIgniteStreamerSelfTest.(StormIgniteStreamerSelfTest.java:14) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:422) > at > > org.apache.ignite.stream.storm.IgniteStormStreamerSelfTestSuite.suite(IgniteStormStreamerSelfTestSuite.java:14) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > > sun.refl
Re: Brainstorming about Reactive Streams
Hy Raul, it could be a valid extension of the Service Grid of Ignite ( if I understand the point), imho. 2015-09-20 14:37 GMT+02:00 Raul Kripalani : > Hey Igniters, > > Lalit Kumar Jha expressed interest [1] in contributing to ticket IGNITE-815 > [2] which aims to bring in Reactive Streams to Ignite. > > I wanted to start a brainstorm about which functionalities we'd like to > cover. > > Off the top of my head, I can think of merging, filtering, sorting, > batching, grouping, etc. on Data Streams, Ignite Messages and Events. Also, > integration with Continuous Queries would be useful. > > Furthermore, I wanted to ask the community if at this point we feel > comfortable with Reactive Streams per-se or we prefer to go with RxJava for > now. Reactive Streams is a proposed standard whose main Java implementation > and is slowly gaining traction (e.g. vert.x [3] and MongoDB integrations > [4]), whereas RxJava is an already mature and production-tested > implementation of the initial ReactiveX design by Microsoft [5] with 7000+ > stars on GitHub. > > RxJava is the foundation of Hystrix [6], a powerful library for latency and > fault tolerance management. RxJava does not implement Reactive Streams as > of 1.x (as they predated it), but they've vowed support for 2.x [7]. > Moreover, there's already an adapter which passes the TCK [8]. > > My take is as follows. I'd like to follow the Reactive Streams standard, > but I wouldn't like to lose support for Hystrix (hopefully it'll eventually > be migrated to Reactive Streams too). So an option is to go with the RxJava > + adapter design for now to get the best of both worlds. Once RxJava 2.0 is > out, we can drop the adapter out of the picture. > > Thoughts? > > [1] > > http://apache-ignite-developers.2346864.n4.nabble.com/Hello-Apache-Ignite-Dev-tp3137p3315.html > [2] https://issues.apache.org/jira/browse/IGNITE-815 > [3] http://vertx.io/docs/vertx-reactive-streams/java/ > [4] https://mongodb.github.io/mongo-java-driver-reactivestreams/ > [5] https://msdn.microsoft.com/en-us/data/gg577609.aspx > [6] https://github.com/Netflix/Hystrix > [7] https://github.com/ReactiveX/RxJava/wiki/Reactive-Streams > [8] https://github.com/ReactiveX/RxJavaReactiveStreams > > Regards, > > *Raúl Kripalani* > Apache Camel PMC Member & Committer | Enterprise Architect, Open Source > Integration specialist > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani > http://blog.raulkr.net | twitter: @raulvk >
Re: After setting streamer and ignite,getting NULL
Please take look here.. https://cwiki.apache.org/confluence/display/IGNITE/Streamers+Implementation+Guidelines 2015-09-21 14:54 GMT+02:00 chandresh pancholi < chandreshpancholi...@gmail.com>: > Hi Gian/Vishal/Lalit, > > You guys have worked on Streamer integration with Ignite. I am working on > Storm-ignite integration. > > I am setting up setStreamer() and setIgnite() in Test class and sending > this object to setBolt() method. > > When i try to read via gettreamer() and getIgnite() i am getting NULL. I am > trying to find out why is it happening but No Luck. > > If any one of you find some time and look into the code and help me to > resolve this. It would be great. > > Git : https://github.com/chandresh-pancholi/ignite > Module : storm > > -- > Chandresh Pancholi > Senior Software Engineer > Flipkart.com > Email-id:chandresh.panch...@flipkart.com > Contact:08951803660 >
Re: Brainstorming about Reactive Streams
It ' a nice feature to be included in the grid compute module , in my opinion . But I have a question : what difference we have with ComputeTask class in behavioral terms ? https://apacheignite.readme.io/docs/compute-tasks 2015-09-23 16:45 GMT+02:00 Lalit Kumar Jha : > Summarizing this: > > *Goal*: All data flow/stream in system adhere to “Reactive Streams” API, > includes data ingestion, async computation, compute result/stream > aggregation. > > *Benefits*: > > >- Common interface for all data transfer/exchange/processing. >- Streaming data ingestion can compose complex stream processing in a >standard (interoperable dropin implementation replacement) fashion, like >filter or aggregate streaming data, merge multiple stream etc. > > >- Compose multiple async compute jobs results as streams. > > > *Design*: To overcome “Cons of Exposing Reactive Stream APIs instead of > RxJava (or other implementation)” mentioned at > https://github.com/ReactiveX/RxJava/wiki/Reactive-Streams > > #1. Follow recommended approach there. > > > #2. Rather than having streaming (data transfer) stream processing logic > (filter, merge, flatMap) in Consumer, treat them as a separate concern, and > wrap Publisher/Consumer in concrete classes. > > This is discouraged by RxJava, but will keep standard and non standard > implementation separate and will allow using multiple libraries for > different use-cases. Rather than having this behaviour tightly coupled in > Consumer. > > > > On Wed, Sep 23, 2015 at 6:29 PM, Raul Kripalani wrote: > > > Yeah, in my original post I already pointed out that Reactive Streams is > a > > proposed standard but not an implementation. > > > > My proposal was to go with RxJava 1.0 + the Reactive Streams adapter ( > > https://github.com/ReactiveX/RxJavaReactiveStreams) for now, as that > would > > allow users to benefit from things like Hystrix whose base is RxJava 1.0, > > while keeping their code future-proof for when RxJava 2.0 is released > with > > a native RS interface. > > > > Thanks for chiming in. > > > > Raúl. > > > > On Wed, Sep 23, 2015 at 1:35 PM, akarnokd wrote: > > > > > I'd definitely go on a Reactive-Streams path (although I don't know > what > > > Apache Ignite does), however, there seems to be a small confusion > around > > > RS. > > > RS is a set of 4 interfaces and practically unusable on its own. One > > needs > > > a > > > library built around it such as Project Reactor, Akka Streams and > RxJava > > > 2.0. Such library, likely, will also slip into the API itself due to > its > > > usefulness. > > > > > > For example, the following API is inconvenient to use but is definitely > > > cutting-edge: > > > > > > Publisher getData(); > > > > > > but you can only subscribe to it in its plain form or wrap it with one > of > > > the libraries: > > > > > > Observable.fromPublisher(getData()).map().filter().group()... > > > > > > I'm not sure about the others, but RxJava 2.0 Observable (which later > may > > > be > > > renamed to Flowable) implement Publisher directly, therefore, the > > following > > > getData() may return an RxJava Observable and still be consumable via > > > Reactor or Akka (after wrapping/fluent-conversion, of course): > > > > > > getData().to(Streams::from).dispatchOn(...) > > > > > > Although I'm pretty confident that RxJava 2.0 works right now, it is > > still > > > considered alpha and based on past experience with its gatekeepers, it > > may > > > take 6-12 months until an official release comes out. > > > > > > > > > > > > -- > > > View this message in context: > > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/Brainstorming-about-Reactive-Streams-tp3346p3422.html > > > Sent from the Apache Ignite Developers mailing list archive at > > Nabble.com. > > > > > >
Re: After setting streamer and ignite,getting NULL
Chandresh, I will launch the unit test later this week , if the problem persists. I think that you should instantiate Ignite through the start() method of Ignition class and retrieve the Ignite cache specifying a name for the default cache. You should provide a name also for data streamer, not passing null. Could you do this and run again the unit test ? Thank you, Regards, Gianfranco 2015-09-24 5:40 GMT+02:00 chandresh pancholi : > Anton, > > Clone this repo https://github.com/chandresh-pancholi/ignite and run this > class > > https://github.com/chandresh-pancholi/ignite/blob/master/modules/storm/src/test/java/org/apache/ignite/stream/storm/IgniteStormStreamerSelfTestSuite.java > > You will get the Error saying "Oouch,Argument is Null" for getStreamer(). > > On Wed, Sep 23, 2015 at 9:46 PM, Anton Vinogradov < > avinogra...@gridgain.com> > wrote: > > > Chandresh, > > I'm trying to analize problem. > > Could you please provide more details and explain step-by-step how can I > > reproduce problem? > > > > On Tue, Sep 22, 2015 at 11:06 PM, chandresh pancholi < > > chandreshpancholi...@gmail.com> wrote: > > > > > Not yet. > > > Still doing brainstorming why StormStreamer object is getting NULLL > > > in-spite setting up ignite and streamer instances. > > > > > > On Tue, Sep 22, 2015 at 7:22 PM, Vishal Garg > wrote: > > > > > > > Did you figure it out? Something related to your storm integration? > > > > Vishal > > > > > > > > Sent from my iPhone > > > > > > > > > On Sep 22, 2015, at 4:50 AM, chandresh pancholi < > > > > chandreshpancholi...@gmail.com> wrote: > > > > > > > > > > Problem here is with Storm. Its making streamer object null once it > > > goes > > > > > into submit topology. > > > > > > > > > > On Mon, Sep 21, 2015 at 7:13 PM, Lalit Kumar Jha < > > lalitj@gmail.com > > > > > > > > > wrote: > > > > > > > > > >> Hi Chandresh, > > > > >> > > > > >> See test suite class here, its based on annotations > > > > >> > > > > >> > > > > > > > > > > https://github.com/sylentprayer/ignite/blob/ignite-530/modules/twitter/src/test/java/org/apache/ignite/stream/twitter/IgniteTwitterStreamerTestSuite.java > > > > >> > > > > >> No code required in class body. > > > > >> > > > > >> On Mon, Sep 21, 2015 at 6:24 PM, chandresh pancholi < > > > > >> chandreshpancholi...@gmail.com> wrote: > > > > >> > > > > >>> Hi Gian/Vishal/Lalit, > > > > >>> > > > > >>> You guys have worked on Streamer integration with Ignite. I am > > > working > > > > on > > > > >>> Storm-ignite integration. > > > > >>> > > > > >>> I am setting up setStreamer() and setIgnite() in Test class and > > > sending > > > > >>> this object to setBolt() method. > > > > >>> > > > > >>> When i try to read via gettreamer() and getIgnite() i am getting > > > NULL. > > > > I > > > > >> am > > > > >>> trying to find out why is it happening but No Luck. > > > > >>> > > > > >>> If any one of you find some time and look into the code and help > me > > > to > > > > >>> resolve this. It would be great. > > > > >>> > > > > >>> Git : https://github.com/chandresh-pancholi/ignite > > > > >>> Module : storm > > > > >>> > > > > >>> -- > > > > >>> Chandresh Pancholi > > > > >>> Senior Software Engineer > > > > >>> Flipkart.com > > > > >>> Email-id:chandresh.panch...@flipkart.com > > > > >>> Contact:08951803660 > > > > > > > > > > > > > > > > > > > > -- > > > > > Chandresh Pancholi > > > > > Senior Software Engineer > > > > > Flipkart.com > > > > > Email-id:chandresh.panch...@flipkart.com > > > > > Contact:08951803660 > > > > > > > > > > > > > > > > -- > > > Chandresh Pancholi > > > Senior Software Engineer > > > Flipkart.com > > > Email-id:chandresh.panch...@flipkart.com > > > Contact:08951803660 > > > > > > > > > -- > Chandresh Pancholi > Senior Software Engineer > Flipkart.com > Email-id:chandresh.panch...@flipkart.com > Contact:08951803660 >
Re: [VOTE] Apache Ignite 1.4.0 Release (RC1)
+1 2015-09-25 17:26 GMT+02:00 Sergi Vladykin : > +1 > > Sergi > > 2015-09-25 16:52 GMT+03:00 Alexey Kuznetsov : > > > +1 > > > > On Fri, Sep 25, 2015 at 8:48 PM, Anton Vinogradov wrote: > > > > > +1 > > > > > > On Fri, Sep 25, 2015 at 3:49 PM, Denis Magda > > wrote: > > > > > > > +1 > > > > > > > > -Original Message- > > > > From: "Yakov Zhdanov" > > > > Sent: 9/25/2015 15:37 > > > > To: "dev@ignite.apache.org" > > > > Subject: [VOTE] Apache Ignite 1.4.0 Release (RC1) > > > > > > > > Dear Sirs! > > > > > > > > We have uploaded release candidate to > > > > https://dist.apache.org/repos/dist/dev/ignite/1.4.0-rc1/ > > > > > > > > I am very glad to mention that this is the first Ignite release as > top > > > > level project! Thanks everyone for help this to happen! > > > > > > > > Tag name is > > > > ignite-1.4.0-rc1 > > > > > > > > 1.4.0 changes: > > > > * Added SSL support to communication and discovery. > > > > * Added support for log4j2. > > > > * Added versioned entry to cache API. > > > > * Added client node based JDBC driver implementation. > > > > * Fixed consistency issue for custom events processing within > > discovery. > > > > * Fixed race in cache swap/unswap logic. > > > > * Fixed IGNITE_HOME resolution with JBoss. > > > > * Fixed configuration file resolution on classpath. > > > > * Fixed MBean registration for caches. > > > > * Fixed near cache evictions with offheap. > > > > * Fixed SQL queries group index logic. > > > > * Fixed memory leak in partitioned transactional cache. > > > > * Fixed auto-retries for cache operations in recoverable cases. > > > > * Fixed affinity routing in compute grid. > > > > * Many stability and fault-tolerance fixes. > > > > > > > > DEVNOTES > > > > > > > > > > > > > > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/ignite-1.4.0-rc1 > > > > > > > > RELEASENOTES > > > > > > > > > > > > > > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/ignite-1.4.0-rc1 > > > > > > > > Please start voting. > > > > > > > > +1 - to accept Apache Ignite 1.4.0 > > > > 0 - don't care either way > > > > -1 - DO NOT accept Apache Ignite 1.4.0 (explain why) > > > > > > > > This vote will go for 72 hours. > > > > > > > > --Yakov > > > > > > > > > > > > > > > -- > > Alexey Kuznetsov > > GridGain Systems > > www.gridgain.com > > >
Re: After setting streamer and ignite,getting NULL
Chan,
I've fixed some issue, please take a look here:
https://github.com/murador/ignite/blob/IGNITE-429/modules/storm/src/test/java/org/apache/ignite/stream/storm/StormIgniteStreamerSelfTest.java
2015-09-26 8:29 GMT+02:00 chandresh pancholi :
> Gian,
>
> I have followed instructions given by you. I instantiate IgniteDateStreamer
> and ignite in prepare() method of bolt. but getting "*Cache doesn't
> exist*".
>
> Code snippet from stormStreamer class in prepare() method
>
> StormStreamer stormStreamer = null;
>
> Ignite ignite = Ignition.start();
>
> System.out.println(" ignite == "+ignite.toString());
>
> try(IgniteDataStreamer stmr =
> ignite.dataStreamer("cache-0")) {
>
> stormStreamer = new StormStreamer<>();
>
> IgniteCache cache = ignite.cache("cache-0");
>
> stmr.allowOverwrite(true);
>
> /* Set ignite instance */
> stormStreamer.setIgnite(ignite);
>
> /* Set streamer instance */
> stormStreamer.setStreamer(stmr);
>
> /* set thread count */
> setThreads(5);
>
> }
>
>
>
> On Thu, Sep 24, 2015 at 4:19 PM, Anton Vinogradov <
> avinogra...@gridgain.com>
> wrote:
>
> > Chandresh,
> > As far as understand IBolt implementation should setup all external
> > connections at .prepare() method.
> > So, better way is to get existing Ignite instance or create new at
> > .prepare()
> > method.
> >
> >
> > On Thu, Sep 24, 2015 at 10:55 AM, Gianfranco Murador <
> > murador.gianfra...@gmail.com> wrote:
> >
> > > Chandresh,
> > > I will launch the unit test later this week , if the problem persists.
> I
> > > think that you should instantiate Ignite through the start() method of
> > > Ignition class
> > > and retrieve the Ignite cache specifying a name for the default cache.
> > You
> > > should provide a name also for data streamer, not passing null.
> > > Could you do this and run again the unit test ?
> > > Thank you,
> > > Regards,
> > > Gianfranco
> > >
> > >
> > > 2015-09-24 5:40 GMT+02:00 chandresh pancholi <
> > > chandreshpancholi...@gmail.com
> > > >:
> > >
> > > > Anton,
> > > >
> > > > Clone this repo https://github.com/chandresh-pancholi/ignite and run
> > > this
> > > > class
> > > >
> > > >
> > >
> >
> https://github.com/chandresh-pancholi/ignite/blob/master/modules/storm/src/test/java/org/apache/ignite/stream/storm/IgniteStormStreamerSelfTestSuite.java
> > > >
> > > > You will get the Error saying "Oouch,Argument is Null" for
> > getStreamer().
> > > >
> > > > On Wed, Sep 23, 2015 at 9:46 PM, Anton Vinogradov <
> > > > avinogra...@gridgain.com>
> > > > wrote:
> > > >
> > > > > Chandresh,
> > > > > I'm trying to analize problem.
> > > > > Could you please provide more details and explain step-by-step how
> > can
> > > I
> > > > > reproduce problem?
> > > > >
> > > > > On Tue, Sep 22, 2015 at 11:06 PM, chandresh pancholi <
> > > > > chandreshpancholi...@gmail.com> wrote:
> > > > >
> > > > > > Not yet.
> > > > > > Still doing brainstorming why StormStreamer object is getting
> NULLL
> > > > > > in-spite setting up ignite and streamer instances.
> > > > > >
> > > > > > On Tue, Sep 22, 2015 at 7:22 PM, Vishal Garg >
> > > > wrote:
> > > > > >
> > > > > > > Did you figure it out? Something related to your storm
> > integration?
> > > > > > > Vishal
> > > > > > >
> > > > > > > Sent from my iPhone
> > > > > > >
> > > > > > > > On Sep 22, 2015, at 4:50 AM, chandresh pancholi <
> > > > > > > chandreshpancholi...@gmail.com> wrote:
> > > > > > > >
> > > > > > > > Problem here is with Storm. Its making streamer object null
> > once
> > > it
> > > > > > goes
> > > > > > > > into submit topology.
> > > > > > > >
> > > > > > > > On Mon, Sep 21, 2015 at 7:13 PM, Lalit Kumar Jha <
> > > > > lalitj@gmail.com
> > > > > > >
> > &
Re: After setting streamer and ignite,getting NULL
Chan,
I can run the test succefully, but sometimes I get this error:
Caused by: class org.apache.ignite.spi.IgniteSpiException: Failed to add
node to topology because remote node is configured to use loopback address,
but local node is not (consider changing 'localAddress' configuration
parameter).
can you send the log file?
Regards, Gianfranco
2015-09-26 17:13 GMT+02:00 chandresh pancholi <
chandreshpancholi...@gmail.com>:
> Gian,
> Its still giving "Ouch! Argument cannot be null: streamer"
>
> On Sat, Sep 26, 2015 at 7:24 PM, Gianfranco Murador <
> murador.gianfra...@gmail.com> wrote:
>
> > Chan,
> > I've fixed some issue, please take a look here:
> >
> >
> https://github.com/murador/ignite/blob/IGNITE-429/modules/storm/src/test/java/org/apache/ignite/stream/storm/StormIgniteStreamerSelfTest.java
> >
> > 2015-09-26 8:29 GMT+02:00 chandresh pancholi <
> > chandreshpancholi...@gmail.com
> > >:
> >
> > > Gian,
> > >
> > > I have followed instructions given by you. I instantiate
> > IgniteDateStreamer
> > > and ignite in prepare() method of bolt. but getting "*Cache doesn't
> > > exist*".
> > >
> > > Code snippet from stormStreamer class in prepare() method
> > >
> > > StormStreamer stormStreamer = null;
> > >
> > > Ignite ignite = Ignition.start();
> > >
> > > System.out.println(" ignite == "+ignite.toString());
> > >
> > > try(IgniteDataStreamer stmr =
> > > ignite.dataStreamer("cache-0")) {
> > >
> > > stormStreamer = new StormStreamer<>();
> > >
> > > IgniteCache cache = ignite.cache("cache-0");
> > >
> > > stmr.allowOverwrite(true);
> > >
> > > /* Set ignite instance */
> > > stormStreamer.setIgnite(ignite);
> > >
> > > /* Set streamer instance */
> > > stormStreamer.setStreamer(stmr);
> > >
> > > /* set thread count */
> > > setThreads(5);
> > >
> > > }
> > >
> > >
> > >
> > > On Thu, Sep 24, 2015 at 4:19 PM, Anton Vinogradov <
> > > avinogra...@gridgain.com>
> > > wrote:
> > >
> > > > Chandresh,
> > > > As far as understand IBolt implementation should setup all external
> > > > connections at .prepare() method.
> > > > So, better way is to get existing Ignite instance or create new at
> > > > .prepare()
> > > > method.
> > > >
> > > >
> > > > On Thu, Sep 24, 2015 at 10:55 AM, Gianfranco Murador <
> > > > murador.gianfra...@gmail.com> wrote:
> > > >
> > > > > Chandresh,
> > > > > I will launch the unit test later this week , if the problem
> > persists.
> > > I
> > > > > think that you should instantiate Ignite through the start() method
> > of
> > > > > Ignition class
> > > > > and retrieve the Ignite cache specifying a name for the default
> > cache.
> > > > You
> > > > > should provide a name also for data streamer, not passing null.
> > > > > Could you do this and run again the unit test ?
> > > > > Thank you,
> > > > > Regards,
> > > > > Gianfranco
> > > > >
> > > > >
> > > > > 2015-09-24 5:40 GMT+02:00 chandresh pancholi <
> > > > > chandreshpancholi...@gmail.com
> > > > > >:
> > > > >
> > > > > > Anton,
> > > > > >
> > > > > > Clone this repo https://github.com/chandresh-pancholi/ignite and
> > run
> > > > > this
> > > > > > class
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/chandresh-pancholi/ignite/blob/master/modules/storm/src/test/java/org/apache/ignite/stream/storm/IgniteStormStreamerSelfTestSuite.java
> > > > > >
> > > > > > You will get the Error saying "Oouch,Argument is Null" for
> > > > getStreamer().
> > > > > >
> > > > > > On Wed, Sep 23, 2015 at 9:46 PM, Anton Vinogradov <
> > > > > > avinogra...@gridgain.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Chandresh,
> > > > > > &
Re: After setting streamer and ignite,getting NULL
Chandresh, we're ready to do a pull request. Look here:
https://github.com/murador/ignite/tree/IGNITE-429/modules/storm
2015-09-27 8:49 GMT+02:00 chandresh pancholi :
> Here is the log file.
>
> Thanks
>
> On Sat, Sep 26, 2015 at 10:40 PM, Gianfranco Murador <
> murador.gianfra...@gmail.com> wrote:
>
>> Chan,
>> I can run the test succefully, but sometimes I get this error:
>> Caused by: class org.apache.ignite.spi.IgniteSpiException: Failed to add
>> node to topology because remote node is configured to use loopback
>> address,
>> but local node is not (consider changing 'localAddress' configuration
>> parameter).
>>
>> can you send the log file?
>> Regards, Gianfranco
>>
>>
>>
>> 2015-09-26 17:13 GMT+02:00 chandresh pancholi <
>> chandreshpancholi...@gmail.com>:
>>
>> > Gian,
>> > Its still giving "Ouch! Argument cannot be null: streamer"
>> >
>> > On Sat, Sep 26, 2015 at 7:24 PM, Gianfranco Murador <
>> > murador.gianfra...@gmail.com> wrote:
>> >
>> > > Chan,
>> > > I've fixed some issue, please take a look here:
>> > >
>> > >
>> >
>> https://github.com/murador/ignite/blob/IGNITE-429/modules/storm/src/test/java/org/apache/ignite/stream/storm/StormIgniteStreamerSelfTest.java
>> > >
>> > > 2015-09-26 8:29 GMT+02:00 chandresh pancholi <
>> > > chandreshpancholi...@gmail.com
>> > > >:
>> > >
>> > > > Gian,
>> > > >
>> > > > I have followed instructions given by you. I instantiate
>> > > IgniteDateStreamer
>> > > > and ignite in prepare() method of bolt. but getting "*Cache doesn't
>> > > > exist*".
>> > > >
>> > > > Code snippet from stormStreamer class in prepare() method
>> > > >
>> > > > StormStreamer stormStreamer = null;
>> > > >
>> > > > Ignite ignite = Ignition.start();
>> > > >
>> > > > System.out.println(" ignite == "+ignite.toString());
>> > > >
>> > > > try(IgniteDataStreamer stmr =
>> > > > ignite.dataStreamer("cache-0")) {
>> > > >
>> > > > stormStreamer = new StormStreamer<>();
>> > > >
>> > > > IgniteCache cache = ignite.cache("cache-0");
>> > > >
>> > > > stmr.allowOverwrite(true);
>> > > >
>> > > > /* Set ignite instance */
>> > > > stormStreamer.setIgnite(ignite);
>> > > >
>> > > > /* Set streamer instance */
>> > > > stormStreamer.setStreamer(stmr);
>> > > >
>> > > > /* set thread count */
>> > > > setThreads(5);
>> > > >
>> > > > }
>> > > >
>> > > >
>> > > >
>> > > > On Thu, Sep 24, 2015 at 4:19 PM, Anton Vinogradov <
>> > > > avinogra...@gridgain.com>
>> > > > wrote:
>> > > >
>> > > > > Chandresh,
>> > > > > As far as understand IBolt implementation should setup all
>> external
>> > > > > connections at .prepare() method.
>> > > > > So, better way is to get existing Ignite instance or create new at
>> > > > > .prepare()
>> > > > > method.
>> > > > >
>> > > > >
>> > > > > On Thu, Sep 24, 2015 at 10:55 AM, Gianfranco Murador <
>> > > > > murador.gianfra...@gmail.com> wrote:
>> > > > >
>> > > > > > Chandresh,
>> > > > > > I will launch the unit test later this week , if the problem
>> > > persists.
>> > > > I
>> > > > > > think that you should instantiate Ignite through the start()
>> method
>> > > of
>> > > > > > Ignition class
>> > > > > > and retrieve the Ignite cache specifying a name for the default
>> > > cache.
>> > > > > You
>> > > > > > should provide a name also for data streamer, not passing null.
>> > > > > > Could you do this and run again the unit test ?
>> > > > > > Thank you,
>> > > > > > Regards,
>> > > > > > Gianfranco
>> > &g
Re: After setting streamer and ignite,getting NULL
Chandresh,
I think that the suggestion of Roman is preferable, we can use the
following code :
Let me know if you have problems
/** Start a simulated topology */
public void startTopology(StormStreamer stormStreamer) {
MkClusterParam mkClusterParam = new MkClusterParam();
mkClusterParam.setSupervisors(4);
Config daemonConf = new Config();
daemonConf.put(Config.STORM_LOCAL_MODE_ZMQ, false);
mkClusterParam.setDaemonConf(daemonConf);
Testing.withSimulatedTimeLocalCluster(mkClusterParam, new TestJob()
{
@Override
public void run(ILocalCluster cluster) throws
IOException {
TopologyBuilder builder = new TopologyBuilder();
builder.setSpout("testSpout", new StormSpout());
builder.setBolt("bolt", stormStreamer)
.shuffleGrouping("spout");
StormTopology topology = builder.createTopology();
MockedSources mockedSources = new MockedSources();
//Our spout will be processing this values.
mockedSources.addMockData("testSpout",new
Values(stormStream.getKeyValMap()));
// prepare the config
Config conf = new Config();
conf.setNumWorkers(2);
CompleteTopologyParam completeTopologyParam = new
CompleteTopologyParam();
completeTopologyParam.setMockedSources(mockedSources);
completeTopologyParam.setStormConf(conf);
Map result = Testing.completeTopology(cluster,
topology, completeTopologyParam);
}
}
);
}
2015-09-28 6:11 GMT+02:00 chandresh pancholi :
> Agree,
> Will check for some other solution and update!!
>
> On Mon, Sep 28, 2015 at 9:12 AM, Vishal Garg wrote:
>
> > Chandresh,
> >
> > Generally sleep in tests is not a good idea. Will try to look into your
> > test this week, see if we can avoid it.
> > Meanwhile you can look at how storm does its own unit testing if you
> could
> > find one?
> > Vishal
> >
> > Sent from my iPhone
> >
> > > On Sep 27, 2015, at 8:23 PM, Roman wrote:
> > >
> > > I also have concerns about this sleep().Storm has testing facilities
> you
> > can use for your test. How about Testing.withSimulatedTimeLocalCluster()?
> > > Roman
> > >
> > >
> > >
> > > On Monday, September 28, 2015 5:39 AM, Dmitriy Setrakyan <
> > dsetrak...@apache.org> wrote:
> > >
> > >
> > > On Sun, Sep 27, 2015 at 1:36 PM, chandresh pancholi <
> > > chandreshpancholi...@gmail.com> wrote:
> > >
> > >> Gian,
> > >> I have checked the code. It looks good.
> > >> Just one little change make it 20 sec.
> > >>
> > >> /* Topology will run for 10sec */
> > >> Utils.sleep(2);
> > >
> > > Hm... Can someone explain what is this sleep() for?
> > >
> > >
> > >>
> > >>
> > >>
> > >> On Sun, Sep 27, 2015 at 4:30 PM, Gianfranco Murador <
> > >> murador.gianfra...@gmail.com> wrote:
> > >>
> > >>> Chandresh, we're ready to do a pull request. Look here:
> > >>> https://github.com/murador/ignite/tree/IGNITE-429/modules/storm
> > >>>
> > >>> 2015-09-27 8:49 GMT+02:00 chandresh pancholi <
> > >>> chandreshpancholi...@gmail.com
> > >>>> :
> > >>>
> > >>>> Here is the log file.
> > >>>>
> > >>>> Thanks
> > >>>>
> > >>>> On Sat, Sep 26, 2015 at 10:40 PM, Gianfranco Murador <
> > >>>> murador.gianfra...@gmail.com> wrote:
> > >>>>
> > >>>>> Chan,
> > >>>>> I can run the test succefully, but sometimes I get this error:
> > >>>>> Caused by: class org.apache.ignite.spi.IgniteSpiException: Failed
> to
> > >> add
> > >>>>> node to topology because remote node is configured to use loopback
> > >>>>> address,
> > >>>>> but local node is not (consider changing 'localAddress'
> configuration
> > >>>>> parameter).
> > >>>>>
> > >>>>> can you send the log file?
> > >>>>> Regards, Gianfranco
> > >>>>>
> > >
Re: Switched main version to 1.4 on readme.io
This news needs a tweet !! :) 2015-09-28 15:24 GMT+02:00 Yakov Zhdanov : > subj > > --Yakov > -- Gianfranco Murador Igniter and Software Engineer.
Re: Ignite 1.5 plans
I would like to propose the integration with JBPM , I think I can finish in a couple of weeks since I have a bit of time to devote to Ignite. Let me know if you agree. Regards, Gianfranco 2015-09-28 18:50 GMT+02:00 Dmitriy Setrakyan : > I would like to add one more: > 10. OSGI integration - Raul Kripalani > > Raul, hopefully you will have time to finish it. > > Also, if anyone in the community wants to propose a feature they are > working on which can be finished within next couple of weeks, it should get > into 1.5 as well. > > D. > > On Mon, Sep 28, 2015 at 6:43 PM, Yakov Zhdanov > wrote: > > > Guys! > > > > We have finalized 1.4 release! > > > > Thanks to everyone involved! That was very important release for our > > project. > > > > Let's discuss scope for 1.5. > > > > I think the main focus areas should be: > > 1. Optimized marshaller rework - Alex Goncharuk works on this. > > 2. .Net and Cpp API release (depends on 3) - Vladimir Ozerov > > 3. Portable API release - Denis Magda and Vladimir > > 4. Failover for continuous query notifications - Nick Tikhonov > > 5. Cache Rebalancing optimizations - Anton Vinogradov > > 6. Fix compatibility with IBM JDK > > 7. Cache stability and performance fixes (as many as possible) > > > > Nice to have: > > 8. Finish vert.x integration - Andrey Gura works on this. > > 9. Finish node.js integration - I think Semyon should pass it over to > > someone else, given he is busy with cache. Anyone? Andrey Gura? > > > > Comments are welcome! > > > > [1] https://issues.apache.org/jira/browse/IGNITE-950 > > [2] https://issues.apache.org/jira/browse/IGNITE-1282 > > [3] https://issues.apache.org/jira/browse/IGNITE-1258 > > [4] https://issues.apache.org/jira/browse/IGNITE-426 > > [5] https://issues.apache.org/jira/browse/IGNITE-1093 > > [5] https://issues.apache.org/jira/browse/IGNITE-324 > > [6] https://issues.apache.org/jira/browse/IGNITE-1526 > > [7] https://issues.apache.org/jira/browse/IGNITE-1345 > > [8] https://issues.apache.org/jira/browse/IGNITE-1079 > > [9] https://issues.apache.org/jira/browse/IGNITE-961 > > > > --Yakov > > > -- Gianfranco Murador Igniter and Software Engineer.
Re: Ignite 1.5 plans
Dmitry, The short answer is because JBPM is integrated well with Infinispan,the longest and technically correct answer is as follows. JBPM is now used in many productions of the clients they serve a high number of users.The main problem with the engine of business processes resides in the non- synchronicity of the workflow, ie the workflow goes forward based on the working times of the employees, so it is possible that a workflow ends within a few days. Maintain an instance of a workflow in the database and retrieve it each time it is expensive in terms of time, we might have many workflow latches.The idea is to allow to save in cache the entire instance of a workflow in order to make the most rapid recovery possible. There are also rapid workflows where the use of a cache is very interesting, for example, a job stream must be recovered and carried forward in a few second (for example,at a bank office). The idea is to create a grid of instances of workflows to allow recovery quickly. The idea has already been implemented for Infinispan, but is not very advanced. https://github.com/droolsjbpm/droolsjbpm-integration/tree/master/kie-infinispan/jbpm-infinispan-persistence/src/main/java/org/jbpm/persistence Regards, Gianfranco. 2015-09-28 18:57 GMT+02:00 Dmitriy Setrakyan : > Gianfranco, > > I am not too familiar with JBPM. Can you make a case on why we may need > this integration and how it will benefit Ignite users? > > Thanks, > D. > > On Mon, Sep 28, 2015 at 6:56 PM, Gianfranco Murador > wrote: > > > I would like to propose the integration with JBPM , > > I think I can finish in a couple of weeks since I have a bit of time to > > devote to Ignite. > > Let me know if you agree. > > Regards, Gianfranco > > > > 2015-09-28 18:50 GMT+02:00 Dmitriy Setrakyan : > > > > > I would like to add one more: > > > 10. OSGI integration - Raul Kripalani > > > > > > Raul, hopefully you will have time to finish it. > > > > > > Also, if anyone in the community wants to propose a feature they are > > > working on which can be finished within next couple of weeks, it should > > get > > > into 1.5 as well. > > > > > > D. > > > > > > On Mon, Sep 28, 2015 at 6:43 PM, Yakov Zhdanov > > > wrote: > > > > > > > Guys! > > > > > > > > We have finalized 1.4 release! > > > > > > > > Thanks to everyone involved! That was very important release for our > > > > project. > > > > > > > > Let's discuss scope for 1.5. > > > > > > > > I think the main focus areas should be: > > > > 1. Optimized marshaller rework - Alex Goncharuk works on this. > > > > 2. .Net and Cpp API release (depends on 3) - Vladimir Ozerov > > > > 3. Portable API release - Denis Magda and Vladimir > > > > 4. Failover for continuous query notifications - Nick Tikhonov > > > > 5. Cache Rebalancing optimizations - Anton Vinogradov > > > > 6. Fix compatibility with IBM JDK > > > > 7. Cache stability and performance fixes (as many as possible) > > > > > > > > Nice to have: > > > > 8. Finish vert.x integration - Andrey Gura works on this. > > > > 9. Finish node.js integration - I think Semyon should pass it over to > > > > someone else, given he is busy with cache. Anyone? Andrey Gura? > > > > > > > > Comments are welcome! > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-950 > > > > [2] https://issues.apache.org/jira/browse/IGNITE-1282 > > > > [3] https://issues.apache.org/jira/browse/IGNITE-1258 > > > > [4] https://issues.apache.org/jira/browse/IGNITE-426 > > > > [5] https://issues.apache.org/jira/browse/IGNITE-1093 > > > > [5] https://issues.apache.org/jira/browse/IGNITE-324 > > > > [6] https://issues.apache.org/jira/browse/IGNITE-1526 > > > > [7] https://issues.apache.org/jira/browse/IGNITE-1345 > > > > [8] https://issues.apache.org/jira/browse/IGNITE-1079 > > > > [9] https://issues.apache.org/jira/browse/IGNITE-961 > > > > > > > > --Yakov > > > > > > > > > > > > > > > -- > > Gianfranco Murador > > Igniter and Software Engineer. > > > -- Gianfranco Murador Igniter and Software Engineer.
Re: After setting streamer and ignite,getting NULL
Yes, in mater branch of my fork.
2015-09-29 8:45 GMT+02:00 chandresh pancholi :
> Gian,
>
> is code for ignite-429 in master branch?
>
> On Mon, Sep 28, 2015 at 5:27 PM, chandresh pancholi <
> chandreshpancholi...@gmail.com> wrote:
>
> > Gian,
> >
> > Lets use this and modify our tests. I will push the code by tomorrow EOD.
> >
> > Thanks
> > Chandresh Pancholi
> >
> > On Mon, Sep 28, 2015 at 3:58 PM, Gianfranco Murador <
> > murador.gianfra...@gmail.com> wrote:
> >
> >> Chandresh,
> >> I think that the suggestion of Roman is preferable, we can use the
> >> following code :
> >> Let me know if you have problems
> >>
> >> /** Start a simulated topology */
> >> public void startTopology(StormStreamer stormStreamer) {
> >> MkClusterParam mkClusterParam = new MkClusterParam();
> >> mkClusterParam.setSupervisors(4);
> >> Config daemonConf = new Config();
> >> daemonConf.put(Config.STORM_LOCAL_MODE_ZMQ, false);
> >> mkClusterParam.setDaemonConf(daemonConf);
> >>
> >> Testing.withSimulatedTimeLocalCluster(mkClusterParam, new
> >> TestJob()
> >> {
> >> @Override
> >> public void run(ILocalCluster cluster) throws
> >> IOException {
> >> TopologyBuilder builder = new TopologyBuilder();
> >>
> >> builder.setSpout("testSpout", new StormSpout());
> >>
> >> builder.setBolt("bolt", stormStreamer)
> >> .shuffleGrouping("spout");
> >>
> >> StormTopology topology =
> builder.createTopology();
> >>
> >> MockedSources mockedSources = new
> MockedSources();
> >>
> >> //Our spout will be processing this values.
> >> mockedSources.addMockData("testSpout",new
> >> Values(stormStream.getKeyValMap()));
> >>
> >>
> >> // prepare the config
> >> Config conf = new Config();
> >> conf.setNumWorkers(2);
> >>
> >> CompleteTopologyParam completeTopologyParam =
> new
> >> CompleteTopologyParam();
> >>
> >> completeTopologyParam.setMockedSources(mockedSources);
> >> completeTopologyParam.setStormConf(conf);
> >>
> >> Map result = Testing.completeTopology(cluster,
> >> topology, completeTopologyParam);
> >> }
> >> }
> >> );
> >> }
> >>
> >> 2015-09-28 6:11 GMT+02:00 chandresh pancholi <
> >> chandreshpancholi...@gmail.com
> >> >:
> >>
> >> > Agree,
> >> > Will check for some other solution and update!!
> >> >
> >> > On Mon, Sep 28, 2015 at 9:12 AM, Vishal Garg
> >> wrote:
> >> >
> >> > > Chandresh,
> >> > >
> >> > > Generally sleep in tests is not a good idea. Will try to look into
> >> your
> >> > > test this week, see if we can avoid it.
> >> > > Meanwhile you can look at how storm does its own unit testing if you
> >> > could
> >> > > find one?
> >> > > Vishal
> >> > >
> >> > > Sent from my iPhone
> >> > >
> >> > > > On Sep 27, 2015, at 8:23 PM, Roman
> >> wrote:
> >> > > >
> >> > > > I also have concerns about this sleep().Storm has testing
> facilities
> >> > you
> >> > > can use for your test. How about
> >> Testing.withSimulatedTimeLocalCluster()?
> >> > > > Roman
> >> > > >
> >> > > >
> >> > > >
> >> > > > On Monday, September 28, 2015 5:39 AM, Dmitriy Setrakyan <
> >> > > dsetrak...@apache.org> wrote:
> >> > > >
> >> > > >
> >> > > > On Sun, Sep 27, 2015 at 1:36 PM, chandresh pancholi <
> >> > > > chandreshpancholi...@gmail.com> wrote:
> >> > > >
> >> > > >> Gian,
> >> > > >> I have checked the code. It looks good.
> >>
Re: Ignite 1.5 plans
Dmitry, Could you give me some feedback about this proposal? You think it might be interesting? Thank you. 2015-09-29 12:00 GMT+02:00 Gianfranco Murador : > Dmitry, > The short answer is because JBPM is integrated well with Infinispan,the > longest and technically correct answer is as follows. > > JBPM is now used in many productions of the clients they serve a high > number of users.The main problem with the engine of business processes > resides in the non- synchronicity of the workflow, ie the workflow goes > forward based on the working times of the employees, so it is possible that > a workflow ends within a few days. Maintain an instance of a workflow in > the database and retrieve it each time it is expensive in terms of time, we > might have many workflow latches.The idea is to allow to save in cache the > entire instance of a workflow in order to make the most rapid recovery > possible. > > There are also rapid workflows where the use of a cache is very > interesting, for example, a job stream must be recovered and carried > forward in a few second (for example,at a bank office). The idea is to > create a grid of instances of workflows to allow recovery quickly. > > The idea has already been implemented for Infinispan, but is not very > advanced. > > > https://github.com/droolsjbpm/droolsjbpm-integration/tree/master/kie-infinispan/jbpm-infinispan-persistence/src/main/java/org/jbpm/persistence > > Regards, > Gianfranco. > > > > 2015-09-28 18:57 GMT+02:00 Dmitriy Setrakyan : > >> Gianfranco, >> >> I am not too familiar with JBPM. Can you make a case on why we may need >> this integration and how it will benefit Ignite users? >> >> Thanks, >> D. >> >> On Mon, Sep 28, 2015 at 6:56 PM, Gianfranco Murador >> wrote: >> >> > I would like to propose the integration with JBPM , >> > I think I can finish in a couple of weeks since I have a bit of time to >> > devote to Ignite. >> > Let me know if you agree. >> > Regards, Gianfranco >> > >> > 2015-09-28 18:50 GMT+02:00 Dmitriy Setrakyan : >> > >> > > I would like to add one more: >> > > 10. OSGI integration - Raul Kripalani >> > > >> > > Raul, hopefully you will have time to finish it. >> > > >> > > Also, if anyone in the community wants to propose a feature they are >> > > working on which can be finished within next couple of weeks, it >> should >> > get >> > > into 1.5 as well. >> > > >> > > D. >> > > >> > > On Mon, Sep 28, 2015 at 6:43 PM, Yakov Zhdanov >> > > wrote: >> > > >> > > > Guys! >> > > > >> > > > We have finalized 1.4 release! >> > > > >> > > > Thanks to everyone involved! That was very important release for our >> > > > project. >> > > > >> > > > Let's discuss scope for 1.5. >> > > > >> > > > I think the main focus areas should be: >> > > > 1. Optimized marshaller rework - Alex Goncharuk works on this. >> > > > 2. .Net and Cpp API release (depends on 3) - Vladimir Ozerov >> > > > 3. Portable API release - Denis Magda and Vladimir >> > > > 4. Failover for continuous query notifications - Nick Tikhonov >> > > > 5. Cache Rebalancing optimizations - Anton Vinogradov >> > > > 6. Fix compatibility with IBM JDK >> > > > 7. Cache stability and performance fixes (as many as possible) >> > > > >> > > > Nice to have: >> > > > 8. Finish vert.x integration - Andrey Gura works on this. >> > > > 9. Finish node.js integration - I think Semyon should pass it over >> to >> > > > someone else, given he is busy with cache. Anyone? Andrey Gura? >> > > > >> > > > Comments are welcome! >> > > > >> > > > [1] https://issues.apache.org/jira/browse/IGNITE-950 >> > > > [2] https://issues.apache.org/jira/browse/IGNITE-1282 >> > > > [3] https://issues.apache.org/jira/browse/IGNITE-1258 >> > > > [4] https://issues.apache.org/jira/browse/IGNITE-426 >> > > > [5] https://issues.apache.org/jira/browse/IGNITE-1093 >> > > > [5] https://issues.apache.org/jira/browse/IGNITE-324 >> > > > [6] https://issues.apache.org/jira/browse/IGNITE-1526 >> > > > [7] https://issues.apache.org/jira/browse/IGNITE-1345 >> > > > [8] https://issues.apache.org/jira/browse/IGNITE-1079 >> > > > [9] https://issues.apache.org/jira/browse/IGNITE-961 >> > > > >> > > > --Yakov >> > > > >> > > >> > >> > >> > >> > -- >> > Gianfranco Murador >> > Igniter and Software Engineer. >> > >> > > > > -- > Gianfranco Murador > Igniter and Software Engineer. > > -- Gianfranco Murador Igniter and Software Engineer.
Re: Ignite 1.5 plans
Yakov, So I guess that integration should only affect the way JBPM interacts with Ignite ? I think that a module dedicated to ignite could provide APIs more advanced than simple get and put on a grid. Infinispan already provides a second level cache Ignite does, but that does not mean that Ignite does not have to provide similar feature. Interacting JBPM with a dedicated module of ignite we could do processing on the workflow instance in advanced mode, exploiting the near cache in a distributed environment. Maybe the module might not be ready for the release of version 1.5. Ultimately, who knows better than you that Ignite is more advanced than Infinspan ? 2015-09-29 16:52 GMT+02:00 Yakov Zhdanov : > Igniters, > > Given we somehow agreed on most of the scope, can everyone please cleanup > JIRA queues accordingly? > > --Yakov > -- Gianfranco Murador Igniter and Software Engineer.
JBPM and Drools integrations
Hello Igniters , I take the discussion to understand if I have the proper approval from the community for the early integration of Ignite with Drools and JBPM. I would ask if you can then create a new repository in https://github.com/apacheignite. Thanks, Regards, Gianfranco -- Gianfranco Murador Igniter and Software Engineer.
Re: Sergey Evdokimov Tickets
Some ticket seem resolved , but the state has been left "open" . I like to work on IGNITE-417 and IGNITE-888 with the right help from community; 2015-09-30 9:42 GMT+02:00 Dmitriy Setrakyan : > On Wed, Sep 30, 2015 at 9:01 AM, Yakov Zhdanov > wrote: > > > Correct. I meant unassign. > > > > There are no critical tickets in my view - > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20%20status%20!%3D%20closed%20AND%20assignee%20%3D%20sevdokimov-gg%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > > > I think that community should feel free to grab these tickets if they have > not had any activity for a while. > > > > > > --Yakov > > > > 2015-09-29 19:44 GMT+03:00 Dmitriy Setrakyan : > > > > > On Tue, Sep 29, 2015 at 4:45 PM, Yakov Zhdanov > > > wrote: > > > > > > > Hi! > > > > > > > > I want to ask if Sergey is going to continue working on tickets > > assigned > > > to > > > > him? If not, we will reassign them in 72 hours. > > > > > > > > > > I thought you meant "un-assign" not "reassign". Do we know if there are > > any > > > critical tickets that Sergey was working on? > > > > > > > > > > > > > > Thanks! > > > > > > > > --Yakov > > > > > > > > > > -- Gianfranco Murador Igniter and Software Engineer.
Re: JBPM and Drools integrations
My github username is murador. Thank you. 2015-09-30 10:39 GMT+02:00 Dmitriy Setrakyan : > On Wed, Sep 30, 2015 at 10:13 AM, Gianfranco Murador > wrote: > > > Hello Igniters , > > I take the discussion to understand if I have the proper approval from > the > > community > > for the early integration of Ignite with Drools and JBPM. > > I would ask if you can then create a new repository in > > https://github.com/apacheignite. > > > > Gianfranco, what is your github username, so I can invite you? > > > > Thanks, > > Regards, Gianfranco > > > > > > -- > > Gianfranco Murador > > Igniter and Software Engineer. > > > -- Gianfranco Murador Igniter and Software Engineer.
Re: JBPM and Drools integrations
Dmitriy, I get this error *Permission to apacheignite/drools-ignite.git denied* , when I push on this repo : https://github.com/apacheignite/drools-ignite. Maybe you need to add write permissions to my user. Thanks 2015-09-30 11:05 GMT+02:00 Dmitriy Setrakyan : > Invitation is sent and "drools-ignite" repository is created. Let me now if > you have troubles accessing it. > > D. > > On Wed, Sep 30, 2015 at 10:46 AM, Gianfranco Murador > wrote: > > > My github username is murador. > > Thank you. > > > > 2015-09-30 10:39 GMT+02:00 Dmitriy Setrakyan : > > > > > On Wed, Sep 30, 2015 at 10:13 AM, Gianfranco Murador < > mura...@apache.org > > > > > > wrote: > > > > > > > Hello Igniters , > > > > I take the discussion to understand if I have the proper approval > from > > > the > > > > community > > > > for the early integration of Ignite with Drools and JBPM. > > > > I would ask if you can then create a new repository in > > > > https://github.com/apacheignite. > > > > > > > > > > Gianfranco, what is your github username, so I can invite you? > > > > > > > > > > Thanks, > > > > Regards, Gianfranco > > > > > > > > > > > > -- > > > > Gianfranco Murador > > > > Igniter and Software Engineer. > > > > > > > > > > > > > > > -- > > Gianfranco Murador > > Igniter and Software Engineer. > > > -- Gianfranco Murador Igniter and Software Engineer.
Re: Sergey Evdokimov Tickets
Chandresh , Thank you, any help is welcome. We update as soon we can replicate the issue 2015-09-30 11:25 GMT+02:00 chandresh pancholi < chandreshpancholi...@gmail.com>: > Gian, > I would love to help you with IGNITE-417. > > Let me know when and where to start. > > Thanks > > On Wed, Sep 30, 2015 at 2:30 PM, Dmitriy Setrakyan > wrote: > > > On Wed, Sep 30, 2015 at 10:18 AM, Gianfranco Murador > > > wrote: > > > > > Some ticket seem resolved , but the state has been left "open" . I like > > to > > > work on IGNITE-417 and IGNITE-888 with the right help from community; > > > > > > > Gianfranco, I am not sure IGNITE-888 is a valid ticket. I personally do > > knot know what it means. Looks like Sergey E. was the one who filed the > > ticket. Does anyone know what this ticket is about? > > > > As far as IGNITE-417, I think this ticket might be valid, although there > is > > no reproducible test. I would start from trying to reproduce it in a test > > (it might be that it has been fixed already in 1.4, in which case we > should > > close the ticket) > > > > D. > > > > > > > 2015-09-30 9:42 GMT+02:00 Dmitriy Setrakyan : > > > > > > > On Wed, Sep 30, 2015 at 9:01 AM, Yakov Zhdanov > > > > wrote: > > > > > > > > > Correct. I meant unassign. > > > > > > > > > > There are no critical tickets in my view - > > > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20%20status%20!%3D%20closed%20AND%20assignee%20%3D%20sevdokimov-gg%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > > > > > > > > > > > > I think that community should feel free to grab these tickets if they > > > have > > > > not had any activity for a while. > > > > > > > > > > > > > > > > > > --Yakov > > > > > > > > > > 2015-09-29 19:44 GMT+03:00 Dmitriy Setrakyan < > dsetrak...@apache.org > > >: > > > > > > > > > > > On Tue, Sep 29, 2015 at 4:45 PM, Yakov Zhdanov < > > yzhda...@apache.org> > > > > > > wrote: > > > > > > > > > > > > > Hi! > > > > > > > > > > > > > > I want to ask if Sergey is going to continue working on tickets > > > > > assigned > > > > > > to > > > > > > > him? If not, we will reassign them in 72 hours. > > > > > > > > > > > > > > > > > > > I thought you meant "un-assign" not "reassign". Do we know if > there > > > are > > > > > any > > > > > > critical tickets that Sergey was working on? > > > > > > > > > > > > > > > > > > > > > > > > > > Thanks! > > > > > > > > > > > > > > --Yakov > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Gianfranco Murador > > > Igniter and Software Engineer. > > > > > > > > > -- > Chandresh Pancholi > Senior Software Engineer > Flipkart.com > Email-id:chandresh.panch...@flipkart.com > Contact:08951803660 > -- Gianfranco Murador Igniter and Software Engineer.
Re: JBPM and Drools integrations
It works, thank you. 2015-09-30 18:14 GMT+02:00 Dmitriy Setrakyan : > Gianfranco, please try again. I had to change some settings on the repo. > > D. > > On Wed, Sep 30, 2015 at 2:50 PM, Gianfranco Murador > wrote: > > > Dmitriy, > > I get this error *Permission to apacheignite/drools-ignite.git denied* > , > > when I push on this repo : https://github.com/apacheignite/drools-ignite > . > > Maybe you need to add write permissions to my user. > > Thanks > > > > 2015-09-30 11:05 GMT+02:00 Dmitriy Setrakyan : > > > > > Invitation is sent and "drools-ignite" repository is created. Let me > now > > if > > > you have troubles accessing it. > > > > > > D. > > > > > > On Wed, Sep 30, 2015 at 10:46 AM, Gianfranco Murador < > mura...@apache.org > > > > > > wrote: > > > > > > > My github username is murador. > > > > Thank you. > > > > > > > > 2015-09-30 10:39 GMT+02:00 Dmitriy Setrakyan >: > > > > > > > > > On Wed, Sep 30, 2015 at 10:13 AM, Gianfranco Murador < > > > mura...@apache.org > > > > > > > > > > wrote: > > > > > > > > > > > Hello Igniters , > > > > > > I take the discussion to understand if I have the proper approval > > > from > > > > > the > > > > > > community > > > > > > for the early integration of Ignite with Drools and JBPM. > > > > > > I would ask if you can then create a new repository in > > > > > > https://github.com/apacheignite. > > > > > > > > > > > > > > > > Gianfranco, what is your github username, so I can invite you? > > > > > > > > > > > > > > > > Thanks, > > > > > > Regards, Gianfranco > > > > > > > > > > > > > > > > > > -- > > > > > > Gianfranco Murador > > > > > > Igniter and Software Engineer. > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Gianfranco Murador > > > > Igniter and Software Engineer. > > > > > > > > > > > > > > > -- > > Gianfranco Murador > > Igniter and Software Engineer. > > > -- Gianfranco Murador Igniter and Software Engineer.
Re: Name of .Net product
+1 Ignite.NET 2015-10-07 18:31 GMT+02:00 Konstantin Boudnik : > Technically, "Apache Ignite" is the project trademark (which could be > registered, if needed). Hence the longer name is probably more correct. > > Cos > > On Wed, Oct 07, 2015 at 07:31AM, Dmitriy Setrakyan wrote: > > +1 for Ignite.NET or Apache Ignite.NET. I think both should be valid. > > > > On Wed, Oct 7, 2015 at 7:12 AM, Vladimir Ozerov > > wrote: > > > > > Raul, good point! > > > > > > I have no information about .Net trademark, but other products use > ".NET" > > > without a blank space. > > > > > > On Wed, Oct 7, 2015 at 4:37 PM, Raul Kripalani > wrote: > > > > > > > I like Ignite.NET. > > > > > > > > I wonder if the .NET portion may be trademarked by Microsoft. If > that's > > > the > > > > case, I guess we cannot put a blank space between Ignite and .NET > (Ignite > > > > .NET), it'll all need to be a single word, like proposed. > > > > > > > > Regards, > > > > > > > > *Raúl Kripalani* > > > > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big > Data and > > > > Messaging Engineer > > > > http://about.me/raulkripalani | > http://www.linkedin.com/in/raulkripalani > > > > http://blog.raulkr.net | twitter: @raulvk > > > > > > > > On Wed, Oct 7, 2015 at 1:04 PM, Vladimir Ozerov < > voze...@gridgain.com> > > > > wrote: > > > > > > > > > Igniters, > > > > > > > > > > Let's agree on the final name of our .Net product. For now it is > > > > referenced > > > > > in various places as "Apache Ignite .Net", "Apache Ignite for > .Net", > > > > > "Apache Ignite .Net platform", etc.. > > > > > > > > > > Ports of other Java projects to .Net are usually named as > > > > "[Product].NET". > > > > > E.g. Akka.NET, Spring.NET. > > > > > > > > > > I suggest use the same scheme and pick the name "Apache > Ignite.NET". > > > > > > > > > > Any ideas or objections? > > > > > > > > > > Vladimir. > > > > > > > > > > > > > -- Gianfranco Murador Igniter and Software Engineer.
Re: [VOTE] Establishing duration of Apache Ignite Chair rotation
+1 (binding) 2015-10-14 15:46 GMT+02:00 Yakov Zhdanov : > +1 (binding) > > --Yakov > > 2015-10-14 1:30 GMT+03:00 Konstantin Boudnik : > > > Hi! > > > > As discussed in the "[DISCUSS] PMC Chair rotation" thread last month, I > > propose > > that we adopt a rule allowing for a Apache Ignite Chair rotation on a > > yearly > > basis. The proposed policy is this: > > - a position of an Apache Ignite Chair gets elected for a year > > - after a year passes it is expected of the active Chair to start a > > [DISCUSS] email thread on priv...@ignite.apache.org asking PMC > > members to > > make a nomination for the next year > > - it is perfectly acceptable for the active chair to nominate him or > > herself > > - there is no limit on the number of terms that one person can serve as > > an > > Apache Ignite Chair. > > > > Each term, however is exactly one year. > > > > [ ] +1 Adopt the Apache Ingite Chair rotation policy > > [ ] +0 > > [ ] -1 Do not adopt the proposed policy (please provide a reason) > > > > This VOTE will be held open for at least 72 hours. > > > > Thanks, > > Cos > > > -- Gianfranco Murador Igniter and Software Engineer.
Re: log4j2 garbage files
Hi Artem, I have no write permission to merge the fix On Oct 30, 2015 11:43 AM, "Artem Shutak" wrote: > Hi Raul, > > Oh, I was sure I deleted these files. > > Fixed in my PR: https://github.com/apache/ignite/pull/188. Raul, > Gianfranco, please, review and merge the fix. > > Thanks, > -- Artem -- > > On Thu, Oct 29, 2015 at 9:46 PM, Raul Kripalani wrote: > > > Gianfranco, Artem, > > > > Could you please check why we have garbage source files ending in a > twiddle > > ~ inside the log4j2 module? > > > > > > > https://github.com/apache/ignite/tree/master/modules/log4j2/src/main/java/org/apache/ignite/logger/log4j2 > > > > Thanks, > > > > *Raúl Kripalani* > > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and > > Messaging Engineer > > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani > > http://blog.raulkr.net | twitter: @raulvk > > >
Re: Hello
Welcome Josè , take a look at these guidelines: https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute and check in the opened jira if there is one you wish to work on it. Thanks , Gianfranco 2015-10-31 1:05 GMT+01:00 jose renato pequeno : > Good evening for everyone! > My name´s José Renato Pequeno. > I work in biggest e-commerce of South America with IT Specialist with > focus in Big Data, working with Hadoop and its ecosystem. > I´d like to contribute with the Ignite team! > Best Regards. > José Renato Pequeno > -- Gianfranco Murador Igniter and Software Engineer.
Re: Ignite with Drools
Hello Dmitriy , in this period I'm quite busy, but I'd like to continue to develop the integration module. If you need space for other projects I can still host the project under my root github. Sorry for my absence, but I hope to have the time available after the first half of December. Regards, Gianfranco 2015-11-28 6:30 GMT+01:00 Dmitriy Setrakyan : > Gianfranco, > > I just found this repository for Drools integration: > https://github.com/apacheignite/drools-ignite > > It looks a bit abandoned. Do you have plans to pick it back up? > > Thanks, > D. > -- Gianfranco Murador Igniter and Software Engineer.
Re: [VOTE] Apache Ignite 1.5.0.final RC3
+1 (binding) 2015-12-30 15:09 GMT+01:00 Semyon Boikov : > +1 > > On Tue, Dec 29, 2015 at 1:54 PM, Anton Vinogradov wrote: > > > Dear Sirs! > > > > We have uploaded release candidate to > > https://dist.apache.org/repos/dist/dev/ignite/1.5.0.final-rc3/ > > > > This is very important release containing initial versions of Ignite.NET > > and Ignite C++ and many other important features. > > > > Tag name is > > 1.5.0.final-rc3 > > > > 1.5.0 changes: > > * Ignite.NET: Initial Release. > > * Ignite C++: Initial Release. > > * Massive performance improvements for cache operations and SQL. > > * Added new binary cache object marshalling implementation. > > * Added IgniteSemaphore data structure. > > * Added MQTT Streamer. > > * Added Twitter Streamer. > > * Added Ignite Sink (integration with Apache Flume). > > * Fixed optimistic serializable transactions: implemented "deadlock-free" > > locking algorithm. > > * Fixed failover for continuous queries. > > * Fixed compilation and runtime errors under OpenJDK and IBM JDK. > > * Fixed Integer.size limitation for cache. > > * Fixed and improved cache types configuration. > > * Fixed cache rebalancing. > > * Many stability and fault-tolerance fixes. > > * Added example to demonstrate the usage of EntryProcessor. > > > > Complete list of closed issues: > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%201.5%20AND%20status%20%3D%20closed > > > > DEVNOTES > > > > > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/1.5.0.final-rc3 > > > > RELEASENOTES > > > > > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/1.5.0.final-rc3 > > > > Please start voting. > > > > +1 - to accept Apache Ignite 1.5.0.final-rc3 > > 0 - don't care either way > > -1 - DO NOT accept Apache Ignite 1.5.0.final-rc3 (explain why) > > > > This vote will go for 72 hours. > > > -- Gianfranco Murador Igniter and Software Engineer.
Re: Great blog about Ignite!
Hi Dmitriy, I'm planning to write some article about about the modules for C++ and C#.I'm finishing the design for integration with drools that I hope to be finished by this summer, the module will also be documented in the blog . The blog is here: http://quite-nice-coding.blogspot.it/ Regards, Gianfranco Hi: If I write the content will be released to: Https://www.zybuluo.com/liyuj/note/230739 I say "authority", mainly refers to the relevant content, if written by the designer, will be more depth. 在 16/3/9 11:16, Dmitriy Setrakyan 写道: > On Thu, Mar 3, 2016 at 11:45 PM, 李玉珏@163 <18624049...@163.com> wrote: > > I wrote some, but it was not deep enough, and the authority was not enough. >> >> I think we should still publish it. Can you explain what you meant by the > “authority”? > > > 在 16/3/4 09:39, Dmitriy Setrakyan 写道: >> >> Couldn’t agree more. It will be great if more community members would >> >>> volunteer to write blogs or articles. >>> >>> >> >>
Re: About Infinispan
Hello Dmitry, I can do this comparison , as I am doing integration with drools getting ideas from what is done with Infinispan. Regards, Gianfranco We definitely should do a comparison to Infinispan. Anyone in the community is interested in picking this up and updating the website? D. On Thu, Mar 10, 2016 at 5:09 AM, 李玉珏@163 <18624049...@163.com> wrote: > From the functionality, I just feel that the two are comparable. > From the point of view of publicity can strengthen the advantages of > Ignite, such as ANSI SQL Query IGFS, and so on. > > 在 16/3/10 20:41, Yakov Zhdanov 写道: > > Hello! >> >> I am afraid I don't fully understand you. Can you please explain what you >> suggest in other words? Are you talking about benchmarks for comparison? >> >> --Yakov >> >> 2016-03-10 18:38 GMT+06:00 李玉珏@163 <18624049...@163.com>: >> >> Hi, >>> >>> Can community for Infinispan and Ignite in function to make a contrast? >>> Like Redis, Gemfire, Hazelcast, Coherence? >>> >>> >>> > >
Re: [VOTE] Apache Ignite 1.6.0 RC1
notifications. > > > > > >> * Fixed background cache partition map exchange not to flood > > > network. > > > > > >> * Fixed BinaryContext to honor custom loader set through > > > > > >> IgniteConfiguration. > > > > > >> * Fixed BinaryObjectOffHeapImpl leak to public code. > > > > > >> * Fixed cluster stability with 500+ clients. > > > > > >> * Fixed continuous queries to send filter factory instead of > > filter. > > > > > >> * Fixed continuous query deployment in case originating node has > > > left. > > > > > >> * Fixed issues with continuous query. > > > > > >> * Fixed deadlock in services deployment when Spring is used. > > > > > >> * Fixed discovery and node start procedure issues that may cause > > > > > slowdowns > > > > > >> during larger topologies start (>100 nodes). > > > > > >> * Fixed eviction policy notification if swap or off heap is > > enabled > > > > and > > > > > an > > > > > >> entry is not loaded during preloading. > > > > > >> * Fixed excessive thread stack usage in case of high contention > on > > > > cache > > > > > >> entries. > > > > > >> * Fixed execution of Splunk MapReduce jobs on top of Ignite MR. > > > > > >> * Fixed GridClosureProcessor internal closures to be > deserialized > > by > > > > > >> BinaryMarshaller. > > > > > >> * Fixed issue with AWS dependencies. > > > > > >> * Fixed java proxies deserialization with optimized marshaller. > > > > > >> * Fixed local store behavior at cross cache transactions. > > > > > >> * Fixed marshalling of Java collection and maps for > > > BinaryMarshaller. > > > > > >> * Fixed memory leak in IgniteH2Indexing. > > > > > >> * Fixed NPE during rebalancing. > > > > > >> * Fixed NPE in GridMergeIndex. > > > > > >> * Fixed OOME when OFFHEAP_TIERED mode is used. > > > > > >> * Fixed potential thread starvation during cache rebalancing. > > > > > >> * Fixed race condition on load cache on changing topology. > > > > > >> * Fixed race in marshalling logic that could arise when several > > > nodes > > > > > are > > > > > >> running on the same host. > > > > > >> * Fixed redeployment issues happened with ScanQueries filters. > > > > > >> * Fixed service proxy not to make remote call for methods > declared > > > in > > > > > >> java.lang.Object. > > > > > >> * Fixed several ClassNotFoundException in OSGi environment. > > > > > >> * Fixed SKIP_STORE flag behavior for transaction entry. > > > > > >> * Fixed support for classes with equal simple name for binary > > > > > marshaller. > > > > > >> * Fixed system caches not to use user-defined > > > > TransactionConfiguration. > > > > > >> * Fixed the issue when CacheStore was updated even if > > EntryProcessor > > > > > didn't > > > > > >> update an entry. > > > > > >> * Fixed thread safety for TcpDiscoveryMulticastIpFinder. > > > > > >> * Fixed unintentional deserialization of BinaryObjects in > OFFHEAP > > > mode > > > > > with > > > > > >> peer class loading enabled. > > > > > >> * Fixed UTF-16 surrogate pairs marshalling. > > > > > >> * Fixed value copying in entry processor with > OptimizedMarshaller. > > > > > >> * Fixed web session clustering with WebLogic. > > > > > >> * Hadoop: fixed a bug causing exception during MR planning when > > > input > > > > > split > > > > > >> file doesn't exist. > > > > > >> * IGFS: Added configuration flag to disable default path modes > > under > > > > > >> "/ignite" folder. > > > > > >> * IGFS: Added pluggable factory interface for Hadoop FileSystem > > > > > creation. > > > > > >> * IGFS: Fixed file properties when running over secondary file > > > system. > > > > > >> * IGFS: Fixed issues with Kerberized HDFS. > > > > > >> * IGFS: Massive performance and stability fixes. > > > > > >> * Improved marshaller behavior during cluster topology change. > > > > > >> * Mesos integration: added possibility to load Ignite package > from > > > > file > > > > > >> system. > > > > > >> * Optimized cache 'get' operations on affinity node. > > > > > >> * Optimized memory usage on server nodes to allow more client > > > > > connections. > > > > > >> * Passed update notifier flag to discovery data to be sure that > > all > > > > > cluster > > > > > >> nodes have the same notifier status as the first node. > > > > > >> * Performance optimization for transactions that do not acquire > > > locks. > > > > > >> * ScanQueries over local partitions performance optimisation. > > > > > >> * Support of package-private implementations for Ignite > Services. > > > > > >> * Supported Ignite Compute tasks cancellation for Ignite.NET. > > > > > >> * Visor CMD: Added ability to attach custom scripts to alerts. > > > > > >> * Web sessions: minor fix to prevent NullPointerException in > some > > > > > special > > > > > >> case. > > > > > >> * Web sessions: user session classes are no longer needed on > > server > > > > > nodes. > > > > > >> * A lot of stability and fault-tolerance fixes. > > > > > >> > > > > > >> Complete list of closed issues: > > > > > >> > > > > > >> > > > > > > > > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%201.6%20AND%20status%20%3D%20closed > > > > > >> > > > > > >> DEVNOTES > > > > > >> > > > > > >> > > > > > > > > > > > > > > > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/1.6.0-rc1 > > > > > >> > > > > > >> RELEASENOTES > > > > > >> > > > > > >> > > > > > > > > > > > > > > > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/1.6.0-rc1 > > > > > >> > > > > > >> Please start voting. > > > > > >> > > > > > >> +1 - to accept Apache Ignite 1.6.0-rc1 > > > > > >> 0 - don't care either way > > > > > >> -1 - DO NOT accept Apache Ignite 1.6.0-rc1 (explain why) > > > > > >> > > > > > >> This vote will go for 72 hours. > > > > > >> > > > > > > > > > > > > > > > > > > > > -- Gianfranco Murador Igniter and Software Engineer.
