Re: visor-console compilation error

Some research around has confirmed that this is indeed a scala problem: the damn thing doesn't work properly with encrypted disks. Well, yet another reason not to use that language until they find a way to write a decent compiler. Looks like my original feeling that it is a tech from 1983 was right

Re: visor-console compilation error

I am running on XFS file system and as pretty much all Linux ones there's limits on the path length. And filename lengths are limited to 255 (in some implementations 256) chars. So, it is either maven or scala compiler. I suspect the latter, because Maven is polished beyond doubts. Besides, Scala c

Re: Brainstorming about Reactive Streams

Yes, lets first explore how reactive-streams can be useful for Ignite. Adding one more candidate to list http://projectreactor.io/docs/, as this project: Is for fast-data applications Team are core contributors to the Reactive Streams Specification

Re: IGNITE-534 JMS 1.1 Streamer - Work completed

Hey guys, I've documented this feature on readme.io, on branch 1.4: https://apacheignite.readme.io/v1.4/docs/jms-data-streamer. Since this is the first piece of document I contribute, your suggestions are welcome. Regards, *Raúl Kripalani* Apache Camel PMC Member & Committer | Enterprise Archit

Re: Nodes starts in tests

Vladimir, Setting setLocalHost to 127.0.0.1 with shared ipfinder did not help me much on my mac, at least on tests with awaitPartitionMapExchange. As far as I understand we don't need to do awaitPartitionMapExchange when starting cache dynamically on stable topology? Sergi 2015-09-20 14:25 GMT+

Re: Brainstorming about Reactive Streams

Guys, I think you are digging too deep in implementation possibilities right away, may be lets start from simpler things? I don't know much about reactive streams and probably not everyone in the community that educated as well :) It would be nice to start with a quick overview of what are they a

Re: Brainstorming about Reactive Streams

Yeah, the idea would be to wrap RxJava 1.0 with the adapter and only use the Reactive Streams API where possible from within Ignite. Nevertheless, the ReactiveX API would also be accessible in case we want to do stuff with Hystrix too. Raúl. On 20 Sep 2015 16:39, "Vishal Garg" wrote: > https://

Re: Brainstorming about Reactive Streams

https://github.com/ReactiveX/RxJava/wiki/R eactive-Streams +1 on your approach ( if we are wrapping 1.0 with adapters??) Raul it looks like there is a path to convergence in RxJava 2.0, but above link mentions that you could use the standard + integration modules with wrappers on core 1.0 Apis. W

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 Ign

Re: visor-console compilation error

Hmmm, as I see in log "[ERROR] error: File name too long" Looks like OS / compiler limitation for file name. Cos, how to reproduce this? I should fork some project on GitHub and run some maven comand? Could you provide instructions (branch name, mave command)? On Sun, Sep 20, 2015 at 2:38 P

Brainstorming about Reactive Streams

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, batc

Re: OpenSource.com looking for content

Hi Rich, The Apache Ignite community will be interested in running an article. Unless there are other volunteers, I can write the 1st article myself, and we can have other community members participate as well. Please let us know how to proceed. D. On Wed, Sep 16, 2015 at 11:57 PM, Rich Bowen w

Fwd: Nodes starts in tests

+1 Sergi idea Create/destroy cache with unique names should be enough to isolated test logic. If failed test case depends which tests were executed (or weren't executed) earlier the it means a bug or non-determenistic test code. -- Forwarded message -- From: Dmitriy Setrakyan Da

Re: Nodes starts in tests

We can analyze how much time is spent in nodes start/stop via build logs. I think this will be quiet significant amount. I would try Sergi's approach in new tests we ads and see what tests can be reapproached and what we can gain from it. Yakov On Sep 20, 2015 14:18, "Vladimir Ozerov" wrote: >

Re: Nodes starts in tests

This Friday I ran unit tests which starts about 10 nodes in a single JVM. It took about a second or so on Windows (!!!) when localhost is set to 127.0.0.1 and IP finder is shared. I believe with can already gain signicant speedup with only two steps: 1) Fix tests where nodes misatkenly start in "b

Re: Nodes starts in tests

On Sun, Sep 20, 2015 at 1:34 PM, Branko Čibej wrote: > On 20.09.2015 10:11, Yakov Zhdanov wrote: > > Very cool idea! However this will not be working in 100% cases since > > sometimes we need custom grid configurations, SPIs, etc, but for > > significant number of tests this will work. > > This i

Re: Nodes starts in tests

Brane, to be fully accurate we should restart the machine and login to the OS to start each new test, but this is an overhead. In terms of Ignite in most cases Serj's idea will be fine, I think. I absolutely agree on accuracy point with you. It should never suffer. --Yakov 2015-09-20 13:34 GMT+

Re: Nodes starts in tests

On 20.09.2015 10:11, Yakov Zhdanov wrote: > Very cool idea! However this will not be working in 100% cases since > sometimes we need custom grid configurations, SPIs, etc, but for > significant number of tests this will work. This is actually, IMO, a very bad idea. One of the most important princi

Re: Nodes starts in tests

Very cool idea! However this will not be working in 100% cases since sometimes we need custom grid configurations, SPIs, etc, but for significant number of tests this will work. --Yakov 2015-09-20 11:00 GMT+03:00 Sergi Vladykin : > Guys, > > A little observation. We have really many tests which

Nodes starts in tests

Guys, A little observation. We have really many tests which start and stop nodes for each test method. Example is IgniteCacheAbstractQuerySelfTest, it contains about 30 test methods and 3 subclasses. In beforeTest method it starts nodes in afterTest it stops them, while cache setup is the same. W

visor-console compilation error

getting this weird error: [INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @ ignite-visor-console --- [INFO] /bigtop/output/ignite-hadoop/ignite-hadoop-1.4/modules/visor-console/src/main/scala:-1: info: compiling [INFO] Compiling 24 source files to /bigtop/output/ignite-hadoop