Re: version names

Yeah, tag names need to be fixed going forward - they look funny for sure. Something like release-x.y.z would be more preferrable. Cos On Sun, Sep 27, 2015 at 03:59PM, Raul Kripalani wrote: > On Sun, Sep 27, 2015 at 10:20 AM, Konstantin Boudnik wrote: > > > On Sat, Sep

Re: version names

On Sun, Sep 27, 2015 at 3:06 AM, Yakov Zhdanov wrote: > Cos, believe me there will be efforts. How about maven poms and automated > procedures? This will need to be fixed and retested. I want to avoid it > unless it's absolutely needed. > I agree with Yakov. We have not had

[GitHub] ignite pull request: IGNITE-429: Implement IgniteStormStreamer to ...

GitHub user murador opened a pull request: https://github.com/apache/ignite/pull/107 IGNITE-429: Implement IgniteStormStreamer to stream data from Apache Storm The test was successful with the latest changes . The operation of the stream is different compared to the one described

Re: version names

On Sun, Sep 27, 2015 at 10:20 AM, Konstantin Boudnik wrote: > On Sat, Sep 26, 2015 at 09:23PM, Raul Kripalani wrote: > > Agree. And we should also normalise tag names and branch names in Git if > > they aren't (cannot check now). > > Tag names aren't much of the concern IMO, but

Re: Semaphore issue

Hi Vladisav, Welcome to the Ignite community! I have added you to Ignite Jira contributors and assigned the IGNITE-638 ticket to you. Going forward, you will be able to assign other tickets to yourself as well. Please find instructions on how to contribute to Ignite here:

Re: After setting streamer and ignite,getting NULL

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); 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: >

Re: After setting streamer and ignite,getting NULL

Dmitriy, In storm, topologies run continuously but in our Unit test we are running them only for 20sec. and this the way to do it in Storm. On Mon, Sep 28, 2015 at 2:08 AM, Dmitriy Setrakyan wrote: > On Sun, Sep 27, 2015 at 1:36 PM, chandresh pancholi < >

Re: After setting streamer and ignite,getting NULL

On Sun, Sep 27, 2015 at 1:43 PM, chandresh pancholi < chandreshpancholi...@gmail.com> wrote: > Dmitriy, > In storm, topologies run continuously but in our Unit test we are running > them only for 20sec. and this the way to do it in Storm. > I generally would avoid any sleep() calls at all. If

Re: version names

ignite-1.4.0-SNAPSHOT-rc1 created by attempt to release 1.4.0 but by mistake -SNAPSHOT has not been removed. On Sun, Sep 27, 2015 at 11:11 PM, Yakov Zhdanov wrote: > I am ok with jira version renaming. > > However, tag name "ignite-1.4.0-rc1" was created automatically, and

Re: SQL IN operator example

I've submitted the fix. Sergi 2015-09-26 2:33 GMT+03:00 vkulichenko : > Hi Kevin, > > I reproduced the issue and created a ticket [1]. I think it will be fixed > in > the next release. > > [1] https://issues.apache.org/jira/browse/IGNITE-1552 > > -Val > > > > -- >

Re: version names

I am ok with jira version renaming. However, tag name "ignite-1.4.0-rc1" was created automatically, and changing this will lead to lots of changes inside. We leave this as is. Correct? Tags like "1.3.3-p3" should be just removed. They were committed to apache git by mistake. Anton V., can you

Re: [VOTE] Apache Ignite 1.4.0 Release (RC1)

Thanks Raul, Any chance you can file a ticket describing this issue? D. On Sat, Sep 26, 2015 at 3:16 AM, Raul Kripalani wrote: > I found an issue with the OOTB experience. The igniterouter scripts are not > working because the MAIN_CLASS variable is using an outdated package

[jira] [Created] (IGNITE-1556) Create screen shots

Pavel Konstantinov created IGNITE-1556: -- Summary: Create screen shots Key: IGNITE-1556 URL: https://issues.apache.org/jira/browse/IGNITE-1556 Project: Ignite Issue Type: Sub-task

Re: After setting streamer and ignite,getting NULL

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

Re: After setting streamer and ignite,getting NULL

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 wrote: On Sun, Sep 27, 2015 at 1:36 PM,

Re: After setting streamer and ignite,getting NULL

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

Re: version names

Agree with Raul about having ignite-1.4 branch as release branch and having ignite- branches that correspond to JIRA issues. In Idea branches sorted alphabetically and it is already painful to search release branch among features branches. Let's at least have a prefix "release-" for release

Re: version names

Yakov versions in the pom files are _absolutely_ fine. E.g 1.5.0-SNAPSHOT right now. We are talking ONLY about JIRA, and JIRA version "ignite-1.5" doesn't really look like "1.5" in Maven repository. I don't really see what's the problem with the proposed names fix. Cos On Sun, Sep 27,

Re: version names

My concrete proposal: * Prefix branches with "something/", as many UI tools parse slashes into a tree structure. It's also what's proposed in Git flow. * Stay away from the word "release" for this, as it can be confused with the release branch for a single release. This branch represents a

Re: version names

On Sun, Sep 27, 2015 at 12:11AM, Yakov Zhdanov wrote: > I would leave it as is for now. Just to avoid any extra efforts. Another There's no effort in it, really - I can rename the versions in the next 15 seconds. Or better yet - let's leave 1.4* as it is, and start normalized version naming in

Re: After setting streamer and ignite,getting NULL

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

Re: version names

On Sun, Sep 27, 2015 at 02:20AM, Konstantin Boudnik wrote: > On Sat, Sep 26, 2015 at 09:23PM, Raul Kripalani wrote: > > Agree. And we should also normalise tag names and branch names in Git if > > they aren't (cannot check now). > > Tag names aren't much of the concern IMO, but it won't hurt

Re: version names

Cos, believe me there will be efforts. How about maven poms and automated procedures? This will need to be fixed and retested. I want to avoid it unless it's absolutely needed. Thanks! Yakov On Sep 27, 2015 12:24, "Konstantin Boudnik" wrote: > On Sun, Sep 27, 2015 at 12:11AM,

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