Re: Rebalancing speedup (IGNITE-1093)

[Anton Vinogradov]

Hello,
I've finished work on IGNITE-1093 & merged changes to master & 1.5.
Results listed at Issue <https://issues.apache.org/jira/browse/IGNITE-1093>

Main results are:
- Speed of rebalancing in case node joined increased ~twice (default
settings) at the same grid throughput,
- No GC hell happens now at the end of rebalancing.

On Tue, Aug 11, 2015 at 11:42 AM, Alexey Kuznetsov <akuznet...@gridgain.com>
wrote:

> Anton, I created issues IGNITE-1230 and IGNITE-1231 and linked them to
> https://issues.apache.org/jira/browse/IGNITE-1093.
>
> On Tue, Aug 11, 2015 at 3:31 PM, Anton Vinogradov <
> avinogra...@gridgain.com>
> wrote:
>
> > Alexey,
> >
> > Could you please create and link Jira issue with these wishes?
> >
> > On Tue, Aug 11, 2015 at 5:43 AM, Alexey Kuznetsov <
> akuznet...@gridgain.com
> > >
> > wrote:
> >
> > > Anton,
> > >
> > > I see that you are working on rebalancing could you as part of your
> > changes
> > > also introduce a boolean flag that will indicate that rebalance in
> > progress
> > > or not?
> > > Also there will be very useful if you add more details in node log when
> > > rebalancing started. Such as: how many partitions will be moved and on
> > what
> > > node and e.t.
> > >
> > >
> > > --
> > > Alexey Kuznetsov
> > > GridGain Systems
> > > www.gridgain.com
> > >
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>

Re: Ignite-1.5 Release

[Anton Vinogradov]

Branch ignite-1.5 created.

On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <avinogra...@gridgain.com>
wrote:

> I assume that correct link at 10th feature is
> https://issues.apache.org/jira/browse/IGNITE-638
>
> On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <yzhda...@apache.org> wrote:
>
>> Guys,
>>
>> I think we can start preparation to Ignite-1.5 release which will include
>> many interesting features:
>>
>> 1. Portable object API
>> https://issues.apache.org/jira/browse/IGNITE-1486
>>
>> 2. Ignite.NET and Ignite C++
>> https://issues.apache.org/jira/browse/IGNITE-1282
>>
>> 3. Optimistic serializable transactions
>> https://issues.apache.org/jira/browse/IGNITE-1607
>>
>> 4. Distributed SQL joins - we will be able to query non-collocated data as
>> well
>> https://issues.apache.org/jira/browse/IGNITE-1232
>>
>> 5. Enhanced Oracle and IBM JDK interoperability
>> https://issues.apache.org/jira/browse/IGNITE-1526
>>
>> 6. MQTT streamer
>> https://issues.apache.org/jira/browse/IGNITE-535
>>
>> 7. Continuous query failover
>> https://issues.apache.org/jira/browse/IGNITE-426
>>
>> 8. Significant transactional cache performance optimizations - I will
>> merge
>> these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
>>
>> 9. Many stability and fault-tolerance fixes.
>>
>> 10. I would also like to include distributed Semaphore. Vladislav, any
>> chance you can finish with it this week?
>> https://issues.apache.org/jira/browse/IGNITE-
>> <https://issues.apache.org/jira/browse/IGNITE-426>638
>>
>> Thanks to everyone involved! Guys, esp. assignees of mentioned issues,
>> please respond to this email and let us know when can we expect your
>> changes being merged to master and release branch?
>>
>> Can someone create ignite-1.5 release branch?
>>
>> --Yakov
>>
>
>

Re: Ignite-1.5 Release

[Anton Vinogradov]

I assume that correct link at 10th feature is
https://issues.apache.org/jira/browse/IGNITE-638

On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov  wrote:

> Guys,
>
> I think we can start preparation to Ignite-1.5 release which will include
> many interesting features:
>
> 1. Portable object API
> https://issues.apache.org/jira/browse/IGNITE-1486
>
> 2. Ignite.NET and Ignite C++
> https://issues.apache.org/jira/browse/IGNITE-1282
>
> 3. Optimistic serializable transactions
> https://issues.apache.org/jira/browse/IGNITE-1607
>
> 4. Distributed SQL joins - we will be able to query non-collocated data as
> well
> https://issues.apache.org/jira/browse/IGNITE-1232
>
> 5. Enhanced Oracle and IBM JDK interoperability
> https://issues.apache.org/jira/browse/IGNITE-1526
>
> 6. MQTT streamer
> https://issues.apache.org/jira/browse/IGNITE-535
>
> 7. Continuous query failover
> https://issues.apache.org/jira/browse/IGNITE-426
>
> 8. Significant transactional cache performance optimizations - I will merge
> these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
>
> 9. Many stability and fault-tolerance fixes.
>
> 10. I would also like to include distributed Semaphore. Vladislav, any
> chance you can finish with it this week?
> https://issues.apache.org/jira/browse/IGNITE-
> 638
>
> Thanks to everyone involved! Guys, esp. assignees of mentioned issues,
> please respond to this email and let us know when can we expect your
> changes being merged to master and release branch?
>
> Can someone create ignite-1.5 release branch?
>
> --Yakov
>

Re: [VOTE] Establishing duration of Apache Ignite Chair rotation

[Anton Vinogradov]

+1 (binding)

On Wed, Oct 14, 2015 at 4:47 PM, Gianfranco Murador 
wrote:

> +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: Name of .Net product

[Anton Vinogradov]

+1 Ignite.NET

On Wed, Oct 7, 2015 at 4:27 PM, chandresh pancholi <
chandreshpancholi...@gmail.com> wrote:

> What abount "Ignite DotN".
>
> On Wed, Oct 7, 2015 at 6:54 PM, Sergi Vladykin 
> wrote:
>
> > I like "Ignite.NET".
> >
> > Sergi
> >
> > 2015-10-07 15:04 GMT+03:00 Vladimir Ozerov :
> >
> > > 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.
> > >
> >
>
>
>
> --
> Chandresh Pancholi
> Senior Software Engineer
> Flipkart.com
> Email-id:chandresh.panch...@flipkart.com
> Contact:08951803660
>

Re: How to build ignite-1.5.0 from source code

[Anton Vinogradov]

Hi Ken,

Everything is correct. Version should be changed to 1.5.0 manually.

Please check DEVNOTES.txt for release instructions.

Quote from DEVNOTES.txt:
"Ensure you have RELEASE (not SNAPSHOT) version at Ignite poms. Maven
release plugin release:prepare goal can be used to make release tag."


On Fri, Nov 13, 2015 at 12:28 PM, Ken Cheng  wrote:

> Hi All,
>
> Even I am on the branch ignite-1.5, but when I try to build 1.5.0 release,
> the version I got is '1.5.0-SNAPSHOT'
>
> I checked the ignite/pom.xml but could not find any clue.
>
> What I am expecting is  '1.5.0' instead of '1.5.0-SNAPSHOT'
>
> Anybody can help me out?
>
>
>
> Many Thanks,
>
> kcheng
>

Re: Ignite 1.4

[Anton Vinogradov]

Seems worth specify "None" fixversion instead of 1.5.
Thoughts?

On Mon, Sep 7, 2015 at 2:50 PM, Sergey Kozlov  wrote:

> Guys
>
> We still have unclosed/unresolved more than 100 issues.
> Could you review issues assigned on you and move then on next release (1.5)
> if it won't be done for 1.4?
>
> Thanks!
>
> On Fri, Sep 4, 2015 at 3:24 PM, Vladimir Ozerov 
> wrote:
>
> > Please disregard p.2 and p.3 as they are out of Ignite scope.
> >
> > On Fri, Sep 4, 2015 at 3:23 PM, Vladimir Ozerov 
> > wrote:
> >
> > > Done.
> > > 1) No changes from my side to Ignite.
> > > 2) Added missing enterprise release notes for 7.3.3.
> > > 3) Updated enterprise release notes for 7.4.1.
> > >
> > > On Fri, Sep 4, 2015 at 2:46 PM, Yakov Zhdanov 
> > wrote:
> > >
> > >> Guys, I have updated release notes (IGNITE_HOME/RELEASE_NOTES.txt). I
> > >> think
> > >> Vladimir may have a couple more points to add. Vladimir, can you
> please
> > >> review?
> > >>
> > >> --Yakov
> > >>
> > >> 2015-09-04 14:05 GMT+03:00 Sergey Kozlov :
> > >>
> > >> > Version updated
> > >> >
> > >> > On Fri, Sep 4, 2015 at 1:10 PM, Yakov Zhdanov 
> > >> wrote:
> > >> >
> > >> > > Of course, we will release ignite-1.4.0. Anton V, can you please
> > fix?
> > >> > >
> > >> > > --Yakov
> > >> > >
> > >> > > 2015-09-04 12:50 GMT+03:00 Sergey Kozlov :
> > >> > >
> > >> > > > Igniters,
> > >> > > >
> > >> > > > Current version in released branch is 1.4.1 (there were issues
> > >> related
> > >> > to
> > >> > > > update notifier but it fixed now). Make sense to change to
> 1.4.0?
> > >> > > >
> > >> > > > On Fri, Sep 4, 2015 at 12:05 PM, Yakov Zhdanov <
> > >> yzhda...@gridgain.com>
> > >> > > > wrote:
> > >> > > >
> > >> > > > > Guys,
> > >> > > > >
> > >> > > > > We need to postpone release due to TC state. I think it will
> be
> > >> sent
> > >> > > for
> > >> > > > > vote Tue-Wed next week.
> > >> > > > >
> > >> > > > > --
> > >> > > > > Yakov Zhdanov, Director R
> > >> > > > > *GridGain Systems*
> > >> > > > > www.gridgain.com
> > >> > > > >
> > >> > > > > 2015-09-04 0:31 GMT+03:00 Dmitriy Setrakyan <
> > >> dsetrak...@apache.org>:
> > >> > > > >
> > >> > > > > > On Thu, Sep 3, 2015 at 1:31 AM, Sergey Kozlov <
> > >> > skoz...@gridgain.com>
> > >> > > > > > wrote:
> > >> > > > > >
> > >> > > > > > > Could someone provide the list of key features (fixes)
> added
> > >> for
> > >> > > > > release
> > >> > > > > > > 1.4?
> > >> > > > > > >
> > >> > > > > >
> > >> > > > > > I would also like to see the release notes for 1.4.
> > >> > > > > >
> > >> > > > > > Also, is the release still happening tomorrow? How close are
> > we?
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > >
> > >> > > > > > >
> > >> > > > > > > On Wed, Sep 2, 2015 at 3:51 PM, Yakov Zhdanov <
> > >> > yzhda...@apache.org
> > >> > > >
> > >> > > > > > wrote:
> > >> > > > > > >
> > >> > > > > > > > Yes, we will be moving almost all the issues to further
> > >> > versions.
> > >> > > > > > > >
> > >> > > > > > > > Branch has already been created.
> > >> > > > > > > >
> > >> > > > > > > > --Yakov
> > >> > > > > > > >
> > >> > > > > > > > 2015-09-01 22:14 GMT+03:00 Branko Čibej <
> br...@apache.org
> > >:
> > >> > > > > > > >
> > >> > > > > > > > > On 01.09.2015 20:46, Konstantin Boudnik wrote:
> > >> > > > > > > > > > On Tue, Sep 01, 2015 at 08:45PM, Sergey Kozlov
> wrote:
> > >> > > > > > > > > >> FYI: We've at least 161 unclosed issues planned to
> > fix
> > >> in
> > >> > > > > version
> > >> > > > > > > 1.4
> > >> > > > > > > > > > If there're so many issues to go - perhaps it makes
> > >> sense
> > >> > not
> > >> > > > to
> > >> > > > > > > branch
> > >> > > > > > > > > out
> > >> > > > > > > > > > this early to avoid extra merges?
> > >> > > > > > > > >
> > >> > > > > > > > > Or just go ahead and release 1.4 and get those issues
> > >> > addressed
> > >> > > > in
> > >> > > > > > 1.5.
> > >> > > > > > > > > It's not as if skipping a  "planned to fix" issue
> would
> > be
> > >> > the
> > >> > > > end
> > >> > > > > of
> > >> > > > > > > > > the world.
> > >> > > > > > > > >
> > >> > > > > > > > > -- Brane
> > >> > > > > > > > >
> > >> > > > > > > > >
> > >> > > > > > > >
> > >> > > > > > >
> > >> > > > > > >
> > >> > > > > > >
> > >> > > > > > > --
> > >> > > > > > > Sergey Kozlov
> > >> > > > > > >
> > >> > > > > >
> > >> > > > >
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > --
> > >> > > > Sergey Kozlov
> > >> > > > GridGain Systems
> > >> > > > www.gridgain.com
> > >> > > >
> > >> > >
> > >> >
> > >> >
> > >> >
> > >> > --
> > >> > Sergey Kozlov
> > >> >
> > >>
> > >
> > >
> >
>
>
>
> --
> Sergey Kozlov
>

Re: Ignite 1.4

[Anton Vinogradov]

Sounds good

On Mon, Sep 7, 2015 at 4:16 PM, Yakov Zhdanov <yzhda...@apache.org> wrote:

> I would introduce new version "pending". This way we can distinguish newly
> filed tickets (version default), postponed tickets (pending) and scheduled
> ones (e.g. 1.4)
>
> Thoughts?
>
> Thanks!
>
> Yakov
> On Sep 7, 2015 15:31, "Anton Vinogradov" <avinogra...@gridgain.com> wrote:
>
> > Seems worth specify "None" fixversion instead of 1.5.
> > Thoughts?
> >
> > On Mon, Sep 7, 2015 at 2:50 PM, Sergey Kozlov <skoz...@gridgain.com>
> > wrote:
> >
> > > Guys
> > >
> > > We still have unclosed/unresolved more than 100 issues.
> > > Could you review issues assigned on you and move then on next release
> > (1.5)
> > > if it won't be done for 1.4?
> > >
> > > Thanks!
> > >
> > > On Fri, Sep 4, 2015 at 3:24 PM, Vladimir Ozerov <voze...@gridgain.com>
> > > wrote:
> > >
> > > > Please disregard p.2 and p.3 as they are out of Ignite scope.
> > > >
> > > > On Fri, Sep 4, 2015 at 3:23 PM, Vladimir Ozerov <
> voze...@gridgain.com>
> > > > wrote:
> > > >
> > > > > Done.
> > > > > 1) No changes from my side to Ignite.
> > > > > 2) Added missing enterprise release notes for 7.3.3.
> > > > > 3) Updated enterprise release notes for 7.4.1.
> > > > >
> > > > > On Fri, Sep 4, 2015 at 2:46 PM, Yakov Zhdanov <yzhda...@apache.org
> >
> > > > wrote:
> > > > >
> > > > >> Guys, I have updated release notes
> (IGNITE_HOME/RELEASE_NOTES.txt).
> > I
> > > > >> think
> > > > >> Vladimir may have a couple more points to add. Vladimir, can you
> > > please
> > > > >> review?
> > > > >>
> > > > >> --Yakov
> > > > >>
> > > > >> 2015-09-04 14:05 GMT+03:00 Sergey Kozlov <skoz...@gridgain.com>:
> > > > >>
> > > > >> > Version updated
> > > > >> >
> > > > >> > On Fri, Sep 4, 2015 at 1:10 PM, Yakov Zhdanov <
> > yzhda...@apache.org>
> > > > >> wrote:
> > > > >> >
> > > > >> > > Of course, we will release ignite-1.4.0. Anton V, can you
> please
> > > > fix?
> > > > >> > >
> > > > >> > > --Yakov
> > > > >> > >
> > > > >> > > 2015-09-04 12:50 GMT+03:00 Sergey Kozlov <
> skoz...@gridgain.com
> > >:
> > > > >> > >
> > > > >> > > > Igniters,
> > > > >> > > >
> > > > >> > > > Current version in released branch is 1.4.1 (there were
> issues
> > > > >> related
> > > > >> > to
> > > > >> > > > update notifier but it fixed now). Make sense to change to
> > > 1.4.0?
> > > > >> > > >
> > > > >> > > > On Fri, Sep 4, 2015 at 12:05 PM, Yakov Zhdanov <
> > > > >> yzhda...@gridgain.com>
> > > > >> > > > wrote:
> > > > >> > > >
> > > > >> > > > > Guys,
> > > > >> > > > >
> > > > >> > > > > We need to postpone release due to TC state. I think it
> will
> > > be
> > > > >> sent
> > > > >> > > for
> > > > >> > > > > vote Tue-Wed next week.
> > > > >> > > > >
> > > > >> > > > > --
> > > > >> > > > > Yakov Zhdanov, Director R
> > > > >> > > > > *GridGain Systems*
> > > > >> > > > > www.gridgain.com
> > > > >> > > > >
> > > > >> > > > > 2015-09-04 0:31 GMT+03:00 Dmitriy Setrakyan <
> > > > >> dsetrak...@apache.org>:
> > > > >> > > > >
> > > > >> > > > > > On Thu, Sep 3, 2015 at 1:31 AM, Sergey Kozlov <
> > > > >> > skoz...@gridgain.com>
> > > > >> > > > > > wrote:
> > > > >> > > > > >
> > > > >> > > > > > > Could someone p

Re: Coding style changed!

[Anton Vinogradov]

Because we should have no mistakes at Ignite Java.
Checking that build logs contains no "Javadoc Warnings" helps to guarantee
that.

On Wed, Sep 2, 2015 at 2:02 PM, Sergi Vladykin <sergi.vlady...@gmail.com>
wrote:

> I think these warnings are valid, since we are really using proprietary
> APIs like Unsafe.
> Why should we hide them?
>
> Sergi
>
> 2015-09-01 16:29 GMT+03:00 Anton Vinogradov <avinogra...@gridgain.com>:
>
> > Hello,
> >
> > Since codestyle was changed javadoc starts to warn about using of
> > proprietary API.
> >
> > For example:
> > Javadoc Warnings
> >
> >
> ignite/modules/core/src/main/java/org/jsr166/ConcurrentLinkedDeque8.java:29:
> > warning: Unsafe is internal proprietary API and may be removed in a
> future
> > release
> > import sun.misc.Unsafe;
> >
> > Using import sun.misc.* solves this problem. IDEA codestyle can be
> > configured to use implicit imports for specified packages.
> > Specifying sun.misc, sun.nio.ch, com.sun.jmx.mbeanserver fixed build
> > output.
> >
> > Does anybody know other way to suspend this warning without suspending
> > others?
> >
> >
> > On Tue, Sep 1, 2015 at 9:21 AM, Denis Magda <dma...@gridgain.com> wrote:
> >
> > > I've updated '{ignite_folder}/idea/ignite_codeStyle.xml' to reflect the
> > > changes.
> > >
> > > --
> > > Denis
> > >
> > >
> > > On 8/31/2015 5:48 PM, Sergi Vladykin wrote:
> > >
> > >> Guys,
> > >>
> > >> As discussed, I changed all the imports in master to explicit ones.
> > >>
> > >> Settings for Idea you can see here:
> > >>
> > >>
> >
> https://issues.apache.org/jira/secure/attachment/12753298/Screen%20Shot%202015-08-31%20at%202.18.27%20PM.png
> > >>
> > >> Coding guidelines will be updated soon.
> > >>
> > >> Sergi
> > >>
> > >>
> > >
> >
>

Re: Coding style changed!

[Anton Vinogradov]

Problem fixed using top secret -XDenableSunApiLintControl param.
Thanks for stopping me :)

On Wed, Sep 2, 2015 at 3:30 PM, Anton Vinogradov <avinogra...@gridgain.com>
wrote:

> I did not found how to do that, will try to search again.
>
>
> On Wed, Sep 2, 2015 at 3:01 PM, Sergi Vladykin <sergi.vlady...@gmail.com>
> wrote:
>
>> Can we ignore this this type of warning in JavaDoc checker?
>> I don't like the idea of having some special imports because of that.
>>
>> Sergi
>>
>> 2015-09-02 14:32 GMT+03:00 Anton Vinogradov <avinogra...@gridgain.com>:
>>
>> > .. I mean at Ignite Javadoc
>> >
>> > On Wed, Sep 2, 2015 at 2:31 PM, Anton Vinogradov <
>> avinogra...@gridgain.com
>> > >
>> > wrote:
>> >
>> > > Because we should have no mistakes at Ignite Java.
>> > > Checking that build logs contains no "Javadoc Warnings" helps to
>> > guarantee
>> > > that.
>> > >
>> > > On Wed, Sep 2, 2015 at 2:02 PM, Sergi Vladykin <
>> sergi.vlady...@gmail.com
>> > >
>> > > wrote:
>> > >
>> > >> I think these warnings are valid, since we are really using
>> proprietary
>> > >> APIs like Unsafe.
>> > >> Why should we hide them?
>> > >>
>> > >> Sergi
>> > >>
>> > >> 2015-09-01 16:29 GMT+03:00 Anton Vinogradov <
>> avinogra...@gridgain.com>:
>> > >>
>> > >> > Hello,
>> > >> >
>> > >> > Since codestyle was changed javadoc starts to warn about using of
>> > >> > proprietary API.
>> > >> >
>> > >> > For example:
>> > >> > Javadoc Warnings
>> > >> >
>> > >> >
>> > >>
>> >
>> ignite/modules/core/src/main/java/org/jsr166/ConcurrentLinkedDeque8.java:29:
>> > >> > warning: Unsafe is internal proprietary API and may be removed in a
>> > >> future
>> > >> > release
>> > >> > import sun.misc.Unsafe;
>> > >> >
>> > >> > Using import sun.misc.* solves this problem. IDEA codestyle can be
>> > >> > configured to use implicit imports for specified packages.
>> > >> > Specifying sun.misc, sun.nio.ch, com.sun.jmx.mbeanserver fixed
>> build
>> > >> > output.
>> > >> >
>> > >> > Does anybody know other way to suspend this warning without
>> suspending
>> > >> > others?
>> > >> >
>> > >> >
>> > >> > On Tue, Sep 1, 2015 at 9:21 AM, Denis Magda <dma...@gridgain.com>
>> > >> wrote:
>> > >> >
>> > >> > > I've updated '{ignite_folder}/idea/ignite_codeStyle.xml' to
>> reflect
>> > >> the
>> > >> > > changes.
>> > >> > >
>> > >> > > --
>> > >> > > Denis
>> > >> > >
>> > >> > >
>> > >> > > On 8/31/2015 5:48 PM, Sergi Vladykin wrote:
>> > >> > >
>> > >> > >> Guys,
>> > >> > >>
>> > >> > >> As discussed, I changed all the imports in master to explicit
>> ones.
>> > >> > >>
>> > >> > >> Settings for Idea you can see here:
>> > >> > >>
>> > >> > >>
>> > >> >
>> > >>
>> >
>> https://issues.apache.org/jira/secure/attachment/12753298/Screen%20Shot%202015-08-31%20at%202.18.27%20PM.png
>> > >> > >>
>> > >> > >> Coding guidelines will be updated soon.
>> > >> > >>
>> > >> > >> Sergi
>> > >> > >>
>> > >> > >>
>> > >> > >
>> > >> >
>> > >>
>> > >
>> > >
>> >
>>
>
>

Re: Update version for master

[Anton Vinogradov]

Should it be 1.5.0-SNAPSHOT?

On Thu, Sep 3, 2015 at 1:32 PM, Yakov Zhdanov  wrote:

> Anton V, can you please do it?
>
> --Yakov
>
> 2015-09-03 12:05 GMT+03:00 Sergey Kozlov :
>
> > Hi
> >
> > Now we've branch ignite-1.4 for release thus make sense to update for
> > version for master to 1.5?
> >
> > --
> > Sergey Kozlov
> >
>

Added missing pages to Ignite documentation

[Anton Vinogradov]

Hello,

I've created new pages on redme.io.
These pages describe usage of Ignite expiry policies and topology validator.
Urls:
https://apacheignite.readme.io/docs/expiry-policies
https://apacheignite.readme.io/docs/topology-validation

Re: Coding style changed!

[Anton Vinogradov]

I did not found how to do that, will try to search again.


On Wed, Sep 2, 2015 at 3:01 PM, Sergi Vladykin <sergi.vlady...@gmail.com>
wrote:

> Can we ignore this this type of warning in JavaDoc checker?
> I don't like the idea of having some special imports because of that.
>
> Sergi
>
> 2015-09-02 14:32 GMT+03:00 Anton Vinogradov <avinogra...@gridgain.com>:
>
> > .. I mean at Ignite Javadoc
> >
> > On Wed, Sep 2, 2015 at 2:31 PM, Anton Vinogradov <
> avinogra...@gridgain.com
> > >
> > wrote:
> >
> > > Because we should have no mistakes at Ignite Java.
> > > Checking that build logs contains no "Javadoc Warnings" helps to
> > guarantee
> > > that.
> > >
> > > On Wed, Sep 2, 2015 at 2:02 PM, Sergi Vladykin <
> sergi.vlady...@gmail.com
> > >
> > > wrote:
> > >
> > >> I think these warnings are valid, since we are really using
> proprietary
> > >> APIs like Unsafe.
> > >> Why should we hide them?
> > >>
> > >> Sergi
> > >>
> > >> 2015-09-01 16:29 GMT+03:00 Anton Vinogradov <avinogra...@gridgain.com
> >:
> > >>
> > >> > Hello,
> > >> >
> > >> > Since codestyle was changed javadoc starts to warn about using of
> > >> > proprietary API.
> > >> >
> > >> > For example:
> > >> > Javadoc Warnings
> > >> >
> > >> >
> > >>
> >
> ignite/modules/core/src/main/java/org/jsr166/ConcurrentLinkedDeque8.java:29:
> > >> > warning: Unsafe is internal proprietary API and may be removed in a
> > >> future
> > >> > release
> > >> > import sun.misc.Unsafe;
> > >> >
> > >> > Using import sun.misc.* solves this problem. IDEA codestyle can be
> > >> > configured to use implicit imports for specified packages.
> > >> > Specifying sun.misc, sun.nio.ch, com.sun.jmx.mbeanserver fixed
> build
> > >> > output.
> > >> >
> > >> > Does anybody know other way to suspend this warning without
> suspending
> > >> > others?
> > >> >
> > >> >
> > >> > On Tue, Sep 1, 2015 at 9:21 AM, Denis Magda <dma...@gridgain.com>
> > >> wrote:
> > >> >
> > >> > > I've updated '{ignite_folder}/idea/ignite_codeStyle.xml' to
> reflect
> > >> the
> > >> > > changes.
> > >> > >
> > >> > > --
> > >> > > Denis
> > >> > >
> > >> > >
> > >> > > On 8/31/2015 5:48 PM, Sergi Vladykin wrote:
> > >> > >
> > >> > >> Guys,
> > >> > >>
> > >> > >> As discussed, I changed all the imports in master to explicit
> ones.
> > >> > >>
> > >> > >> Settings for Idea you can see here:
> > >> > >>
> > >> > >>
> > >> >
> > >>
> >
> https://issues.apache.org/jira/secure/attachment/12753298/Screen%20Shot%202015-08-31%20at%202.18.27%20PM.png
> > >> > >>
> > >> > >> Coding guidelines will be updated soon.
> > >> > >>
> > >> > >> Sergi
> > >> > >>
> > >> > >>
> > >> > >
> > >> >
> > >>
> > >
> > >
> >
>

Ignite Teamcity at Apache side

[Anton Vinogradov]

Hello,

As you may know we already have Ignite Teamcity server where contributors
can check it's patches. But, as Cos said before, this test environment
should be runned under apache hardware.

Apache test environment based on Jenkins, but it is not so simple to
migrate from TeamCity to Jenkins.

Is it possible to make Ignite test environment at Apache side using
TeamCity, not Jenkins?
TeamCity can be used under opensource license (
https://www.jetbrains.com/teamcity/buy/opensource.html).

Re: Update version for master

[Anton Vinogradov]

Version Updated

On Thu, Sep 3, 2015 at 3:29 PM, Raul Kripalani  wrote:

> On Thu, Sep 3, 2015 at 1:16 PM, Branko Čibej  wrote:
>
> > There hasn't been a 1.4.0 release package yet, so of course no tag?
> >
>
> Well, that would explain it ;-) But why is the POM version for both master
> and ignite-1.4 branches already on 1.4.1-SNAPSHOT in that case?
>
> https://github.com/apache/ignite/blob/master/pom.xml#L35
> https://github.com/apache/ignite/blob/ignite-1.4/pom.xml#L35
>
> Is the 1.4.0 release cut and under VOTE?
>
> 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: Added missing pages to Ignite documentation

[Anton Vinogradov]

Dmitriy,
TopologyValidator's javadoc was improved as a part of these changes.

On Thu, Sep 10, 2015 at 6:41 AM, Dmitriy Setrakyan <dsetrak...@apache.org>
wrote:

> Thanks Anton!
>
> By the way, I just noticed that the TopologyValidator has no javadoc.
> Perhaps it makes sense to add it as well?
>
> D.
>
> On Sat, Sep 5, 2015 at 11:15 PM, Anton Vinogradov <
> avinogra...@gridgain.com>
> wrote:
>
> > Hello,
> >
> > I've created new pages on redme.io.
> > These pages describe usage of Ignite expiry policies and topology
> > validator.
> > Urls:
> > https://apacheignite.readme.io/docs/expiry-policies
> > https://apacheignite.readme.io/docs/topology-validation
> >
>

Re: Added missing pages to Ignite documentation

[Anton Vinogradov]

Dmitriy,

Thanks for improving javadoc.
I've updated https://apacheignite.readme.io/docs/topology-validation according
to your changes.

On Fri, Sep 11, 2015 at 2:38 AM, Dmitriy Setrakyan <dsetrak...@apache.org>
wrote:

> Thanks Anton,
>
> I made a few edits. Please take a look and see if you agree.
>
> D.
>
> On Thu, Sep 10, 2015 at 3:08 AM, Anton Vinogradov <
> avinogra...@gridgain.com>
> wrote:
>
> > Done, thanks for tips
> >
> > On Thu, Sep 10, 2015 at 12:44 PM, Yakov Zhdanov <yzhda...@apache.org>
> > wrote:
> >
> > > I think that main docs should be in TopologyValidator interface. Other
> > > places should be briefly documented and contain a link to validator
> > > interface.
> > >
> > > Thanks!
> > >
> > > Yakov
> > > On Sep 10, 2015 11:22, "Anton Vinogradov" <avinogra...@gridgain.com>
> > > wrote:
> > >
> > > > Usage explaned at place where TopologyValidator used - at
> > > > CacheConfiguration.setTopologyValidator(tv).
> > > > Is it necessary to dublicate usage javadoc to TopologyValidator
> class?
> > > >
> > > > On Thu, Sep 10, 2015 at 11:00 AM, Dmitriy Setrakyan <
> > > dsetrak...@apache.org
> > > > >
> > > > wrote:
> > > >
> > > > > On Thu, Sep 10, 2015 at 12:35 AM, Anton Vinogradov <
> > > > > avinogra...@gridgain.com
> > > > > > wrote:
> > > > >
> > > > > > Dmitriy,
> > > > > > TopologyValidator's javadoc was improved as a part of these
> > changes.
> > > > > >
> > > > >
> > > > > I just checked in master, and this is the only javadoc I can find
> for
> > > > > TopologyValidator class:
> > > > >
> > > > > /**
> > > > >  * Topology validator.
> > > > >  */
> > > > >
> > > > > A bit too pithy for my taste :)
> > > > >
> > > > >
> > > > > > On Thu, Sep 10, 2015 at 6:41 AM, Dmitriy Setrakyan <
> > > > > dsetrak...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > Thanks Anton!
> > > > > > >
> > > > > > > By the way, I just noticed that the TopologyValidator has no
> > > javadoc.
> > > > > > > Perhaps it makes sense to add it as well?
> > > > > > >
> > > > > > > D.
> > > > > > >
> > > > > > > On Sat, Sep 5, 2015 at 11:15 PM, Anton Vinogradov <
> > > > > > > avinogra...@gridgain.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hello,
> > > > > > > >
> > > > > > > > I've created new pages on redme.io.
> > > > > > > > These pages describe usage of Ignite expiry policies and
> > topology
> > > > > > > > validator.
> > > > > > > > Urls:
> > > > > > > > https://apacheignite.readme.io/docs/expiry-policies
> > > > > > > > https://apacheignite.readme.io/docs/topology-validation
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

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

[Anton Vinogradov]

Ignite 1.4.0 successfuly released to
https://dist.apache.org/repos/dist/release/ignite/1.4.0/
Site will be updated soon.

On Mon, Sep 28, 2015 at 4:13 PM, Yakov Zhdanov <yzhda...@apache.org> wrote:

> Hello!
>
> Apache Ignite 1.4.0 release (RC1) has been accepted.
>
> 9 "+1" votes received.
>
> Here are the votes received:
>
>- Denis Magda (binding)
>- Anton Vinogradov (binding)
>- Alexey Kuznetsov (binding)
>- Sergi Vladykin (binding)
>- Gianfranco Murador (binding)
>- Vladimir Ozerov (binding)
>- Raul Kripalani (binding)
>- Konstantin Boudnik (binding)
>- chandresh pancholi
>
> Here is the link to vote thread -
>
> http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-1-4-0-Release-RC1-tp3474.html
>
> Thanks!
>
> --Yakov
>

Re: Fwd: Coding Guidelines: zookeeper IP finder and mqtt streamer

[Anton Vinogradov]

Raul,

I've fixed most of TODOs you created.
Seems that indentation policy with multi-line parameter descriptions
already defined: "multiline comments in Javadoc tags should be indented by
4 or 5 characters ...".

Please check my changes:
https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=57901455=16=15



On Tue, Sep 29, 2015 at 3:28 PM, Roman Shaposhnik 
wrote:

> On Tue, Sep 29, 2015 at 3:01 PM, Raul Kripalani  wrote:
> > Thanks, Cos. I'm glad we sorted this out. Sometimes a chat would be
> useful
> > to establish rapport.
> >
> > Accusing someone of negligence is *extremely* serious and casts a very
> bad
> > image on the person being attributed with it.
>
> I've been there and I understand where you're coming from. Different words
> have different level of gravity in different languages and cultures.
>
> FWIW: I didn't read it as invoking catastrophic ramifications and/or
> doubting
> integrity of the person. But that's *my* reading. Somebody who, at the end
> of
> the day, speaks English fluently but alas as a second language. I do
> apologize
> if it made if you feel uncomfortable.
>
> I think the key takeaway for all of us who chimed in on this thread is
> to be extremely
> appreciative of the fact that we all come from different backgrounds
> and cultures
> and can interpret things differently. Lets give each other a bit of a
> breathing
> room and a benefit of the doubt.
>
> Thanks,
> Roman.
>

'Implement IgniteSemaphore data structure' Review

[Anton Vinogradov]

Val,

Vladisav prepared pull request related to Implement IgniteSemaphore data
structure .
Pull request seems to be ready for review.

Could you please review it?
PR url: https://github.com/apache/ignite/pull/120

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

[Anton Vinogradov]

I'll fix found bugs.
https://issues.apache.org/jira/browse/IGNITE-1557
https://issues.apache.org/jira/browse/IGNITE-1558

On Mon, Sep 28, 2015 at 4:30 AM, Dmitriy Setrakyan 
wrote:

> 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 name
> > for GridRouterCommandLineStartup.
> >
> > Also occurred with 1.3.0-incubating. No reason to block the release, but
> it
> > would be nice to include a note in the release notes under a "known
> issues"
> > section, or something.
> >
> > +1 (binding).
> >
> > *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 Fri, Sep 25, 2015 at 1:37 PM, Yakov Zhdanov 
> > wrote:
> >
> > > 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
> > >
> >
>

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

[Anton Vinogradov]

Raul, thanks!

Closed my issue as duplicate.

On Mon, Sep 28, 2015 at 11:44 AM, Raul Kripalani <r...@evosent.com> wrote:

> Hey Anton,
>
> I had already fixed the igniterouter scripts:
> https://issues.apache.org/jira/browse/IGNITE-1554
>
> On both 1.4 and master.
>
> Regards,
> Raúl.
> On 28 Sep 2015 08:48, "Anton Vinogradov" <avinogra...@gridgain.com> wrote:
>
> > I'll fix found bugs.
> > https://issues.apache.org/jira/browse/IGNITE-1557
> > https://issues.apache.org/jira/browse/IGNITE-1558
> >
> > On Mon, Sep 28, 2015 at 4:30 AM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > wrote:
> >
> > > Thanks Raul,
> > >
> > > Any chance you can file a ticket describing this issue?
> > >
> > > D.
> > >
> > > On Sat, Sep 26, 2015 at 3:16 AM, Raul Kripalani <ra...@apache.org>
> > 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
> > name
> > > > for GridRouterCommandLineStartup.
> > > >
> > > > Also occurred with 1.3.0-incubating. No reason to block the release,
> > but
> > > it
> > > > would be nice to include a note in the release notes under a "known
> > > issues"
> > > > section, or something.
> > > >
> > > > +1 (binding).
> > > >
> > > > *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 Fri, Sep 25, 2015 at 1:37 PM, Yakov Zhdanov <yzhda...@apache.org>
> > > > wrote:
> > > >
> > > > > 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
> > > > >
> > > >
> > >
> >
>

Re: After setting streamer and ignite,getting NULL

[Anton Vinogradov]

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 <gargv...@gmail.com>
> > 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: Pull Request Merge Process

[Anton Vinogradov]

Hello,
I've made initial review.
Comments was added to issue, please have a look.

On Tue, Sep 22, 2015 at 10:15 AM, Lalit Kumar Jha 
wrote:

> I submitted pull request for IGNITE-530 (Twitter streamer).
>
> What is the proceess for reviewing and merging?
>

Re: ignite-schema-import

[Anton Vinogradov]

Dmitriy,

Thats not a git issue, it's an IDEA warning. I have no such warning.
Seems you have broken *.iml files or you are swithing betwen branches where
some branches have schema-import module, but some not.

Better way to fix broken files is to remove everything and checkout
repository again. (Removing of .idea folder and all .iml files should give
save effect). Don't forget to close IDEA before removing.

On Fri, Sep 25, 2015 at 11:30 AM, Alexey Kuznetsov 
wrote:

> Dmitry,
>
> 1) Could you take a screenshot of Idea Maven tool window with expanded
> "profiles" and share with us via dropbox or smth. similar (apache dev list
> does not allow attachments)?
>
> 2) Try to do in Idea: Main menu -> Files -> Invalidate Caches / restart ->
> Invalidate and restart and after Idea restarted and source code indexing
> finished -> Click "reimport" on Maven toolbox.
> This often helped to resolve issues like this.
>
>
> On Fri, Sep 25, 2015 at 3:18 PM, Dmitriy Setrakyan 
> wrote:
>
> > Alexey,
> >
> > I have enabled schema-import profile, but know the whole project shows as
> > RED in the Maven take in IDEA. All modules have problem with
> > "com.sun.tools:1.4.2" dependency.
> >
> > Any idea?
> >
> > D.
> >
> > On Wed, Sep 16, 2015 at 11:22 PM, Alexey Kuznetsov <
> > akuznet...@gridgain.com>
> > wrote:
> >
> > > Seems that you unchecked "schema-import" profile in Maven projects /
> > > Profile tree?
> > >
> > > On Thu, Sep 17, 2015 at 10:44 AM, Dmitriy Setrakyan <
> > dsetrak...@apache.org
> > > >
> > > wrote:
> > >
> > > > Igniters,
> > > >
> > > > Is there a reason every time I update from GIT I get the following
> > popup
> > > in
> > > > IDEA:
> > > >
> > > > "This modules have been removed from Maven structure:
> > > > "ignite-schema-import"?
> > > >
> > > > D.
> > > >
> > >
> > >
> > >
> > > --
> > > Alexey Kuznetsov
> > > GridGain Systems
> > > www.gridgain.com
> > >
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>

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

[Anton Vinogradov]

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

Re: 'How to Contribute' wiki page updated.

[Anton Vinogradov]

Dmitriy,

I've fixed page according to your request except:

>- "Release Process" section should be a numbered list describing steps
>(including QA branch) necessary to create a release.

As far as I understans there is no QA's at Ignite community. GridGain QAs
can provide some help, but it's not a part of Ignite release process.
Another steps Prepare->Vote->Release are declared at Apache site and they
are the same for all projects.

   - I would add Continuous Integration section with URL to TeamCity. It
>should also state that merges to master should only happen after the
> whole
>TC suite passes.

Each case at workflow ends with phrase similar to:
"Run TC tests.Once tests are passed, the pull request can be reviewed and
merged by a committer."
Is it enough?

On Tue, Oct 6, 2015 at 8:10 AM, Dmitriy Setrakyan <dsetrak...@apache.org>
wrote:

> Thanks, Anton!
>
> I think the whole process looks too big right now. Perhaps we can make the
> following changes:
>
>- Remove "Development Process" section (not sure if it applies to us).
>- Remove "Git Workflow" section as it is described already in "Workflow"
>section.
>- Remove "Git Branches" section
>- "Release Process" section should be a numbered list describing steps
>(including QA branch) necessary to create a release.
>- For the ticket branch section, I don't think it is clear how to submit
>a branch for review or how to apply changes on master. Would be nice if
> you
>could clarify.
>- I would add Continuous Integration section with URL to TeamCity. It
>should also state that merges to master should only happen after the
> whole
>TC suite passes.
>
> Raul, it would be nice if you could also take a look and provide comments.
>
> Thanks,
> D.
>
> On Mon, Oct 5, 2015 at 7:36 AM, Anton Vinogradov <a...@apache.org> wrote:
>
> > Igniters,
> >
> > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> page
> > updated.
> >
> > Changes:
> > 1) Jira process and Git process becomes part of How to Contribute
> > <https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute>.
> > 2) Added 'Ticket Branch' case (only for committers).
> > 3) Fixed minor issues.
> >
> > It will be nice if someone check correctness.
> >
>

Re: Update version for branch ignite-1.5

[Anton Vinogradov]

+1

On Mon, Dec 7, 2015 at 6:03 PM, Sergey Kozlov  wrote:

> Hi
>
> Now we released Apache Ignite 1.5.0-b1 and version in branch ignite-1.5
> should changed to 1.5.0-b2
>
> Thoughts?
>
> --
> Sergey Kozlov
>

Re: Build Failure on master branch

[Anton Vinogradov]

Is it possible to remove folder D:\sandbox\ignite\modules\gce\target\apidocs
?
Also there is should no be any target folder in case it's a clean branch.
Please check this point.

On Thu, Dec 3, 2015 at 3:22 PM, Ken Cheng <kcheng@gmail.com> wrote:

> Still run into the same issue. As it's a clean branch.
> but this issue only happens in Windows
>
> On Thursday, December 3, 2015, Anton Vinogradov <avinogra...@gridgain.com>
> wrote:
> > Ken,
> >
> > I can't understand, did my tip helped?
> >
> > On Thu, Dec 3, 2015 at 3:11 PM, Ken Cheng <kcheng@gmail.com> wrote:
> >
> >> HI Anton,
> >>
> >> it's wired, as I did not nothing just try to build the the jar.
> >>
> >> Thanks,
> >> kcheng
> >>
> >> On Thu, Dec 3, 2015 at 8:08 PM, Anton Vinogradov <
> avinogra...@gridgain.com
> >> >
> >> wrote:
> >>
> >> > Ken,
> >> >
> >> > Seems some other application used files at
> >> > D:\sandbox\ignite\modules\gce\target\apidocs.
> >> > Possible it's an Explorer.
> >> >
> >> > On Thu, Dec 3, 2015 at 3:04 PM, Ken Cheng <kcheng@gmail.com>
> wrote:
> >> >
> >> > > Hi All,
> >> > >
> >> > > Here is my environment details:
> >> > >
> >> > > OS : Windows 64
> >> > > jdk 1.7
> >> > >
> >> > > here is error message
> >> > >
> >> > >
> >> > > 
> >> > > [INFO] ignite-apache-license-gen .. SUCCESS
> [
> >> > > 3.689 s]
> >> > > [INFO] ignite-tools ... SUCCESS
> [
> >> > > 23.021 s]
> >> > > [INFO] ignite-core  SUCCESS
> >> > [02:36
> >> > > min]
> >> > > [INFO] ignite-log4j ... SUCCESS
> [
> >> > > 34.038 s]
> >> > > [INFO] ignite-urideploy ... SUCCESS
> [
> >> > > 15.394 s]
> >> > > [INFO] ignite-spring .. SUCCESS
> [
> >> > > 11.462 s]
> >> > > [INFO] ignite-hadoop .. SUCCESS
> [
> >> > > 37.277 s]
> >> > > [INFO] ignite-extdata-p2p . SUCCESS
> [
> >> > > 6.321 s]
> >> > > [INFO] ignite-extdata-uri-dep . SUCCESS
> [
> >> > > 8.013 s]
> >> > > [INFO] ignite-extdata-uri . SUCCESS
> [
> >> > > 2.241 s]
> >> > > [INFO] ignite-indexing  SUCCESS
> [
> >> > > 23.103 s]
> >> > > [INFO] ignite-rest-http ... SUCCESS
> [
> >> > > 11.376 s]
> >> > > [INFO] ignite-clients . SUCCESS
> [
> >> > > 5.518 s]
> >> > > [INFO] ignite-web . SUCCESS
> [
> >> > > 7.509 s]
> >> > > [INFO] ignite-aop . SUCCESS
> [
> >> > > 6.985 s]
> >> > > [INFO] ignite-ssh . SUCCESS
> [
> >> > > 4.100 s]
> >> > > [INFO] ignite-jta . SUCCESS
> [
> >> > > 5.105 s]
> >> > > [INFO] ignite-aws . SUCCESS
> [
> >> > > 8.850 s]
> >> > > [INFO] ignite-log4j2 .. SUCCESS
> [
> >> > > 3.847 s]
> >> > > [INFO] ignite-slf4j ... SUCCESS
> [
> >> > > 5.768 s]
> >> > > [INFO] ignite-jcl . SUCCESS
> [
> >> > > 25.840 s]
> >> > > [INFO] ignite-codegen . SUCCESS
> [
> >> > > 3.010 s]
> >> > > [INFO] ignite-gce . FAILURE
> [
> >> > > 2.146 s]
> >> > > [INFO] ignite-cloud ... SKIPPED
> >> > > [INFO] ignite-mesos 

Re: Build Failure on master branch

[Anton Vinogradov]

Ken,

Seems some other application used files at
D:\sandbox\ignite\modules\gce\target\apidocs.
Possible it's an Explorer.

On Thu, Dec 3, 2015 at 3:04 PM, Ken Cheng  wrote:

> Hi All,
>
> Here is my environment details:
>
> OS : Windows 64
> jdk 1.7
>
> here is error message
>
>
> 
> [INFO] ignite-apache-license-gen .. SUCCESS [
> 3.689 s]
> [INFO] ignite-tools ... SUCCESS [
> 23.021 s]
> [INFO] ignite-core  SUCCESS [02:36
> min]
> [INFO] ignite-log4j ... SUCCESS [
> 34.038 s]
> [INFO] ignite-urideploy ... SUCCESS [
> 15.394 s]
> [INFO] ignite-spring .. SUCCESS [
> 11.462 s]
> [INFO] ignite-hadoop .. SUCCESS [
> 37.277 s]
> [INFO] ignite-extdata-p2p . SUCCESS [
> 6.321 s]
> [INFO] ignite-extdata-uri-dep . SUCCESS [
> 8.013 s]
> [INFO] ignite-extdata-uri . SUCCESS [
> 2.241 s]
> [INFO] ignite-indexing  SUCCESS [
> 23.103 s]
> [INFO] ignite-rest-http ... SUCCESS [
> 11.376 s]
> [INFO] ignite-clients . SUCCESS [
> 5.518 s]
> [INFO] ignite-web . SUCCESS [
> 7.509 s]
> [INFO] ignite-aop . SUCCESS [
> 6.985 s]
> [INFO] ignite-ssh . SUCCESS [
> 4.100 s]
> [INFO] ignite-jta . SUCCESS [
> 5.105 s]
> [INFO] ignite-aws . SUCCESS [
> 8.850 s]
> [INFO] ignite-log4j2 .. SUCCESS [
> 3.847 s]
> [INFO] ignite-slf4j ... SUCCESS [
> 5.768 s]
> [INFO] ignite-jcl . SUCCESS [
> 25.840 s]
> [INFO] ignite-codegen . SUCCESS [
> 3.010 s]
> [INFO] ignite-gce . FAILURE [
> 2.146 s]
> [INFO] ignite-cloud ... SKIPPED
> [INFO] ignite-mesos ... SKIPPED
> [INFO] ignite-kafka ... SKIPPED
> [INFO] ignite-flume ... SKIPPED
> [INFO] ignite-yarn  SKIPPED
> [INFO] ignite-jms11 ... SKIPPED
> [INFO] ignite-twitter . SKIPPED
> [INFO] ignite-mqtt  SKIPPED
> [INFO] ignite-zookeeper ... SKIPPED
> [INFO] ignite-camel ... SKIPPED
> [INFO] ignite-scalar .. SKIPPED
> [INFO] ignite-spark ... SKIPPED
> [INFO] ignite-visor-console ... SKIPPED
> [INFO] ignite-visor-plugins ... SKIPPED
> [INFO] ignite-schema-import ... SKIPPED
> [INFO] apache-ignite .. SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 06:52 min
> [INFO] Finished at: 2015-12-03T20:01:05+08:00
> [INFO] Final Memory: 118M/605M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-clean-plugin:2.5:clean (default-clean) on
> project ignite-gce: Failed to clean project: Failed to delete
> D:\sandbox\ignite\modules\gce\target\apidocs -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :ignite-gce
>
>
> ---
>
> Thanks,
> kcheng
>

Re: GridCacheIoManager.processFailedMessage() method

[Anton Vinogradov]

https://issues.apache.org/jira/browse/IGNITE-2079

On Thu, Dec 3, 2015 at 11:26 AM, Yakov Zhdanov  wrote:

> This method was introduced exactly to prevent cluster from hanging in case
> of unexpected problems during message processing. The thing is that the one
> who has added new message has not added corresponding block to mentioned
> method.
>
> Agree with the point about original error message should not be suppressed
> in any case.
>
> Anton V, can you please file a ticket and fix the comments?
>
> --Yakov
>

Re: Build Failure on master branch

[Anton Vinogradov]

Ken,

I can't understand, did my tip helped?

On Thu, Dec 3, 2015 at 3:11 PM, Ken Cheng <kcheng@gmail.com> wrote:

> HI Anton,
>
> it's wired, as I did not nothing just try to build the the jar.
>
> Thanks,
> kcheng
>
> On Thu, Dec 3, 2015 at 8:08 PM, Anton Vinogradov <avinogra...@gridgain.com
> >
> wrote:
>
> > Ken,
> >
> > Seems some other application used files at
> > D:\sandbox\ignite\modules\gce\target\apidocs.
> > Possible it's an Explorer.
> >
> > On Thu, Dec 3, 2015 at 3:04 PM, Ken Cheng <kcheng@gmail.com> wrote:
> >
> > > Hi All,
> > >
> > > Here is my environment details:
> > >
> > > OS : Windows 64
> > > jdk 1.7
> > >
> > > here is error message
> > >
> > >
> > > 
> > > [INFO] ignite-apache-license-gen .. SUCCESS [
> > > 3.689 s]
> > > [INFO] ignite-tools ... SUCCESS [
> > > 23.021 s]
> > > [INFO] ignite-core  SUCCESS
> > [02:36
> > > min]
> > > [INFO] ignite-log4j ... SUCCESS [
> > > 34.038 s]
> > > [INFO] ignite-urideploy ... SUCCESS [
> > > 15.394 s]
> > > [INFO] ignite-spring .. SUCCESS [
> > > 11.462 s]
> > > [INFO] ignite-hadoop .. SUCCESS [
> > > 37.277 s]
> > > [INFO] ignite-extdata-p2p . SUCCESS [
> > > 6.321 s]
> > > [INFO] ignite-extdata-uri-dep . SUCCESS [
> > > 8.013 s]
> > > [INFO] ignite-extdata-uri . SUCCESS [
> > > 2.241 s]
> > > [INFO] ignite-indexing  SUCCESS [
> > > 23.103 s]
> > > [INFO] ignite-rest-http ... SUCCESS [
> > > 11.376 s]
> > > [INFO] ignite-clients . SUCCESS [
> > > 5.518 s]
> > > [INFO] ignite-web . SUCCESS [
> > > 7.509 s]
> > > [INFO] ignite-aop . SUCCESS [
> > > 6.985 s]
> > > [INFO] ignite-ssh . SUCCESS [
> > > 4.100 s]
> > > [INFO] ignite-jta . SUCCESS [
> > > 5.105 s]
> > > [INFO] ignite-aws . SUCCESS [
> > > 8.850 s]
> > > [INFO] ignite-log4j2 .. SUCCESS [
> > > 3.847 s]
> > > [INFO] ignite-slf4j ... SUCCESS [
> > > 5.768 s]
> > > [INFO] ignite-jcl . SUCCESS [
> > > 25.840 s]
> > > [INFO] ignite-codegen . SUCCESS [
> > > 3.010 s]
> > > [INFO] ignite-gce . FAILURE [
> > > 2.146 s]
> > > [INFO] ignite-cloud ... SKIPPED
> > > [INFO] ignite-mesos ... SKIPPED
> > > [INFO] ignite-kafka ... SKIPPED
> > > [INFO] ignite-flume ... SKIPPED
> > > [INFO] ignite-yarn  SKIPPED
> > > [INFO] ignite-jms11 ... SKIPPED
> > > [INFO] ignite-twitter . SKIPPED
> > > [INFO] ignite-mqtt  SKIPPED
> > > [INFO] ignite-zookeeper ... SKIPPED
> > > [INFO] ignite-camel ... SKIPPED
> > > [INFO] ignite-scalar .. SKIPPED
> > > [INFO] ignite-spark ... SKIPPED
> > > [INFO] ignite-visor-console ... SKIPPED
> > > [INFO] ignite-visor-plugins ... SKIPPED
> > > [INFO] ignite-schema-import ... SKIPPED
> > > [INFO] apache-ignite .. SKIPPED
> > > [INFO]
> > >
> 
> > > [INFO] BUILD FAILURE
> > > [INFO]
> > >
> 

Ignite Teamcity update

[Anton Vinogradov]

Igniters,

Ingite tests at Teamcity migrated from 'Ignite' project to "Ignite Tests"
project.
Old project (Ignite) paused now and will be removed next week.

Please use "Ignite Tests" project only.

Re: Weird releases [Was: EA versioning]

[Anton Vinogradov]

It's a test release.
I have no clue why it's located at archive dist.
It should be removed.

Does anybody know how to remove it?

On Mon, Dec 7, 2015 at 7:18 AM, Konstantin Boudnik  wrote:

> Forking of the release schema conversation. I have noticed that official
> dist
> http://archive.apache.org/dist//ignite/
>
> has 2.2.2-test version. Anyone knows why it is there?
>
> Cos
>
>

Re: [VOTE] Apache Ignite 1.5.0-b1

[Anton Vinogradov]

+1

On Wed, Dec 2, 2015 at 3:16 PM, Yakov Zhdanov  wrote:

> Dear Sirs!
>
> We have uploaded release candidate to
> https://dist.apache.org/repos/dist/dev/ignite/1.5.0-b1-rc1/
>
> This is very important release containing initial versions of Ignite.NET
> and Ignite C++ and many other important features.
> We want community to test this Early Access version in order to gather
> feedback and move on to releasing final version.
>
> Tag name is
> ignite-1.5.0-b1-rc1
>
> 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 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.
>
> 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/ignite-1.5.0-b1-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.5.0-b1-rc1
>
> Please start voting.
>
> +1 - to accept Apache Ignite 1.5.0-b1
> 0 - don't care either way
> -1 - DO NOT accept Apache Ignite 1.5.0-b1 (explain why)
>
> This vote will go for 72 hours.
>
> --Yakov
>

Re: 1.5 GA

[Anton Vinogradov]

Raul,

Tag 1.5.0-b1 fixed, please check.

On Mon, Dec 14, 2015 at 3:59 PM, Raul Kripalani  wrote:

> On Mon, Dec 14, 2015 at 10:36 AM, Yakov Zhdanov 
> wrote:
>
> > osgi has been pushed to 1.5 after b1 has been built. You can build ignite
> > binaries from ignite-1.5 branch to test the functionality.
> >
>
> Then the 1.5.0-b1 tag is incorrect. It points
> to 9a14d6432932fc1a1fdf2ddd77dea920382efe8c which would have included OSGi.
>
> Could you please fix the tag to point to the commit you actually built the
> release from?
>
> 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: 1.5 GA

[Anton Vinogradov]

Cos,

I'm affraid that we already too close to release that we have no chances
for one more delay.
Also we should research how to fix this issue in correct way.
Possible we have to replace "-" with "." and gain 1.x.0.b1 & 1.x.0.final as
a result, but I'm not sure it will not break compatibility with some other
case.

Raul & Sergi,

Could you please check that usage of "." instead of "-" is a good case?

On Fri, Dec 18, 2015 at 10:19 AM, Anton Vinogradov <avinogra...@gridgain.com
> wrote:

> Yakov,
>
> ignite-1.5.0-b1-rc1
> <https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=f51c051d1e588855c37774efb22cd3536f512aa3>
>  was
> correct.
> 1.5.0-b1
> <https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=f51c051d1e588855c37774efb22cd3536f512aa3>
>  -
> now correct too, was fixed.
> Both (now) points to the same commit.
>
> On Fri, Dec 18, 2015 at 7:40 AM, Yakov Zhdanov <yzhda...@apache.org>
> wrote:
>
>> Cos, rc tag was fine. Problem was with release one. Anton V. is that
>> correct?
>>
>> Yakov
>> On Dec 18, 2015 10:32, "Konstantin Boudnik" <c...@apache.org> wrote:
>>
>> > Was VOTE done against the tag pointed to the incorrect commit?
>> >
>> > Cos
>> >
>> > On Mon, Dec 14, 2015 at 12:59PM, Raul Kripalani wrote:
>> > > On Mon, Dec 14, 2015 at 10:36 AM, Yakov Zhdanov <yzhda...@apache.org>
>> > wrote:
>> > >
>> > > > osgi has been pushed to 1.5 after b1 has been built. You can build
>> > ignite
>> > > > binaries from ignite-1.5 branch to test the functionality.
>> > > >
>> > >
>> > > Then the 1.5.0-b1 tag is incorrect. It points
>> > > to 9a14d6432932fc1a1fdf2ddd77dea920382efe8c which would have included
>> > OSGi.
>> > >
>> > > Could you please fix the tag to point to the commit you actually built
>> > the
>> > > release from?
>> > >
>> > > 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: 1.5 GA

[Anton Vinogradov]

Yakov,

ignite-1.5.0-b1-rc1

was
correct.
1.5.0-b1

-
now correct too, was fixed.
Both (now) points to the same commit.

On Fri, Dec 18, 2015 at 7:40 AM, Yakov Zhdanov  wrote:

> Cos, rc tag was fine. Problem was with release one. Anton V. is that
> correct?
>
> Yakov
> On Dec 18, 2015 10:32, "Konstantin Boudnik"  wrote:
>
> > Was VOTE done against the tag pointed to the incorrect commit?
> >
> > Cos
> >
> > On Mon, Dec 14, 2015 at 12:59PM, Raul Kripalani wrote:
> > > On Mon, Dec 14, 2015 at 10:36 AM, Yakov Zhdanov 
> > wrote:
> > >
> > > > osgi has been pushed to 1.5 after b1 has been built. You can build
> > ignite
> > > > binaries from ignite-1.5 branch to test the functionality.
> > > >
> > >
> > > Then the 1.5.0-b1 tag is incorrect. It points
> > > to 9a14d6432932fc1a1fdf2ddd77dea920382efe8c which would have included
> > OSGi.
> > >
> > > Could you please fix the tag to point to the commit you actually built
> > the
> > > release from?
> > >
> > > 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
> >
>

[RESULT] [VOTE] Apache Ignite 1.5.0.final Release (RC3)

[Anton Vinogradov]

Hello!

Apache Ignite 1.5.0.final release (RC3) has been accepted.

13 "+1" votes received.

Here are the votes received:

   - Anton Vinogradov (binding)
   - Nikolay Tikhonov (binding)
   - Konstantin Boudnik (binding)
   - Semyon Boikov (binding)
   - Gianfranco Murador (binding)
   - Vladimir Ozerov (binding)
   - Alexey Goncharuk (binding)
   - Raul Kripalani (binding)
   - Denis Magda (binding)
   - Sergi Vladykin (binding)
   - 姜 为
   - Alexey Kuznetsov
   - Roman Shtykh

Here is the link to vote thread -
http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-1-5-0-final-RC3-td6305.html

Ignite 1.5.0.final successfuly released to
https://dist.apache.org/repos/dist/release/ignite/1.5.0.final/

Site & Maven will be updated soon.

Thanks!

Re: [RESULT] [VOTE] Apache Ignite 1.5.0.final Release (RC3)

[Anton Vinogradov]

Dmitriy,

Please download and extract
https://dist.apache.org/repos/dist/release/ignite/1.5.0.final/apache-ignite-fabric-1.5.0.final-bin.zip
and from it's folder make
svn import docs
https://svn.apache.org/repos/asf/ignite/site/trunk/releases/1.5.0.final -m
"new Release (1.5.0.final)"

This step described at
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process

On Mon, Jan 4, 2016 at 9:42 PM, Dmitriy Setrakyan <dsetrak...@apache.org>
wrote:

> Anton,
>
> I have published the release on the website. However, it looks like we are
> missing the Javadoc and Scaladoc for 1.5.0.final version. What is the
> procedure for adding it?
>
> D.
>
> On Mon, Jan 4, 2016 at 2:12 AM, Anton Vinogradov <a...@apache.org> wrote:
>
> > Hello!
> >
> > Apache Ignite 1.5.0.final release (RC3) has been accepted.
> >
> > 13 "+1" votes received.
> >
> > Here are the votes received:
> >
> >- Anton Vinogradov (binding)
> >- Nikolay Tikhonov (binding)
> >- Konstantin Boudnik (binding)
> >- Semyon Boikov (binding)
> >- Gianfranco Murador (binding)
> >- Vladimir Ozerov (binding)
> >- Alexey Goncharuk (binding)
> >- Raul Kripalani (binding)
> >- Denis Magda (binding)
> >- Sergi Vladykin (binding)
> >- 姜 为
> >- Alexey Kuznetsov
> >- Roman Shtykh
> >
> > Here is the link to vote thread -
> >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-1-5-0-final-RC3-td6305.html
> >
> > Ignite 1.5.0.final successfuly released to
> > https://dist.apache.org/repos/dist/release/ignite/1.5.0.final/
> >
> > Site & Maven will be updated soon.
> >
> > Thanks!
> >
>

Re: 1.5.final

[Anton Vinogradov]

The fix for https://issues.apache.org/jira/browse/IGNITE-2175 has been
merged to ignite-1.5​

On Wed, Dec 23, 2015 at 4:30 PM, Alexey Kuznetsov 
wrote:

> I think "IGNITE-2252 Add support for cache sql schema in REST topology
> command" will be fixed tomorrow in first half of a day.
>
> On Wed, Dec 23, 2015 at 7:14 PM, Sergey Kozlov 
> wrote:
>
> > Hi Igniters
> > We've great progress and only two outstanding issues prevents to release:
> > IGNITE-2252 Add support for cache sql schema in REST topology command
> > 
> > IGNITE-2175 Not valid exceptions in case when example can't works with
> > remote node started with server classpath (Java 7)
> > 
> >
> >
> >
> > On Wed, Dec 23, 2015 at 3:10 PM, Alexey Goncharuk <
> > alexey.goncha...@gmail.com> wrote:
> >
> > > The fix for https://issues.apache.org/jira/browse/IGNITE-2200 has been
> > > merged to ignite-1.5​
> > >
> >
> >
> >
> > --
> > Sergey Kozlov
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>

Re: [VOTE] Apache Ignite 1.5.0.final

[Anton Vinogradov]

+1 (binding)

On Fri, Dec 25, 2015 at 4:19 PM, Nikolay Tikhonov <ntikho...@gridgain.com>
wrote:

> +1 (binding)
>
> On Fri, Dec 25, 2015 at 4:00 PM, Anton Vinogradov <a...@apache.org> wrote:
>
> > Dear Sirs!
> >
> > We have uploaded release candidate to
> > https://dist.apache.org/repos/dist/dev/ignite/1.5.0.final-rc1/
> >
> > 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-rc1
> >
> > 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-rc1
> >
> > 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-rc1
> >
> > Please start voting.
> >
> > +1 - to accept Apache Ignite 1.5.0.final
> > 0 - don't care either way
> > -1 - DO NOT accept Apache Ignite 1.5.0.final (explain why)
> >
> > This vote will go for 72 hours.
> >
>

Re: [VOTE] Apache Ignite 1.5.0.final

[Anton Vinogradov]

Hi,

1-2)
Seems that we have to have dotnet build folder located at "regular" java
target folder which will be automatically excluded at source package build.
Another way is to configure "source-release-assembly" at "apache-release"
profile somehow.
And last one case is to build source package at separate step (without
using dotnet assemblies)

1 & 2 way is preffered.

Thoughts?

3) We have tip about this issue at
https://apacheignite.readme.io/docs/getting-started, but I agree with
Vladimir.

Cos, in case we will fix sourcess manually (for issue 1-2) and regenerate
md5 & sha will you change your decision?

On Sat, Dec 26, 2015 at 2:29 PM, Sergey Kozlov <skoz...@gridgain.com> wrote:

> Hi
>
> I analyzed the build log for Apache Ignite 1.5.0.final-rc1 and found that
> we make a source archive after building of fabric edition. It seems it
> caused the issue raised by Cos.
> I propose to move the step of source archiving  before any build steps and
> may be run RAT against source zip file.
>
>
>
> On Sat, Dec 26, 2015 at 11:12 AM, Vladimir Ozerov <voze...@gridgain.com>
> wrote:
>
>> Cos,
>>
>> p.1 and p.2 appear to be the same - folder "modules/platforms/dotnet/bin"
>> should not exist in source release, only in binary build.
>> p.3 - looks like we need make .NET and CPP docs creation step off by
>> default and enable it only if particular flag is set. For now behavior is
>> the opposite - docs are generated by default unless "!isClientDocs" flag
>> is
>> set.
>>
>>
>> On Sat, Dec 26, 2015 at 10:46 AM, Konstantin Boudnik <c...@apache.org>
>> wrote:
>>
>> > Looks like a -1 [binding] is order
>> >
>> > 1) RAT check fails on
>> > modules/platforms/dotnet/bin/Apache.Ignite.Core.xml
>> > 2) release archive includes binary files under
>> > /modules/platforms/dotnet/bin
>> > /modules/platforms/dotnet/bin/x86/
>> > 3) build fails with
>> > [ERROR] Failed to execute goal
>> > org.apache.maven.plugins:maven-antrun-plugin:1.7:run (dotnetdoc) on
>> project
>> > ignite-clients: An Ant BuildException has occured: Execute failed:
>> > java.io.IOException: Cannot run program "doxygen" (in directory
>> >
>> >
>> "/ws/build/ignite-hadoop/rpm/BUILD/ignite-hadoop-1.5.0.final/modules/platforms/dotnet"):
>> > error=2, No such file or directory
>> >
>> > Cheers,
>> >   Cos
>> >
>> > On Fri, Dec 25, 2015 at 04:00PM, Anton Vinogradov wrote:
>> > > Dear Sirs!
>> > >
>> > > We have uploaded release candidate to
>> > > https://dist.apache.org/repos/dist/dev/ignite/1.5.0.final-rc1/
>> > >
>> > > 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-rc1
>> > >
>> > > 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-rc1
>> > >
>> > > 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-rc1
>> > >
>> > > Please start voting.
>> > >
>> > > +1 - to accept Apache Ignite 1.5.0.final
>> > > 0 - don't care either way
>> > > -1 - DO NOT accept Apache Ignite 1.5.0.final (explain why)
>> > >
>> > > This vote will go for 72 hours.
>> >
>>
>
>
>
> --
> Sergey Kozlov
>
>

[CLOSE] [VOTE] Apache Ignite 1.5.0.final

[Anton Vinogradov]

Vote has to be closed due to found issues.

A new build will be resubmitted soon.

Re: 1.5 GA

[Anton Vinogradov]

Seems everything is ok,

https://versionatorr.appspot.com/?a=1.5.0.final=1.5.0-b1
https://versionatorr.appspot.com/?a=1.5.0.final=1.5.0-final

I'll update versions.

On Tue, Dec 22, 2015 at 12:28 PM, Anton Vinogradov <avinogra...@gridgain.com
> wrote:

> Dmitriy,
>
> that's not a big change, but we have to check it will not break something
> else.
> I'll check it today.
>
> Raul,
>
> Could you please check this solution is suitable for OSGi?
>
> On Tue, Dec 22, 2015 at 10:04 AM, Dmitriy Setrakyan <dsetrak...@apache.org
> > wrote:
>
>> I filed the ticket:
>> https://issues.apache.org/jira/browse/IGNITE-2226
>>
>> I think we should change dash to dot for now.
>>
>> Anton, can you explain why this is a big change?
>>
>> D.
>>
>> On Mon, Dec 21, 2015 at 10:28 PM, Konstantin Boudnik <c...@apache.org>
>> wrote:
>>
>> > Well, being too close to the release doesn't mean that we need to rush
>> and
>> > produce yet another one that will be causing troubles downstream.
>> >
>> > There's nothing to research really. Just dump the string suffixes in the
>> > versions and be happy. They are solving nothing, but create confusion
>> and
>> > incompatibilities.
>> >
>> > Cos
>> >
>> > On Fri, Dec 18, 2015 at 12:32PM, Anton Vinogradov wrote:
>> > > Cos,
>> > >
>> > > I'm affraid that we already too close to release that we have no
>> chances
>> > > for one more delay.
>> > > Also we should research how to fix this issue in correct way.
>> > > Possible we have to replace "-" with "." and gain 1.x.0.b1 &
>> 1.x.0.final
>> > as
>> > > a result, but I'm not sure it will not break compatibility with some
>> > other
>> > > case.
>> > >
>> > > Raul & Sergi,
>> > >
>> > > Could you please check that usage of "." instead of "-" is a good
>> case?
>> > >
>> > > On Fri, Dec 18, 2015 at 10:19 AM, Anton Vinogradov <
>> > avinogra...@gridgain.com
>> > > > wrote:
>> > >
>> > > > Yakov,
>> > > >
>> > > > ignite-1.5.0-b1-rc1
>> > > > <
>> >
>> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=f51c051d1e588855c37774efb22cd3536f512aa3
>> >
>> > was
>> > > > correct.
>> > > > 1.5.0-b1
>> > > > <
>> >
>> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=f51c051d1e588855c37774efb22cd3536f512aa3
>> >
>> > -
>> > > > now correct too, was fixed.
>> > > > Both (now) points to the same commit.
>> > > >
>> > > > On Fri, Dec 18, 2015 at 7:40 AM, Yakov Zhdanov <yzhda...@apache.org
>> >
>> > > > wrote:
>> > > >
>> > > >> Cos, rc tag was fine. Problem was with release one. Anton V. is
>> that
>> > > >> correct?
>> > > >>
>> > > >> Yakov
>> > > >> On Dec 18, 2015 10:32, "Konstantin Boudnik" <c...@apache.org>
>> wrote:
>> > > >>
>> > > >> > Was VOTE done against the tag pointed to the incorrect commit?
>> > > >> >
>> > > >> > Cos
>> > > >> >
>> > > >> > On Mon, Dec 14, 2015 at 12:59PM, Raul Kripalani wrote:
>> > > >> > > On Mon, Dec 14, 2015 at 10:36 AM, Yakov Zhdanov <
>> > yzhda...@apache.org>
>> > > >> > wrote:
>> > > >> > >
>> > > >> > > > osgi has been pushed to 1.5 after b1 has been built. You can
>> > build
>> > > >> > ignite
>> > > >> > > > binaries from ignite-1.5 branch to test the functionality.
>> > > >> > > >
>> > > >> > >
>> > > >> > > Then the 1.5.0-b1 tag is incorrect. It points
>> > > >> > > to 9a14d6432932fc1a1fdf2ddd77dea920382efe8c which would have
>> > included
>> > > >> > OSGi.
>> > > >> > >
>> > > >> > > Could you please fix the tag to point to the commit you
>> actually
>> > built
>> > > >> > the
>> > > >> > > release from?
>> > > >> > >
>> > > >> > > 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: 1.5 GA

[Anton Vinogradov]

Dmitriy,

that's not a big change, but we have to check it will not break something
else.
I'll check it today.

Raul,

Could you please check this solution is suitable for OSGi?

On Tue, Dec 22, 2015 at 10:04 AM, Dmitriy Setrakyan <dsetrak...@apache.org>
wrote:

> I filed the ticket:
> https://issues.apache.org/jira/browse/IGNITE-2226
>
> I think we should change dash to dot for now.
>
> Anton, can you explain why this is a big change?
>
> D.
>
> On Mon, Dec 21, 2015 at 10:28 PM, Konstantin Boudnik <c...@apache.org>
> wrote:
>
> > Well, being too close to the release doesn't mean that we need to rush
> and
> > produce yet another one that will be causing troubles downstream.
> >
> > There's nothing to research really. Just dump the string suffixes in the
> > versions and be happy. They are solving nothing, but create confusion and
> > incompatibilities.
> >
> > Cos
> >
> > On Fri, Dec 18, 2015 at 12:32PM, Anton Vinogradov wrote:
> > > Cos,
> > >
> > > I'm affraid that we already too close to release that we have no
> chances
> > > for one more delay.
> > > Also we should research how to fix this issue in correct way.
> > > Possible we have to replace "-" with "." and gain 1.x.0.b1 &
> 1.x.0.final
> > as
> > > a result, but I'm not sure it will not break compatibility with some
> > other
> > > case.
> > >
> > > Raul & Sergi,
> > >
> > > Could you please check that usage of "." instead of "-" is a good case?
> > >
> > > On Fri, Dec 18, 2015 at 10:19 AM, Anton Vinogradov <
> > avinogra...@gridgain.com
> > > > wrote:
> > >
> > > > Yakov,
> > > >
> > > > ignite-1.5.0-b1-rc1
> > > > <
> >
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=f51c051d1e588855c37774efb22cd3536f512aa3
> >
> > was
> > > > correct.
> > > > 1.5.0-b1
> > > > <
> >
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=f51c051d1e588855c37774efb22cd3536f512aa3
> >
> > -
> > > > now correct too, was fixed.
> > > > Both (now) points to the same commit.
> > > >
> > > > On Fri, Dec 18, 2015 at 7:40 AM, Yakov Zhdanov <yzhda...@apache.org>
> > > > wrote:
> > > >
> > > >> Cos, rc tag was fine. Problem was with release one. Anton V. is that
> > > >> correct?
> > > >>
> > > >> Yakov
> > > >> On Dec 18, 2015 10:32, "Konstantin Boudnik" <c...@apache.org> wrote:
> > > >>
> > > >> > Was VOTE done against the tag pointed to the incorrect commit?
> > > >> >
> > > >> > Cos
> > > >> >
> > > >> > On Mon, Dec 14, 2015 at 12:59PM, Raul Kripalani wrote:
> > > >> > > On Mon, Dec 14, 2015 at 10:36 AM, Yakov Zhdanov <
> > yzhda...@apache.org>
> > > >> > wrote:
> > > >> > >
> > > >> > > > osgi has been pushed to 1.5 after b1 has been built. You can
> > build
> > > >> > ignite
> > > >> > > > binaries from ignite-1.5 branch to test the functionality.
> > > >> > > >
> > > >> > >
> > > >> > > Then the 1.5.0-b1 tag is incorrect. It points
> > > >> > > to 9a14d6432932fc1a1fdf2ddd77dea920382efe8c which would have
> > included
> > > >> > OSGi.
> > > >> > >
> > > >> > > Could you please fix the tag to point to the commit you actually
> > built
> > > >> > the
> > > >> > > release from?
> > > >> > >
> > > >> > > 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: 1.5.final

[Anton Vinogradov]

My tickets:

IGNITE-2226 Replace dash in 1.5.0-final with dot 1.5.0.final

IGNITE-2175 Not valid exceptions in case when example can't works with
remote node started with server classpath (Java 7)

Both should be ready today.

IGNITE-2116 ignite-osgi-karaf has only readme and license files
Waiting for Raul's answer.

On Tue, Dec 22, 2015 at 10:45 AM, Dmitriy Setrakyan 
wrote:

> From maven standpoint, 1.5.0.final comes after 1.5.0-b1. Can someone double
> confirm this?
>
> D.
>
> On Mon, Dec 21, 2015 at 10:34 PM, Konstantin Boudnik 
> wrote:
>
> > 1.5.final is bigger that 1.5.0-b1? Or lesser?
> >
> > On Mon, Dec 21, 2015 at 08:33AM, Dmitriy Setrakyan wrote:
> > > I would like to assemble a list of the remaining issues for the 1.5
> final
> > > release. Can everyone in the community please reply here with a list of
> > > tickets you are still working on for 1.5 release?
> > >
> > > Thanks,
> > > D.
> >
>

Re: 1.5.final

[Anton Vinogradov]

I closed one,
Left:  IGNITE-2175 Not valid exceptions in case when example can't works
with remote node started with server classpath (Java 7)

On Wed, Dec 23, 2015 at 9:22 AM, Vladimir Ozerov 
wrote:

> I closed my ticket. There was a problem in test preventing compilation with
> Java 8.
>
> On Wed, Dec 23, 2015 at 4:54 AM, Dmitriy Setrakyan 
> wrote:
>
> > As of today, there are still 4 tickets open:
> > http://s.apache.org/ignite-1.5.0.final
> >
> > Anton - 2 tickets
> > Vladimir - 1 ticket
> > Alexey - 1 ticket
> >
> > D.
> >
> >
> > On Tue, Dec 22, 2015 at 5:50 AM, Alexey Goncharuk <
> > alexey.goncha...@gmail.com> wrote:
> >
> > > Looks like it is a duplicate of IGNITE-2135.
> > > The issue is caused by not setting deployment info bean in query
> request
> > > when binary marshaller is used.
> > >
> > > I anticipate the fix to be pretty simple, though need some more time to
> > add
> > > a proper test and to run CI. Will send an update once all is done.
> > >
> >
>

Ignite Voting Process

[Anton Vinogradov]

Igniters,

We've published Ignite Voting Process, please have a look before sending +1
to vote ;)

https://cwiki.apache.org/confluence/display/IGNITE/Voting+Process

Re: [VOTE] Apache Ignite 1.5.0.final RC3

[Anton Vinogradov]

+1 (binding)

On Tue, Dec 29, 2015 at 4:17 PM, 姜 为 <ydswcy...@gmail.com> wrote:

> +1 nice job!
>
> > 在 2015年12月29日，下午6:54，Anton Vinogradov <a...@apache.org> 写道：
> >
> > 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.
>
>

Re: Providing an example as part of contribution

[Anton Vinogradov]

This should be at least discussable for each new feature/functionalitiy.
It would be nice to see OSGi example at this release. It's still riddle for
me what our OSGi modules do.

On Tue, Dec 29, 2015 at 4:41 PM, Yakov Zhdanov  wrote:

> I suggest no rules here. Let's take the decision on whether to add example
> or not relying on what functionality is being added.
>
> --Yakov
>
> 2015-12-29 16:21 GMT+03:00 Sergey Kozlov :
>
> > Hi
> >
> > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> >
> > I propose to introduce the requirement to add an example for new
> > features/functionalities. It will make easier further using/testing by
> the
> > community and may be for review process as well.
> >
> > --
> > Sergey Kozlov
> >
>

Re: Providing an example as part of contribution

[Anton Vinogradov]

+100500

On Tue, Dec 29, 2015 at 4:21 PM, Sergey Kozlov  wrote:

> Hi
>
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
>
> I propose to introduce the requirement to add an example for new
> features/functionalities. It will make easier further using/testing by the
> community and may be for review process as well.
>
> --
> Sergey Kozlov
>

[VOTE] Apache Ignite 1.5.0.final RC3

[Anton Vinogradov]

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.

Re: Optional modules without README and apache license

[Anton Vinogradov]

Raul, Thanks.

On Fri, Nov 27, 2015 at 2:54 PM, Raul Kripalani <ra...@apache.org> wrote:

> On Fri, Nov 27, 2015 at 9:38 AM, Anton Vinogradov <
> avinogra...@gridgain.com>
> wrote:
>
> > Raul, we are goin to make release today (4 hours later this email) is it
> > possible to push jms11, zk, mqtt changes before this moment?
> >
>
> Changes pushed.
>
> 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
>

Re: Publishing readme.io site

[Anton Vinogradov]

Pavel,

I think we should not publish ignite.NET wiki at separate domain. Better
case is to add .Net (c++, etc ... ) section to
https://apacheignite.readme.io/


On Tue, Dec 1, 2015 at 11:35 AM, Pavel Tupitsyn 
wrote:

> It was available, and I have just taken it.
> Dmitry, I've added you as an admin.
>
> * Can you please activate it, or tell me how to do it?
> * I've added a logo, but it does not look good (too small), can you add a
> proper one?
>
> Thanks,
>
> On Tue, Dec 1, 2015 at 9:50 AM, Dmitriy Setrakyan 
> wrote:
>
> > On Mon, Nov 30, 2015 at 10:44 PM, Pavel Tupitsyn  >
> > wrote:
> >
> > > Dmitry, thank you, I see it.
> > >
> > > However, I'm concerned that site name is not consistent with the main
> > one:
> > > * apacheignite.readme.io
> > > * apache-ignite-net.readme.io
> > >
> > > I think it first part should be the same: apacheignite-net.readme.io.
> >
> >
> > I agree, however I don’t know how to change the URL. Is the URL you are
> > suggesting available or has someone in the community already taken it? If
> > someone started using it already, can I be invited?
> >
> >
> > >
> >
> >
> > > Thanks,
> > >
> > >
> > > On Tue, Dec 1, 2015 at 5:27 AM, Dmitriy Setrakyan <
> dsetrak...@apache.org
> > >
> > > wrote:
> > >
> > > > Pavel,
> > > >
> > > > I have created Apache Ignite for .NET space in readme and added you
> to
> > > the
> > > > project. You should have an invite in your inbox.
> > > >
> > > > D.
> > > >
> > > > On Mon, Nov 30, 2015 at 10:01 AM, Pavel Tupitsyn <
> > ptupit...@gridgain.com
> > > >
> > > > wrote:
> > > >
> > > > > Hello Igniters,
> > > > >
> > > > > We have Apache Ignite readme.io site published:
> > > > > https://apacheignite.readme.io/
> > > > > I'm working on a similar site for Apache Ignite .NET and have some
> > > > > questions:
> > > > >
> > > > > 1) Publishing. Should I file an open source application? How did we
> > do
> > > it
> > > > > before?
> > > > > 2) Naming. Should it be apacheignite-dotnet, apacheignite-net,
> > > > > apache-ignite-net?
> > > > >
> > > > > Thanks,
> > > > >
> > > > > --
> > > > > --
> > > > > Pavel Tupitsyn
> > > > > GridGain Systems, Inc.
> > > > > www.gridgain.com
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > --
> > > Pavel Tupitsyn
> > > GridGain Systems, Inc.
> > > www.gridgain.com
> > >
> >
>
>
>
> --
> --
> Pavel Tupitsyn
> GridGain Systems, Inc.
> www.gridgain.com
>

Re: Publishing readme.io site

[Anton Vinogradov]

Pavel,

Yes, I did not found how how to create 2-level category too. So seems, if
it impossible - better to create separate domain.

On Tue, Dec 1, 2015 at 12:30 PM, Pavel Tupitsyn <ptupit...@gridgain.com>
wrote:

> Anton, how would you do that?
> As I understand, our readme.io template is two-level, so it would be
> impossible to discern between different platforms within one subdomain.
>
> Thanks,
>
> On Tue, Dec 1, 2015 at 12:11 PM, Anton Vinogradov <
> avinogra...@gridgain.com>
> wrote:
>
> > Pavel,
> >
> > I think we should not publish ignite.NET wiki at separate domain. Better
> > case is to add .Net (c++, etc ... ) section to
> > https://apacheignite.readme.io/
> >
> >
> > On Tue, Dec 1, 2015 at 11:35 AM, Pavel Tupitsyn <ptupit...@gridgain.com>
> > wrote:
> >
> > > It was available, and I have just taken it.
> > > Dmitry, I've added you as an admin.
> > >
> > > * Can you please activate it, or tell me how to do it?
> > > * I've added a logo, but it does not look good (too small), can you
> add a
> > > proper one?
> > >
> > > Thanks,
> > >
> > > On Tue, Dec 1, 2015 at 9:50 AM, Dmitriy Setrakyan <
> dsetrak...@apache.org
> > >
> > > wrote:
> > >
> > > > On Mon, Nov 30, 2015 at 10:44 PM, Pavel Tupitsyn <
> > ptupit...@gridgain.com
> > > >
> > > > wrote:
> > > >
> > > > > Dmitry, thank you, I see it.
> > > > >
> > > > > However, I'm concerned that site name is not consistent with the
> main
> > > > one:
> > > > > * apacheignite.readme.io
> > > > > * apache-ignite-net.readme.io
> > > > >
> > > > > I think it first part should be the same:
> apacheignite-net.readme.io
> > .
> > > >
> > > >
> > > > I agree, however I don’t know how to change the URL. Is the URL you
> are
> > > > suggesting available or has someone in the community already taken
> it?
> > If
> > > > someone started using it already, can I be invited?
> > > >
> > > >
> > > > >
> > > >
> > > >
> > > > > Thanks,
> > > > >
> > > > >
> > > > > On Tue, Dec 1, 2015 at 5:27 AM, Dmitriy Setrakyan <
> > > dsetrak...@apache.org
> > > > >
> > > > > wrote:
> > > > >
> > > > > > Pavel,
> > > > > >
> > > > > > I have created Apache Ignite for .NET space in readme and added
> you
> > > to
> > > > > the
> > > > > > project. You should have an invite in your inbox.
> > > > > >
> > > > > > D.
> > > > > >
> > > > > > On Mon, Nov 30, 2015 at 10:01 AM, Pavel Tupitsyn <
> > > > ptupit...@gridgain.com
> > > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Hello Igniters,
> > > > > > >
> > > > > > > We have Apache Ignite readme.io site published:
> > > > > > > https://apacheignite.readme.io/
> > > > > > > I'm working on a similar site for Apache Ignite .NET and have
> > some
> > > > > > > questions:
> > > > > > >
> > > > > > > 1) Publishing. Should I file an open source application? How
> did
> > we
> > > > do
> > > > > it
> > > > > > > before?
> > > > > > > 2) Naming. Should it be apacheignite-dotnet, apacheignite-net,
> > > > > > > apache-ignite-net?
> > > > > > >
> > > > > > > Thanks,
> > > > > > >
> > > > > > > --
> > > > > > > --
> > > > > > > Pavel Tupitsyn
> > > > > > > GridGain Systems, Inc.
> > > > > > > www.gridgain.com
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > --
> > > > > Pavel Tupitsyn
> > > > > GridGain Systems, Inc.
> > > > > www.gridgain.com
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > --
> > > Pavel Tupitsyn
> > > GridGain Systems, Inc.
> > > www.gridgain.com
> > >
> >
>
>
>
> --
> --
> Pavel Tupitsyn
> GridGain Systems, Inc.
> www.gridgain.com
>

Ignite 1.5 Wiki changed status to Beta.

[Anton Vinogradov]

Igniters,

Wiki page https://apacheignite.readme.io/v1.5 now public beta.

Re: EA versioning

[Anton Vinogradov]

Sergi,

Sounds bad.
I've made decision to use EA looking on Hazelcast's versions (
http://mvnrepository.com/artifact/com.hazelcast/hazelcast).

Seems we have to use 'alpha' or use 'ga' at release. Or ignore this case
and recomend users to use explicit version.

On Tue, Dec 1, 2015 at 5:22 PM, Sergi Vladykin <sergi.vlady...@gmail.com>
wrote:

> Guys,
>
> The only issue I see here is Maven versions ordering if we are going to
> release EA maven binaries.
> As far as I understand *ignite-1.5.0-ea* will be **greater** than final
> *ignite-1.5.0* which is wrong.
> This happens because maven (since 3.2 AFAIK) looks for well-known
> qualifiers for ordering
> and it seems that EA is not in the list. See [1] and [2] for details.
> Probably we have to use *beta* or *milestone* instead of EA and it will
> work for us.
>
> Sergi
>
> [1] http://stackoverflow.com/a/31482463/4012372
> [2]
>
> http://grepcode.com/file/repo1.maven.org/maven2/org.apache.maven/maven-artifact/3.3.3/org/apache/maven/artifact/versioning/ComparableVersion.java
>
>
>
>
> 2015-12-01 15:51 GMT+03:00 Alexey Kuznetsov <akuznet...@gridgain.com>:
>
> > I asked my question because I never see EA and RC in one name. Only one
> of
> > them.
> > But seems it is OK to have such name.
> >
> > On Tue, Dec 1, 2015 at 7:11 PM, Anton Vinogradov <
> avinogra...@gridgain.com
> > >
> > wrote:
> >
> > > RC means Release Candidate.
> > > After successful vote RC cut from name, and this binary becomes
> release.
> > >
> > > On Tue, Dec 1, 2015 at 1:04 PM, Alexey Kuznetsov <
> > akuznet...@gridgain.com>
> > > wrote:
> > >
> > > > Ok, now I see.
> > > >
> > > > But just one more question it is possible to add "-vote1" instead
> > "-rc1"?
> > > > Or I just do not understand what is abbreviated as "-rc1" ?
> > > >
> > > > On Tue, Dec 1, 2015 at 4:53 PM, Sergey Kozlov <skoz...@gridgain.com>
> > > > wrote:
> > > >
> > > > > Alexey.
> > > > >
> > > > > We don't mix RC and EA. RCX just added to package for vote.
> > > > >
> > > > > On Tue, Dec 1, 2015 at 12:41 PM, Alexey Kuznetsov <
> > > > akuznet...@gridgain.com
> > > > > >
> > > > > wrote:
> > > > >
> > > > > > Looks good for me, but why do we need "-rc1" ???
> > > > > >
> > > > > > Maybe if vote failed just increase EA number?
> > > > > >
> > > > > > Mixing EA and RC in one name - looks (IMHO) confusing for me...
> > > > > >
> > > > > > On Tue, Dec 1, 2015 at 4:35 PM, Yakov Zhdanov <
> yzhda...@apache.org
> > >
> > > > > wrote:
> > > > > >
> > > > > > > Guys,
> > > > > > >
> > > > > > > When trying to release Apache Ignite 1.5.0 we came to
> conclusion
> > > that
> > > > > we
> > > > > > > had to proceed with EA version rather than with final release
> due
> > > to
> > > > > many
> > > > > > > reasons.
> > > > > > >
> > > > > > > I think that everyone understands the purposes of EA versions
> and
> > > the
> > > > > > > advantages that we gain if we establish this process in a
> proper
> > > way.
> > > > > > >
> > > > > > > Now I see the following points. Let's discuss and put results
> on
> > > our
> > > > > > > project wiki.
> > > > > > >
> > > > > > > 1. Complex features will be released only through EA process,
> but
> > > > point
> > > > > > > and/or patch releases may omit this step.
> > > > > > >
> > > > > > > 2. The first EA (EA1?) build can be released when upcoming
> > release
> > > > gets
> > > > > > > 100% code/feature complete and it is verified that
> > build/deployment
> > > > > > > procedures work and TC is in green state.
> > > > > > >
> > > > > > > 3. EA version names should be the following:
> > > > > > >
> > > > > > > * apache-ignite-X.X.X-EA1
> > > > > > > * apache-ignite-X.X.X-EA2
> > > > > > > * ...
> > > > > > > * apache-ignite-X.X.X-EA15
> > > > > > >
> > > > > > > Where X is a number. Index after EA makes ordering intuitive.
> > > > > > >
> > > > > > > 4. EA versions go through the same voting process as we have
> for
> > > > > release
> > > > > > > procedure now. E.g. apache-ignite-1.5.0-EA1-rc1 will be
> submitted
> > > and
> > > > > > after
> > > > > > > approval "-rc1" part gets stripped.
> > > > > > >
> > > > > > > 5. I would prefer EA versions being available through maven. I
> > know
> > > > > that
> > > > > > > there are different opinions on this and I know the reasoning
> for
> > > > > > opinions,
> > > > > > > but from my standpoint this will save us from managing
> additional
> > > > repos
> > > > > > and
> > > > > > > make everything transparent.
> > > > > > >
> > > > > > >
> > > > > > > Thanks!
> > > > > > >
> > > > > > > --Yakov
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Alexey Kuznetsov
> > > > > > GridGain Systems
> > > > > > www.gridgain.com
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Sergey Kozlov
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Alexey Kuznetsov
> > > > GridGain Systems
> > > > www.gridgain.com
> > > >
> > >
> >
> >
> >
> > --
> > Alexey Kuznetsov
> > GridGain Systems
> > www.gridgain.com
> >
>

Re: Optional modules without README and apache license

[Anton Vinogradov]

Igniters, it's really Important!

It's impossible to release 1.5.0 without README.txt files inside modules.

Please create them at modules made by you or/and at modules you reviewed.

On Wed, Nov 25, 2015 at 5:50 PM, Vasilisa Sidorova 
wrote:

> Dear Igniters,
> we have following optional modules without README.txt and apache-2.0.txt
> license files:
>
> README.txt is not found:
> ignite-jms11
> ignite-kafka
> ignite-mqtt
> ignite-zookeeper
>
> apache-2.0.txt is not found:
> ignite-jms11
> ignite-mqtt
> ignite-zookeeper
>
> I've filed the issue https://issues.apache.org/jira/browse/IGNITE-2003
>
> We are close to the release 1.5. So it will be great if the contributors
> (who added modules above) fixed it according to
>
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Checklistbeforepush
>
> Otherwise it takes more time for others contributors to write documentation
> about unknown modules.
>
> Vasilisa
>

Re: Optional modules without README and apache license

[Anton Vinogradov]

I'll take care of ignite-kafka readme & all apache-2.0.txt

Raul, we are goin to make release today (4 hours later this email) is it
possible to push jms11, zk, mqtt changes before this moment?

On Thu, Nov 26, 2015 at 11:37 AM, Raul Kripalani  wrote:

> Yep. I'll take care of jms11, zk, mqtt.
>
> It was very unfortunate to have picked kafka as a template, where these
> files are missing too.
>
> Also, no mention of these requirements in the Wiki didn't help back then.
> On 25 Nov 2015 14:50, "Vasilisa Sidorova"  wrote:
>
> > Dear Igniters,
> > we have following optional modules without README.txt and apache-2.0.txt
> > license files:
> >
> > README.txt is not found:
> > ignite-jms11
> > ignite-kafka
> > ignite-mqtt
> > ignite-zookeeper
> >
> > apache-2.0.txt is not found:
> > ignite-jms11
> > ignite-mqtt
> > ignite-zookeeper
> >
> > I've filed the issue https://issues.apache.org/jira/browse/IGNITE-2003
> >
> > We are close to the release 1.5. So it will be great if the contributors
> > (who added modules above) fixed it according to
> >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Checklistbeforepush
> >
> > Otherwise it takes more time for others contributors to write
> documentation
> > about unknown modules.
> >
> > Vasilisa
> >
>

Javadoc warnings at Ignite 1.5

[Anton Vinogradov]

Hello,

I've checked output of prerelease build of Ignite 1.5 and found javadoc
warnings like
CamelStreamer.java:51: warning - Tag @link: malformed:
"StreamMultipleTupleExtractor)"

Raul, seems that was your changes. Could you please fix it?

Re: Javadoc warnings at Ignite 1.5

[Anton Vinogradov]

Raul,

Of course I can,
But this changes made by you recently, and it will be nice if you'll fix
them.

I've added some requirment to
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
Please see section Checklist before pust
<https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Checklistbeforepust>
.

On Thu, Nov 19, 2015 at 12:06 PM, Raul Kripalani <ra...@apache.org> wrote:

> Anton,
>
> Could you please just go ahead and fix it? This is a collaborative
> project. Source is not owned by individual people.
>
> And let's not abuse the mailing list for details like this.
>
> Regards,
> Raúl.
> On 19 Nov 2015 08:49, "Anton Vinogradov" <avinogra...@gridgain.com> wrote:
>
>> Hello,
>>
>> I've checked output of prerelease build of Ignite 1.5 and found javadoc
>> warnings like
>> CamelStreamer.java:51: warning - Tag @link: malformed:
>> "StreamMultipleTupleExtractor)"
>>
>> Raul, seems that was your changes. Could you please fix it?
>>
>

Re: Version mismatch Was: [RESULT] [VOTE] Apache Ignite 1.5.0.final Release (RC3)

[Anton Vinogradov]

Sergey,

Correct, thats a backward compatibility fix.
Internal node's version based on maven version but each ".a", ".b" and
".final" replaces with corresponding "-".


On Wed, Jan 6, 2016 at 7:14 AM, Konstantin Boudnik <c...@apache.org> wrote:

> On Tue, Jan 05, 2016 at 08:20PM, Sergey Kozlov wrote:
> > Hi
> >
> > As I rememeber Ignite node prints out the version with dash due internal
> > requirements.
> >
> > Anton V: could you explain why we made such replacement?
>
> That's a bit confusing, not fatal. And it means that there's either an
> alternative version string somewhere, or a transformation of the said
> string.
> In either way - confusing ;)
>
> Thanks
>   Cos
>
> > On Tue, Jan 5, 2016 at 10:09 AM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > wrote:
> >
> > > Cos, this seems to be just a typo. The actual release version in maven
> is
> > > 1.5.0.final.
> > >
> > > On Mon, Jan 4, 2016 at 8:04 PM, Konstantin Boudnik <c...@apache.org>
> wrote:
> > >
> > > > Running into some issues with Zeppelin integration and have noticed
> that
> > > > the
> > > > version reported by the node in the log isn't the same as the version
> > > just
> > > > released. It says
> > > > 1.5.0-final
> > > > instead of
> > > > 1.5.0.final
> > > >
> > > > Cos
> > > >
> > > > On Mon, Jan 04, 2016 at 01:12PM, Anton Vinogradov wrote:
> > > > > Hello!
> > > > >
> > > > > Apache Ignite 1.5.0.final release (RC3) has been accepted.
> > > > >
> > > > > 13 "+1" votes received.
> > > > >
> > > > > Here are the votes received:
> > > > >
> > > > >- Anton Vinogradov (binding)
> > > > >- Nikolay Tikhonov (binding)
> > > > >- Konstantin Boudnik (binding)
> > > > >- Semyon Boikov (binding)
> > > > >- Gianfranco Murador (binding)
> > > > >- Vladimir Ozerov (binding)
> > > > >- Alexey Goncharuk (binding)
> > > > >- Raul Kripalani (binding)
> > > > >- Denis Magda (binding)
> > > > >- Sergi Vladykin (binding)
> > > > >- 姜 为
> > > > >- Alexey Kuznetsov
> > > > >- Roman Shtykh
> > > > >
> > > > > Here is the link to vote thread -
> > > > >
> > > >
> > >
> http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-1-5-0-final-RC3-td6305.html
> > > > >
> > > > > Ignite 1.5.0.final successfuly released to
> > > > > https://dist.apache.org/repos/dist/release/ignite/1.5.0.final/
> > > > >
> > > > > Site & Maven will be updated soon.
> > > > >
> > > > > Thanks!
> > > >
> > >
> >
> >
> >
> > --
> > Sergey Kozlov
> > GridGain Systems
> > www.gridgain.com
>

new committer: Vladisav Jelisavcic

[Anton Vinogradov]

The Project Management Committee (PMC) for Apache Ignite has asked Vladisav
Jelisavcic
to become a committer and we are pleased to announce that Vladisav has
accepted.

Being a committer enables easier contribution to the project since there is
no need to go via the patch submission process. This should enable better
productivity.

Re: Maven conflicts within ignite-core from duplicated classes

[Anton Vinogradov]

We already have 2 dependencies at ignite-core:
*javax.cache.cache-api* and *org.gridgain.ignite-shmem*
(ASAIK we have an issue to redeploy org.gridgain.ignite-shmem as
org.apache.ignite.ignite-shmem)

On Thu, Jun 16, 2016 at 11:57 AM, Vladimir Ozerov 
wrote:

> And why do we afraid this dependency? It has "CLASS" retention so users do
> not need them in runtime, AFAIK.
>
> On Thu, Jun 16, 2016 at 11:19 AM, Vladislav Pyatkov  >
> wrote:
>
> > Why not just rename these classes?
> >
> > On Thu, Jun 16, 2016 at 11:16 AM, Semyon Boikov 
> > wrote:
> >
> > > As far as I know the only reason sources of Nullable are in Ignite - we
> > > did not want to have any dependecy for 'core' module.
> > >
> > > On Mon, Jun 13, 2016 at 10:04 AM, Denis Magda 
> > wrote:
> > >
> > >> Hi Pete,
> > >>
> > >> CC-ing Ignite dev list to the thread as well.
> > >>
> > >> Igniters, up to today is there any reason why we need to include
> sources
> > >> of Nullable JetBrain’s annotation in Ignite sources?
> > >>
> > >> As I see we can rather import that latest version from the maven
> > >> repository
> > >> https://maven-repository.com/artifact/org.jetbrains/annotations/15.0
> > >>
> > >> *Anton, *please take a look at Pete issue and suggest a workaround and
> > >> generic solution overall.
> > >>
> > >> —
> > >> Denis
> > >>
> > >> On Jun 9, 2016, at 1:32 PM, Pete Campton 
> > wrote:
> > >>
> > >> Hello,
> > >>
> > >> I've come across an issue where there are a couple of classes
> duplicated
> > >> from org.jetbrains.annotations within the ignite-core module which
> > conflict
> > >> with other part of our code base.
> > >>
> > >> As these files are duplicated rather than being referenced as a maven
> > >> dependency I am unable to exclude them or reference a specific version
> > of
> > >> the org.jetbrains.annotations artifact.
> > >>
> > >> Specifically, the included version cannot be used to annotate types
> > >> ignite-core-1.6.0.jar:org.jetbrains.annotations.Nullable ...
> > >> @Target({ElementType.METHOD, ElementType.FIELD, ElementType.PARAMETER,
> > >> ElementType.LOCAL_VARIABLE})
> > >> annotations-15.0.jar:org.jetbrains.annotations.Nullable ...
> > >> @Target({ElementType.METHOD, ElementType.FIELD, ElementType.PARAMETER,
> > >> ElementType.LOCAL_VARIABLE, ElementType.TYPE_USE})
> > >>
> > >> As far as I know there isn't an easy way of excluding these files from
> > >> within the ignite-core module. Is there are reason why these
> "external"
> > >> files have been duplicated within the ignite code base rather than
> being
> > >> referenced as a maven dependency? Or alternatively, has anyone come
> > across
> > >> a way of avoiding these conflicts?
> > >>
> > >> Thanks
> > >> Pete
> > >>
> > >>
> > >>
> > >
> >
>

Re: Maven conflicts within ignite-core from duplicated classes

[Anton Vinogradov]

Denis,

I've created issue: https://issues.apache.org/jira/browse/IGNITE-3323

On Mon, Jun 13, 2016 at 10:04 AM, Denis Magda  wrote:

> Hi Pete,
>
> CC-ing Ignite dev list to the thread as well.
>
> Igniters, up to today is there any reason why we need to include sources
> of Nullable JetBrain’s annotation in Ignite sources?
>
> As I see we can rather import that latest version from the maven repository
> https://maven-repository.com/artifact/org.jetbrains/annotations/15.0
>
> *Anton, *please take a look at Pete issue and suggest a workaround and
> generic solution overall.
>
> —
> Denis
>
> On Jun 9, 2016, at 1:32 PM, Pete Campton  wrote:
>
> Hello,
>
> I've come across an issue where there are a couple of classes duplicated
> from org.jetbrains.annotations within the ignite-core module which conflict
> with other part of our code base.
>
> As these files are duplicated rather than being referenced as a maven
> dependency I am unable to exclude them or reference a specific version of
> the org.jetbrains.annotations artifact.
>
> Specifically, the included version cannot be used to annotate types
> ignite-core-1.6.0.jar:org.jetbrains.annotations.Nullable ...
> @Target({ElementType.METHOD, ElementType.FIELD, ElementType.PARAMETER,
> ElementType.LOCAL_VARIABLE})
> annotations-15.0.jar:org.jetbrains.annotations.Nullable ...
> @Target({ElementType.METHOD, ElementType.FIELD, ElementType.PARAMETER,
> ElementType.LOCAL_VARIABLE, ElementType.TYPE_USE})
>
> As far as I know there isn't an easy way of excluding these files from
> within the ignite-core module. Is there are reason why these "external"
> files have been duplicated within the ignite code base rather than being
> referenced as a maven dependency? Or alternatively, has anyone come across
> a way of avoiding these conflicts?
>
> Thanks
> Pete
>
>
>

Re: Ignite Download links broken

[Anton Vinogradov]

Dmitriy,

I'm not sure I understand what should I ask INFRA to do.
We had broken mirror resolving at download page, not sure INFRA can solve
html/js issues.

On Mon, Jun 20, 2016 at 6:07 PM, Dmitriy Setrakyan <dsetrak...@apache.org>
wrote:

> Anton, did you file an INFRA issue?
>
> On Mon, Jun 20, 2016 at 6:42 AM, Pavel Tupitsyn <ptupit...@gridgain.com>
> wrote:
>
> > Thanks Anton, works for me now.
> >
> > On Mon, Jun 20, 2016 at 4:29 PM, Anton Vinogradov <
> > avinogra...@gridgain.com> wrote:
> >
> >> Download urls changed to https://archive.apache.org/dist/ignite/*
> >>
> >>
> >> On Mon, Jun 20, 2016 at 4:14 PM, Dmitriy Setrakyan <
> dsetrak...@apache.org
> >> > wrote:
> >>
> >>> I think we should do it, at least for now, until the mirror issue is
> >>> resolved. We should also file an INFRA issue in parallel. Anton, do you
> >>> mind fixing it?
> >>>
> >>> On Mon, Jun 20, 2016 at 6:13 AM, Anton Vinogradov <a...@apache.org>
> wrote:
> >>>
> >>>> We already provides "hard-coded links (without mirror) " to previous
> >>>> versions.
> >>>> For example
> >>>>
> >>>>
> https://archive.apache.org/dist/ignite/1.4.0/apache-ignite-fabric-1.4.0-bin.zip
> >>>> I think we can do that for all releases.
> >>>>
> >>>>
> >>>> On Mon, Jun 20, 2016 at 4:08 PM, Dmitriy Setrakyan <
> >>>> dsetrak...@apache.org>
> >>>> wrote:
> >>>>
> >>>> > Is it possible to provide hard-coded links (without mirror) in the
> >>>> mean
> >>>> > time, while we are resolving this issue?
> >>>> >
> >>>> > Pavel, I think this issue should be reported to INFRA, not Ignite. I
> >>>> doubt
> >>>> > Ignite community can do anything to fix it.
> >>>> >
> >>>> > D.
> >>>> >
> >>>> > On Mon, Jun 20, 2016 at 6:04 AM, Pavel Tupitsyn <
> >>>> ptupit...@gridgain.com>
> >>>> > wrote:
> >>>> >
> >>>> >> I have reported this issue 4 months ago, please see details there:
> >>>> >> https://issues.apache.org/jira/browse/IGNITE-2743
> >>>> >> Christos, your link is missing .cgi suffix.
> >>>> >>
> >>>> >> Pavel.
> >>>> >>
> >>>> >> On Mon, Jun 20, 2016 at 3:53 PM, Vladisav Jelisavcic <
> >>>> vladis...@gmail.com
> >>>> >> > wrote:
> >>>> >>
> >>>> >>> Not working for me also,
> >>>> >>> but only 1.6.0 (latest) and 1.5.0.final, the rest is working fine.
> >>>> >>>
> >>>> >>> On Mon, Jun 20, 2016 at 8:02 AM, Sergey Kozlov <
> >>>> skoz...@gridgain.com>
> >>>> >>> wrote:
> >>>> >>>
> >>>> >>>> Hi
> >>>> >>>>
> >>>> >>>> It's a known issue: apache site puts links to a nearest site for
> >>>> user (I
> >>>> >>>> suppose it based on IP address) and does it incorrect.
> >>>> >>>>
> >>>> >>>> On Mon, Jun 20, 2016 at 8:37 AM, Dmitriy Setrakyan <
> >>>> >>>> dsetrak...@apache.org>
> >>>> >>>> wrote:
> >>>> >>>>
> >>>> >>>> > Worked for me just now. Can you try again?
> >>>> >>>> >
> >>>> >>>> > On Sun, Jun 19, 2016 at 2:59 AM, Christos Erotocritou <
> >>>> >>>> > chris...@gridgain.com> wrote:
> >>>> >>>> >
> >>>> >>>> >> Hey guys,
> >>>> >>>> >>
> >>>> >>>> >> The links on the website seem to be broken, can someone check
> >>>> this?
> >>>> >>>> >>
> >>>> >>>> >> https://ignite.apache.org/download.html#binaries <
> >>>> >>>> >> https://ignite.apache.org/download.html#binaries>
> >>>> >>>> >>
> >>>> >>>> >> Thanks,
> >>>> >>>> >>
> >>>> >>>> >> Christos
> >>>> >>>> >
> >>>> >>>> >
> >>>> >>>> >
> >>>> >>>>
> >>>> >>>>
> >>>> >>>> --
> >>>> >>>> Sergey Kozlov
> >>>> >>>> GridGain Systems
> >>>> >>>> www.gridgain.com
> >>>> >>>>
> >>>> >>>
> >>>> >>>
> >>>> >>
> >>>> >
> >>>>
> >>>
> >>>
> >>
> >
>

Re: Ignite REST API is not actually RESTful

[Anton Vinogradov]

Alexey,
In this case we will make Not REST again.

Here is good article about idempotency:
http://www.restapitutorial.com/lessons/idempotency.html

On Mon, Jun 20, 2016 at 5:46 PM, Alexey Kuznetsov 
wrote:

> Pavel,
>
> >> What is the use case?
> As far as I know it could be used for quick testing. But I agree that it is
> not mandatory.
> Testing could be done with appropriate tools.
>
>
> >>> large SQL query that could be fetched page by page
> >>REST is stateless. This should be handled by the user (with LIMIT/OFFSET
> in SQL).
> In this case we will force users to implement complex solutions.
> IMHO in some cases we could have state.
>
>
> On Mon, Jun 20, 2016 at 9:37 PM, Pavel Tupitsyn 
> wrote:
>
> > Alexey,
> >
> > > be able to run all command from browser address line
> > What is the use case? Non-developers do not need that. Developers have
> > better tools than a browser to test an API.
> > GET requests must never modify data, this is very important. People and
> > software assume GET to be safe.
> >
> > > large SQL query that could be fetched page by page
> > REST is stateless. This should be handled by the user (with LIMIT/OFFSET
> in
> > SQL).
> >
> > Pavel.
> >
> > On Mon, Jun 20, 2016 at 5:20 PM, Sergey Kozlov 
> > wrote:
> >
> > > We also can consider to keep the compatibility and move new API either
> to
> > > new http port or use new url (e.g. http://localhost:8080/api/rest
> > instead
> > > of http://localhost:8080/ignite)
> > >
> > > On Mon, Jun 20, 2016 at 5:15 PM, Alexey Kuznetsov <
> > akuznet...@gridgain.com
> > > >
> > > wrote:
> > >
> > > > Pavel,
> > > >
> > > > Current API was developed long time ago and was not actively
> developed.
> > > > It may looks inconsistent for some use cases.
> > > > May be it is a good idea to develop new API and deprecate current.
> > > >
> > > > From my experience we should take care:
> > > > 1) "null" cache names
> > > > 2) some commands could have state, for example large SQL query that
> > could
> > > > be fetched page by page
> > > > 3) It will be "nice  to have" to be able to run all command from
> > browser
> > > > address line.
> > > >
> > > >
> > > > On Mon, Jun 20, 2016 at 8:59 PM, Pavel Tupitsyn <
> ptupit...@apache.org>
> > > > wrote:
> > > >
> > > > > Igniters,
> > > > >
> > > > > There are two serious issues with current Ignite REST API:
> > > > >
> > > > > 1) It does not care about HTTP verbs (GET/POST/etc).
> > > > > GET must never modify anything, for example (because GET requests
> can
> > > be
> > > > > cached, duplicated, etc).
> > > > >
> > > > > 2) Proper resource paths are not used
> > > > > For example, to get a cache value, instead of
> > > > > GET /ignite?cmd=get=myKey=partionedCache
> > > > > it should be
> > > > > GET /ignite/caches/partitionedCache/keys/myKey/
> > > > >
> > > > > Modify cache key:
> > > > > PUT /ignite/caches/partitionedCache/keys/myKey/
> > > > > DELETE /ignite/caches/partitionedCache/keys/myKey/
> > > > >
> > > > >
> > > > > I think we should deprecate current API and provide a new one that
> > > > follows
> > > > > the guidelines.
> > > > > A good writeup on a proper REST API design can be found there:
> > > > > https://zalando.github.io/restful-api-guidelines/
> > > > >
> > > > >
> > > > > Thoughts, comments?
> > > > >
> > > > > Pavel.
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Alexey Kuznetsov
> > > > GridGain Systems
> > > > www.gridgain.com
> > > >
> > >
> > >
> > >
> > > --
> > > Sergey Kozlov
> > > GridGain Systems
> > > www.gridgain.com
> > >
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>

Re: Ignite REST API is not actually RESTful

[Anton Vinogradov]

Pavel,

Looks good, but:
According to Swagger demo  need to use
singular (caches->cache).

And I'm also not sure we need ignite preffix.

On Mon, Jun 20, 2016 at 5:15 PM, Alexey Kuznetsov 
wrote:

> Pavel,
>
> Current API was developed long time ago and was not actively developed.
> It may looks inconsistent for some use cases.
> May be it is a good idea to develop new API and deprecate current.
>
> From my experience we should take care:
> 1) "null" cache names
> 2) some commands could have state, for example large SQL query that could
> be fetched page by page
> 3) It will be "nice  to have" to be able to run all command from browser
> address line.
>
>
> On Mon, Jun 20, 2016 at 8:59 PM, Pavel Tupitsyn 
> wrote:
>
> > Igniters,
> >
> > There are two serious issues with current Ignite REST API:
> >
> > 1) It does not care about HTTP verbs (GET/POST/etc).
> > GET must never modify anything, for example (because GET requests can be
> > cached, duplicated, etc).
> >
> > 2) Proper resource paths are not used
> > For example, to get a cache value, instead of
> > GET /ignite?cmd=get=myKey=partionedCache
> > it should be
> > GET /ignite/caches/partitionedCache/keys/myKey/
> >
> > Modify cache key:
> > PUT /ignite/caches/partitionedCache/keys/myKey/
> > DELETE /ignite/caches/partitionedCache/keys/myKey/
> >
> >
> > I think we should deprecate current API and provide a new one that
> follows
> > the guidelines.
> > A good writeup on a proper REST API design can be found there:
> > https://zalando.github.io/restful-api-guidelines/
> >
> >
> > Thoughts, comments?
> >
> > Pavel.
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>

Re: Ignite Download links broken

[Anton Vinogradov]

We already provides "hard-coded links (without mirror) " to previous
versions.
For example
https://archive.apache.org/dist/ignite/1.4.0/apache-ignite-fabric-1.4.0-bin.zip
I think we can do that for all releases.


On Mon, Jun 20, 2016 at 4:08 PM, Dmitriy Setrakyan 
wrote:

> Is it possible to provide hard-coded links (without mirror) in the mean
> time, while we are resolving this issue?
>
> Pavel, I think this issue should be reported to INFRA, not Ignite. I doubt
> Ignite community can do anything to fix it.
>
> D.
>
> On Mon, Jun 20, 2016 at 6:04 AM, Pavel Tupitsyn 
> wrote:
>
>> I have reported this issue 4 months ago, please see details there:
>> https://issues.apache.org/jira/browse/IGNITE-2743
>> Christos, your link is missing .cgi suffix.
>>
>> Pavel.
>>
>> On Mon, Jun 20, 2016 at 3:53 PM, Vladisav Jelisavcic > > wrote:
>>
>>> Not working for me also,
>>> but only 1.6.0 (latest) and 1.5.0.final, the rest is working fine.
>>>
>>> On Mon, Jun 20, 2016 at 8:02 AM, Sergey Kozlov 
>>> wrote:
>>>
 Hi

 It's a known issue: apache site puts links to a nearest site for user (I
 suppose it based on IP address) and does it incorrect.

 On Mon, Jun 20, 2016 at 8:37 AM, Dmitriy Setrakyan <
 dsetrak...@apache.org>
 wrote:

 > Worked for me just now. Can you try again?
 >
 > On Sun, Jun 19, 2016 at 2:59 AM, Christos Erotocritou <
 > chris...@gridgain.com> wrote:
 >
 >> Hey guys,
 >>
 >> The links on the website seem to be broken, can someone check this?
 >>
 >> https://ignite.apache.org/download.html#binaries <
 >> https://ignite.apache.org/download.html#binaries>
 >>
 >> Thanks,
 >>
 >> Christos
 >
 >
 >


 --
 Sergey Kozlov
 GridGain Systems
 www.gridgain.com

>>>
>>>
>>
>

Re: Ignite Download links broken

[Anton Vinogradov]

Download urls changed to https://archive.apache.org/dist/ignite/*


On Mon, Jun 20, 2016 at 4:14 PM, Dmitriy Setrakyan <dsetrak...@apache.org>
wrote:

> I think we should do it, at least for now, until the mirror issue is
> resolved. We should also file an INFRA issue in parallel. Anton, do you
> mind fixing it?
>
> On Mon, Jun 20, 2016 at 6:13 AM, Anton Vinogradov <a...@apache.org> wrote:
>
>> We already provides "hard-coded links (without mirror) " to previous
>> versions.
>> For example
>>
>> https://archive.apache.org/dist/ignite/1.4.0/apache-ignite-fabric-1.4.0-bin.zip
>> I think we can do that for all releases.
>>
>>
>> On Mon, Jun 20, 2016 at 4:08 PM, Dmitriy Setrakyan <dsetrak...@apache.org
>> >
>> wrote:
>>
>> > Is it possible to provide hard-coded links (without mirror) in the mean
>> > time, while we are resolving this issue?
>> >
>> > Pavel, I think this issue should be reported to INFRA, not Ignite. I
>> doubt
>> > Ignite community can do anything to fix it.
>> >
>> > D.
>> >
>> > On Mon, Jun 20, 2016 at 6:04 AM, Pavel Tupitsyn <ptupit...@gridgain.com
>> >
>> > wrote:
>> >
>> >> I have reported this issue 4 months ago, please see details there:
>> >> https://issues.apache.org/jira/browse/IGNITE-2743
>> >> Christos, your link is missing .cgi suffix.
>> >>
>> >> Pavel.
>> >>
>> >> On Mon, Jun 20, 2016 at 3:53 PM, Vladisav Jelisavcic <
>> vladis...@gmail.com
>> >> > wrote:
>> >>
>> >>> Not working for me also,
>> >>> but only 1.6.0 (latest) and 1.5.0.final, the rest is working fine.
>> >>>
>> >>> On Mon, Jun 20, 2016 at 8:02 AM, Sergey Kozlov <skoz...@gridgain.com>
>> >>> wrote:
>> >>>
>> >>>> Hi
>> >>>>
>> >>>> It's a known issue: apache site puts links to a nearest site for
>> user (I
>> >>>> suppose it based on IP address) and does it incorrect.
>> >>>>
>> >>>> On Mon, Jun 20, 2016 at 8:37 AM, Dmitriy Setrakyan <
>> >>>> dsetrak...@apache.org>
>> >>>> wrote:
>> >>>>
>> >>>> > Worked for me just now. Can you try again?
>> >>>> >
>> >>>> > On Sun, Jun 19, 2016 at 2:59 AM, Christos Erotocritou <
>> >>>> > chris...@gridgain.com> wrote:
>> >>>> >
>> >>>> >> Hey guys,
>> >>>> >>
>> >>>> >> The links on the website seem to be broken, can someone check
>> this?
>> >>>> >>
>> >>>> >> https://ignite.apache.org/download.html#binaries <
>> >>>> >> https://ignite.apache.org/download.html#binaries>
>> >>>> >>
>> >>>> >> Thanks,
>> >>>> >>
>> >>>> >> Christos
>> >>>> >
>> >>>> >
>> >>>> >
>> >>>>
>> >>>>
>> >>>> --
>> >>>> Sergey Kozlov
>> >>>> GridGain Systems
>> >>>> www.gridgain.com
>> >>>>
>> >>>
>> >>>
>> >>
>> >
>>
>
>

Re: Fwd: TC access

[Anton Vinogradov]

Alexey,

I've fixed adress.

Seems, you have good vision how to describe TeamCity usage, could you pleae
create it?


On Wed, Jun 29, 2016 at 10:56 AM, Alexey Kuznetsov <akuznet...@gridgain.com>
wrote:

> Anton,
>
> I noticed that wiki page
>
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Creation
> refers to TC by IP and not by name http://ci.ignite.apache.org
>
> And I also agree with Dima - we could have a special paragraph on that page
> about TC.
> In current version info about TC is spread all over that page.
> IMHO it will be very informative to have a special TC paragraph.
>
>
>
> On Wed, Jun 29, 2016 at 2:11 PM, Anton Vinogradov <
> avinogra...@gridgain.com>
> wrote:
>
> > Dmitriy,
> >
> > TeamCity usage is a part of contribution process.
> > The only reason for contributor to use TeamCity is to check pull-request.
> > Thats why TeamCity usage explained at " Create GitHub pull-request
> > -> Creation" section.
> >
> >
> > On Wed, Jun 29, 2016 at 12:46 AM, Dmitriy Setrakyan <
> dsetrak...@apache.org
> > >
> > wrote:
> >
> > > Anton, I think the documentation for TeamCity if well-belied and hardly
> > > noticeable. Do you mind creating a separate section for it, so everyone
> > > will know how their PR will be tested?
> > >
> > > On Tue, Jun 28, 2016 at 12:25 AM, Anton Vinogradov <
> > > avinogra...@gridgain.com
> > > > wrote:
> > >
> > > > Hi All,
> > > >
> > > > 1) Testing at TeamCity already documented here:
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Creation
> > > > 2) We cannot trigger every pullrequest testing automaticaly because
> it
> > > > takes ~1.5 hours to test only one, but we have more than 50 commits
> per
> > > day
> > > > at active pullrequests.
> > > > We have automatical testing only for master and release branches.
> > > >
> > > > On Tue, Jun 28, 2016 at 9:03 AM, mabiao <mab...@ict.ac.cn> wrote:
> > > >
> > > > > I wonder if we could make the continuous integration test be
> > triggered
> > > > > automatically?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > -- 原始邮件 --
> > > > > 发件人: "Dmitriy Setrakyan";<dsetrak...@apache.org>;
> > > > > 发送时间: 2016年6月28日(星期二) 中午1:08
> > > > > 收件人: "dev"<dev@ignite.apache.org>;
> > > > >
> > > > > 主题: Fwd: TC access
> > > > >
> > > > >
> > > > >
> > > > > Anton, do you mind documenting this for posterity?
> > > > >
> > > > > -- Forwarded message --
> > > > > From: Alexey Kuznetsov <akuznet...@gridgain.com>
> > > > > Date: Mon, Jun 27, 2016 at 10:07 PM
> > > > > Subject: Re: TC access
> > > > > To: u...@ignite.apache.org
> > > > >
> > > > >
> > > > > Hmmm,...
> > > > >
> > > > > Seems NO. I searched over web site and wiki and not found anything.
> > > > > We could ask Anton as the most experienced person to add
> appropriate
> > > page
> > > > > to wiki.
> > > > >
> > > > > On Tue, Jun 28, 2016 at 12:02 PM, Dmitriy Setrakyan <
> > > > > dsetrak...@gridgain.com
> > > > > > wrote:
> > > > >
> > > > > > Alexey, is this documented?
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Jun 27, 2016, at 9:33 PM, Alexey Kuznetsov <
> > > akuznet...@gridgain.com
> > > > >
> > > > > > wrote:
> > > > > >
> > > > > > Alexandre,
> > > > > >
> > > > > > If you need to test your PR with existing tests just:
> > > > > >  1. Go to http://ci.ignite.apache.org
> > > > > >  2. Register if needed /  Loging.
> > > > > >  3. Select appropriate test / all tests and run them with
> > specifying
> > > > > > number of your PR.
> > > > > >
> > > > > > If you are going to add new tests you need admin privileges for
> > tha

Re: Fwd: TC access

[Anton Vinogradov]

Dmitriy,

TeamCity usage is a part of contribution process.
The only reason for contributor to use TeamCity is to check pull-request.
Thats why TeamCity usage explained at " Create GitHub pull-request
-> Creation" section.


On Wed, Jun 29, 2016 at 12:46 AM, Dmitriy Setrakyan <dsetrak...@apache.org>
wrote:

> Anton, I think the documentation for TeamCity if well-belied and hardly
> noticeable. Do you mind creating a separate section for it, so everyone
> will know how their PR will be tested?
>
> On Tue, Jun 28, 2016 at 12:25 AM, Anton Vinogradov <
> avinogra...@gridgain.com
> > wrote:
>
> > Hi All,
> >
> > 1) Testing at TeamCity already documented here:
> >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Creation
> > 2) We cannot trigger every pullrequest testing automaticaly because it
> > takes ~1.5 hours to test only one, but we have more than 50 commits per
> day
> > at active pullrequests.
> > We have automatical testing only for master and release branches.
> >
> > On Tue, Jun 28, 2016 at 9:03 AM, mabiao <mab...@ict.ac.cn> wrote:
> >
> > > I wonder if we could make the continuous integration test be triggered
> > > automatically?
> > >
> > >
> > >
> > >
> > > -- 原始邮件 --
> > > 发件人: "Dmitriy Setrakyan";<dsetrak...@apache.org>;
> > > 发送时间: 2016年6月28日(星期二) 中午1:08
> > > 收件人: "dev"<dev@ignite.apache.org>;
> > >
> > > 主题: Fwd: TC access
> > >
> > >
> > >
> > > Anton, do you mind documenting this for posterity?
> > >
> > > -- Forwarded message --
> > > From: Alexey Kuznetsov <akuznet...@gridgain.com>
> > > Date: Mon, Jun 27, 2016 at 10:07 PM
> > > Subject: Re: TC access
> > > To: u...@ignite.apache.org
> > >
> > >
> > > Hmmm,...
> > >
> > > Seems NO. I searched over web site and wiki and not found anything.
> > > We could ask Anton as the most experienced person to add appropriate
> page
> > > to wiki.
> > >
> > > On Tue, Jun 28, 2016 at 12:02 PM, Dmitriy Setrakyan <
> > > dsetrak...@gridgain.com
> > > > wrote:
> > >
> > > > Alexey, is this documented?
> > > >
> > > >
> > > >
> > > > On Jun 27, 2016, at 9:33 PM, Alexey Kuznetsov <
> akuznet...@gridgain.com
> > >
> > > > wrote:
> > > >
> > > > Alexandre,
> > > >
> > > > If you need to test your PR with existing tests just:
> > > >  1. Go to http://ci.ignite.apache.org
> > > >  2. Register if needed /  Loging.
> > > >  3. Select appropriate test / all tests and run them with specifying
> > > > number of your PR.
> > > >
> > > > If you are going to add new tests you need admin privileges for that.
> > > > I think Anton can help with this.
> > > >
> > > >
> > > > On Tue, Jun 28, 2016 at 2:04 AM, Alexandre Boudnik <
> > > > alexander.boud...@gmail.com> wrote:
> > > >
> > > >> I don't need access to TC console, I need to have my pull requests
> > > tested.
> > > >> Take care,
> > > >> Alexandre "Sasha" Boudnik
> > > >>
> > > >> call me via Google Voice:
> > > >> 1(405) BUDNIKA
> > > >> 1(405) 283-6452
> > > >>
> > > >>
> > > >>
> > > >> On Mon, Jun 27, 2016 at 2:07 PM, Dmitriy Setrakyan
> > > >> <dsetrak...@apache.org> wrote:
> > > >> > I just realized that I don’t have a link either. Anton, do you
> mind
> > > >> adding
> > > >> > the link to TC to the community dropdown on the website?
> > > >> >
> > > >> > On Mon, Jun 27, 2016 at 10:28 AM, Alexandre Boudnik
> > > >> > <alexander.boud...@gmail.com> wrote:
> > > >> >>
> > > >> >> Hello,
> > > >> >>
> > > >> >> In order to use Ignite's TeamCity, could you provide myself with
> > > >> access to
> > > >> >> it?
> > > >> >>
> > > >> >> Take care,
> > > >> >> Alexandre "Sasha" Boudnik
> > > >> >>
> > > >> >> call me via Google Voice:
> > > >> >> 1(405) BUDNIKA
> > > >> >> 1(405) 283-6452
> > > >> >
> > > >> >
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > Alexey Kuznetsov
> > > > GridGain Systems
> > > > www.gridgain.com
> > > >
> > > >
> > >
> > >
> > > --
> > > Alexey Kuznetsov
> > > GridGain Systems
> > > www.gridgain.com
> > >
> >
>

Grid behavior at key deserialization failure during rebalancing

[Anton Vinogradov]

Igniters,

At this moment key deserialization failure during rebalancing cause strange
situation:

Rebalancing from node sent supply message with broken key will be cancelled
at current topology.
All upcoming supply messages from this node will be be ignored, no new
demand messages to this node will be sent.

But when topology will be changed again, node with broken key will take
path at rebalancing again, untill key deserialization failure happen ...
again.

Do we need to improve this situation, and if we have to how should be
handled case with key deserialization failure?

I see some ways:
1) We can inform user about data loss because of deserialization problems,
but keep current rebalancing strategy
2) We can continue rebalancing from this node, but ignore messages with
broken keys. And inform user about data loss.
3) We can pause rebalancing untill deserialization will be fixed somehow,
for example by shutdowning demanding or supplying node.

Thoughts?

Re: [jira] [Commented] (IGNITE-1523) Need to always serialize user objects with configured marshaller

[Anton Vinogradov]

Val,

I've fixed some cases related to this issue.
In case you know what is left please describe it at issue and assign to me

On Tue, Feb 2, 2016 at 9:20 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Anton,
>
> If you're working in this issue, can you please assign it to yourself?
>
> -Val
>
> -- Forwarded message --
> From: Anton Vinogradov (JIRA) <j...@apache.org>
> Date: Tue, Feb 2, 2016 at 4:43 AM
> Subject: [jira] [Commented] (IGNITE-1523) Need to always serialize user
> objects with configured marshaller
> To: valentin.kuliche...@gmail.com
>
>
>
> [
>
> https://issues.apache.org/jira/browse/IGNITE-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15128185#comment-15128185
> ]
>
> Anton Vinogradov commented on IGNITE-1523:
> --
>
> Fixed unmarshalling of Enum
> Fixed unmarshalling of CacheStoreFactory within CacheConfiguration
> All new checks added to GridCacheReplicatedPreloadSelfTest
>
> > Need to always serialize user objects with configured marshaller
> > 
> >
> > Key: IGNITE-1523
> > URL: https://issues.apache.org/jira/browse/IGNITE-1523
> > Project: Ignite
> >  Issue Type: Improvement
> >  Components: general
> >Reporter: Valentin Kulichenko
> >Assignee: Valentin Kulichenko
> >Priority: Critical
> >  Labels: important, user-request
> > Fix For: 1.6
> >
> >
> > Currently some components (at least discovery) use {{JdkMarshaller}} for
> all objects.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>

Powered by Ignite logo

[Anton Vinogradov]

Igniters,

I'd like to add "Powered by Ignite" logo files to
https://www.apache.org/foundation/press/kit/poweredBy
but I have no such permissions.

Only ASF Members can do it.

"Powered by Ignite" logo files located at /x1/home/sboikov/pb (at
people.apache.org)

Could someone from ASF Members copy them to directory
/x1/www/www.apache.org/content/foundation/press/kit/poweredBy

Thanks.

Re: [jira] [Commented] (IGNITE-1523) Need to always serialize user objects with configured marshaller

[Anton Vinogradov]

Val,

Please see commit 28a5247d37ba65bdcb6119f97023f32d511b5f1e at master.

On Thu, Feb 4, 2016 at 3:53 AM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Anton,
>
> Where can I see the changes?
>
> -Val
>
> On Wed, Feb 3, 2016 at 12:01 AM, Anton Vinogradov <
> avinogra...@gridgain.com>
> wrote:
>
> > Val,
> >
> > I've fixed some cases related to this issue.
> > In case you know what is left please describe it at issue and assign to
> me
> >
> > On Tue, Feb 2, 2016 at 9:20 PM, Valentin Kulichenko <
> > valentin.kuliche...@gmail.com> wrote:
> >
> > > Anton,
> > >
> > > If you're working in this issue, can you please assign it to yourself?
> > >
> > > -Val
> > >
> > > -- Forwarded message --
> > > From: Anton Vinogradov (JIRA) <j...@apache.org>
> > > Date: Tue, Feb 2, 2016 at 4:43 AM
> > > Subject: [jira] [Commented] (IGNITE-1523) Need to always serialize user
> > > objects with configured marshaller
> > > To: valentin.kuliche...@gmail.com
> > >
> > >
> > >
> > > [
> > >
> > >
> >
> https://issues.apache.org/jira/browse/IGNITE-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15128185#comment-15128185
> > > ]
> > >
> > > Anton Vinogradov commented on IGNITE-1523:
> > > --
> > >
> > > Fixed unmarshalling of Enum
> > > Fixed unmarshalling of CacheStoreFactory within CacheConfiguration
> > > All new checks added to GridCacheReplicatedPreloadSelfTest
> > >
> > > > Need to always serialize user objects with configured marshaller
> > > > 
> > > >
> > > > Key: IGNITE-1523
> > > > URL:
> https://issues.apache.org/jira/browse/IGNITE-1523
> > > > Project: Ignite
> > > >  Issue Type: Improvement
> > > >  Components: general
> > > >Reporter: Valentin Kulichenko
> > > >Assignee: Valentin Kulichenko
> > > >Priority: Critical
> > > >  Labels: important, user-request
> > > > Fix For: 1.6
> > > >
> > > >
> > > > Currently some components (at least discovery) use {{JdkMarshaller}}
> > for
> > > all objects.
> > >
> > >
> > >
> > > --
> > > This message was sent by Atlassian JIRA
> > > (v6.3.4#6332)
> > >
> >
>

new committer and PMC member: Roman Shtykh

[Anton Vinogradov]

The Project Management Committee (PMC) for Apache Ignite has asked Roman
Shtykh
to become a committer and PMC member and we are pleased to announce
that Roman has accepted.

Being a committer enables easier contribution to the project since there is
no need to go via the patch submission process. This should enable better
productivity. Being a PMC member enables assistance with the management and
to guide the direction of the project.

Re: newbie tickets

[Anton Vinogradov]

Done,

Updated to
https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20labels%20in%20(newbie)%20and%20status%20%3D%20OPEN

On Wed, Feb 24, 2016 at 12:15 PM, Yakov Zhdanov  wrote:

> I think link should be
>
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20labels%20in%20(newbie)
>
> --Yakov
>
> 2016-02-24 12:14 GMT+03:00 Yakov Zhdanov :
>
> > I cleared component field for tickets and added label instead. Anton, can
> > you please change link on the website to search by label?
> >
> > --Yakov
> >
> > 2016-02-24 11:50 GMT+03:00 Dmitriy Setrakyan :
> >
> >> I agree, label makes more sense.
> >>
> >> On Tue, Feb 23, 2016 at 8:55 PM, Valentin Kulichenko <
> >> valentin.kuliche...@gmail.com> wrote:
> >>
> >> > Folks,
> >> >
> >> > I noticed that the 'newbie' filter on site [1] searches issues by
> >> > *component*. But it seems to me that the majority of such tickets are
> >> > marked with a label instead, so contributors don't see them when they
> >> open
> >> > this link.
> >> >
> >> > Is there a policy? For me label makes more sense. 'newbie' is not a
> >> > component.
> >> >
> >> > [1]
> >> >
> >> >
> >>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20component%20in%20(newbie)
> >> >
> >> > -Val
> >> >
> >>
> >
> >
>

Re: Grid behavior at key deserialization failure during rebalancing

[Anton Vinogradov]

Dmitriy,

Key can be undeserializable during rebalancing because of many reasons.
For example,
1) It was serialized with errors
2) Deserialization cause error
3) It based on classes unavailable at node trying to deserialize it
Third is the most possible case.


On Sat, Feb 13, 2016 at 3:44 AM, Dmitriy Setrakyan <dsetrak...@apache.org>
wrote:

> Anton,
>
> I am not sure I fully grok the use case. Can you please explain why a key
> can be broken?
>
> D.
>
> On Fri, Feb 12, 2016 at 7:11 AM, Anton Vinogradov <
> avinogra...@gridgain.com>
> wrote:
>
> > Igniters,
> >
> > At this moment key deserialization failure during rebalancing cause
> strange
> > situation:
> >
> > Rebalancing from node sent supply message with broken key will be
> cancelled
> > at current topology.
> > All upcoming supply messages from this node will be be ignored, no new
> > demand messages to this node will be sent.
> >
> > But when topology will be changed again, node with broken key will take
> > path at rebalancing again, untill key deserialization failure happen ...
> > again.
> >
> > Do we need to improve this situation, and if we have to how should be
> > handled case with key deserialization failure?
> >
> > I see some ways:
> > 1) We can inform user about data loss because of deserialization
> problems,
> > but keep current rebalancing strategy
> > 2) We can continue rebalancing from this node, but ignore messages with
> > broken keys. And inform user about data loss.
> > 3) We can pause rebalancing untill deserialization will be fixed somehow,
> > for example by shutdowning demanding or supplying node.
> >
> > Thoughts?
> >
>

Re: Grid behavior at key deserialization failure during rebalancing

[Anton Vinogradov]

Dmitry,

I found such behavior at GridCacheRebalancingUnmarshallingFailedSelfTest.
Seems we always unmarshalling keys at supply message handling in case of
OptimizeMarshaller used.
Also it happens when BinaryMarshaller used but key class implements
Externalizable.

On Mon, Feb 15, 2016 at 10:43 PM, Dmitriy Setrakyan <dsetrak...@apache.org>
wrote:

> Anton,
>
> I am not sure why we would deserialize on the server side with Binary
> Marshaller. The data should remain in binary form. Do you know if we have a
> test for it?
>
> Thanks,
> D.
>
> On Mon, Feb 15, 2016 at 1:20 AM, Anton Vinogradov <
> avinogra...@gridgain.com>
> wrote:
>
> > Dmitriy,
> >
> > Key can be undeserializable during rebalancing because of many reasons.
> > For example,
> > 1) It was serialized with errors
> > 2) Deserialization cause error
> > 3) It based on classes unavailable at node trying to deserialize it
> > Third is the most possible case.
> >
> >
> > On Sat, Feb 13, 2016 at 3:44 AM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > wrote:
> >
> > > Anton,
> > >
> > > I am not sure I fully grok the use case. Can you please explain why a
> key
> > > can be broken?
> > >
> > > D.
> > >
> > > On Fri, Feb 12, 2016 at 7:11 AM, Anton Vinogradov <
> > > avinogra...@gridgain.com>
> > > wrote:
> > >
> > > > Igniters,
> > > >
> > > > At this moment key deserialization failure during rebalancing cause
> > > strange
> > > > situation:
> > > >
> > > > Rebalancing from node sent supply message with broken key will be
> > > cancelled
> > > > at current topology.
> > > > All upcoming supply messages from this node will be be ignored, no
> new
> > > > demand messages to this node will be sent.
> > > >
> > > > But when topology will be changed again, node with broken key will
> take
> > > > path at rebalancing again, untill key deserialization failure happen
> > ...
> > > > again.
> > > >
> > > > Do we need to improve this situation, and if we have to how should be
> > > > handled case with key deserialization failure?
> > > >
> > > > I see some ways:
> > > > 1) We can inform user about data loss because of deserialization
> > > problems,
> > > > but keep current rebalancing strategy
> > > > 2) We can continue rebalancing from this node, but ignore messages
> with
> > > > broken keys. And inform user about data loss.
> > > > 3) We can pause rebalancing untill deserialization will be fixed
> > somehow,
> > > > for example by shutdowning demanding or supplying node.
> > > >
> > > > Thoughts?
> > > >
> > >
> >
>

Re: Grid behavior at key deserialization failure during rebalancing

[Anton Vinogradov]

Done https://issues.apache.org/jira/browse/IGNITE-2660

On Tue, Feb 16, 2016 at 12:58 PM, Dmitriy Setrakyan <dsetrak...@apache.org>
wrote:

> Anton,
>
> If there is no deserialization for binary marshaller, then I would treat it
> as a low priority issue. We should file a ticket and get to it when it
> becomes more critical.
>
> D.
>
> On Tue, Feb 16, 2016 at 12:37 AM, Anton Vinogradov <
> avinogra...@gridgain.com
> > wrote:
>
> > Dmitry,
> >
> > I found such behavior at GridCacheRebalancingUnmarshallingFailedSelfTest.
> > Seems we always unmarshalling keys at supply message handling in case of
> > OptimizeMarshaller used.
> > Also it happens when BinaryMarshaller used but key class implements
> > Externalizable.
> >
> > On Mon, Feb 15, 2016 at 10:43 PM, Dmitriy Setrakyan <
> dsetrak...@apache.org
> > >
> > wrote:
> >
> > > Anton,
> > >
> > > I am not sure why we would deserialize on the server side with Binary
> > > Marshaller. The data should remain in binary form. Do you know if we
> > have a
> > > test for it?
> > >
> > > Thanks,
> > > D.
> > >
> > > On Mon, Feb 15, 2016 at 1:20 AM, Anton Vinogradov <
> > > avinogra...@gridgain.com>
> > > wrote:
> > >
> > > > Dmitriy,
> > > >
> > > > Key can be undeserializable during rebalancing because of many
> reasons.
> > > > For example,
> > > > 1) It was serialized with errors
> > > > 2) Deserialization cause error
> > > > 3) It based on classes unavailable at node trying to deserialize it
> > > > Third is the most possible case.
> > > >
> > > >
> > > > On Sat, Feb 13, 2016 at 3:44 AM, Dmitriy Setrakyan <
> > > dsetrak...@apache.org>
> > > > wrote:
> > > >
> > > > > Anton,
> > > > >
> > > > > I am not sure I fully grok the use case. Can you please explain
> why a
> > > key
> > > > > can be broken?
> > > > >
> > > > > D.
> > > > >
> > > > > On Fri, Feb 12, 2016 at 7:11 AM, Anton Vinogradov <
> > > > > avinogra...@gridgain.com>
> > > > > wrote:
> > > > >
> > > > > > Igniters,
> > > > > >
> > > > > > At this moment key deserialization failure during rebalancing
> cause
> > > > > strange
> > > > > > situation:
> > > > > >
> > > > > > Rebalancing from node sent supply message with broken key will be
> > > > > cancelled
> > > > > > at current topology.
> > > > > > All upcoming supply messages from this node will be be ignored,
> no
> > > new
> > > > > > demand messages to this node will be sent.
> > > > > >
> > > > > > But when topology will be changed again, node with broken key
> will
> > > take
> > > > > > path at rebalancing again, untill key deserialization failure
> > happen
> > > > ...
> > > > > > again.
> > > > > >
> > > > > > Do we need to improve this situation, and if we have to how
> should
> > be
> > > > > > handled case with key deserialization failure?
> > > > > >
> > > > > > I see some ways:
> > > > > > 1) We can inform user about data loss because of deserialization
> > > > > problems,
> > > > > > but keep current rebalancing strategy
> > > > > > 2) We can continue rebalancing from this node, but ignore
> messages
> > > with
> > > > > > broken keys. And inform user about data loss.
> > > > > > 3) We can pause rebalancing untill deserialization will be fixed
> > > > somehow,
> > > > > > for example by shutdowning demanding or supplying node.
> > > > > >
> > > > > > Thoughts?
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: Semaphore blocking on tryAcquire() while holding a cache-lock

[Anton Vinogradov]

I've populated FAQ
https://cwiki.apache.org/confluence/display/IGNITE/FAQ

On Fri, Mar 11, 2016 at 9:58 PM, Dmitriy Setrakyan <dsetrak...@apache.org>
wrote:

> On Fri, Mar 11, 2016 at 10:20 AM, Christos Erotocritou <
> chris...@gridgain.com> wrote:
>
> > We already have a basic FAQ page which I am populating:
> > http://apacheignite.gridgain.org/docs/faq <
> > http://apacheignite.gridgain.org/docs/faq>
> >
> > Please feel free to add to it.
> >
>
> Thanks Christos! Here is the correct link (your link is just an alias):
> https://apacheignite.readme.io/docs/faq
>
> I think we should add a TOC up top as well, whenever you are done.
>
>
> > Not sure if we want to migrate this to the wiki?
> >
>
> I don’t think we need to.
>
>
> >
> > Christos
> >
> > > On 11 Mar 2016, at 17:35, Dmitriy Setrakyan <dsetrak...@apache.org>
> > wrote:
> > >
> > > +1 on FAQ
> > >
> > > Can we just create a page, and start populating it?
> > >
> > > D.
> > >
> > > On Fri, Mar 11, 2016 at 3:25 AM, Anton Vinogradov <
> > avinogra...@gridgain.com>
> > > wrote:
> > >
> > >> Yakov,
> > >>
> > >> I've answered.
> > >> Seems we have to have special FAQ section at Ignite wiki to publish
> same
> > >> things.
> > >>
> > >> On Sun, Mar 6, 2016 at 12:21 PM, Yakov Zhdanov <yzhda...@apache.org>
> > >> wrote:
> > >>
> > >>> Vlad and all (esp Val and Anton V.),
> > >>>
> > >>> I reviewed the PR. My comments are in the ticket.
> > >>>
> > >>> Anton V. there is a question regarding
> optimized-classnames.properties.
> > >>> Can you please respond in ticket?
> > >>>
> > >>>
> > >>> --Yakov
> > >>>
> > >>> 2016-02-29 16:00 GMT+06:00 Yakov Zhdanov <yzhda...@apache.org>:
> > >>>
> > >>>> Vlad, that's great! I will take a look this week. Reassigning ticket
> > to
> > >>>> myself.
> > >>>>
> > >>>> --Yakov
> > >>>>
> > >>>> 2016-02-26 18:37 GMT+03:00 Vladisav Jelisavcic <vladis...@gmail.com
> >:
> > >>>>
> > >>>>> Hi,
> > >>>>>
> > >>>>> i recently implemented distributed ReentrantLock - IGNITE-642,
> > >>>>> i made a pull request, so hopefully this could be added to the next
> > >>>>> release.
> > >>>>>
> > >>>>> Best regards,
> > >>>>> Vladisav
> > >>>>>
> > >>>>> On Thu, Feb 18, 2016 at 10:49 AM, Alexey Goncharuk <
> > >>>>> alexey.goncha...@gmail.com> wrote:
> > >>>>>
> > >>>>>> Folks,
> > >>>>>>
> > >>>>>> The current implementation of IgniteCache.lock(key).lock() has the
> > >>>>> same
> > >>>>>> semantics as the transactional locks - cache topology cannot be
> > >>>>> changed
> > >>>>>> while there exists an ongoing transaction or an explicit lock is
> > >>>>> held. The
> > >>>>>> restriction for transactions is quite fundamental, the lock()
> issue
> > >>>>> can be
> > >>>>>> fixed if we re-implement locking the same way IgniteSemaphore
> > >>>>> currently
> > >>>>>> works.
> > >>>>>>
> > >>>>>> As for the "Failed to find semaphore with the given name" message,
> > my
> > >>>>> first
> > >>>>>> guess is that DataStructures were configured with 1 backups which
> > led
> > >>>>> to
> > >>>>>> the data loss when two nodes were stopped. Mario, can you please
> > >>>>> re-test
> > >>>>>> your semaphore scenario with 2 backups configured for data
> > structures?
> > >>>>>> From my side, I can also take a look at the semaphore issue when
> I'm
> > >>>>> done
> > >>>>>> with IGNITE-2610.
> > >>>>>>
> > >>>>>
> > >>>>
> > >>>>
> > >>>
> > >>
> >
> >
>

Re: Semaphore blocking on tryAcquire() while holding a cache-lock

[Anton Vinogradov]

Yakov,

I've answered.
Seems we have to have special FAQ section at Ignite wiki to publish same
things.

On Sun, Mar 6, 2016 at 12:21 PM, Yakov Zhdanov  wrote:

> Vlad and all (esp Val and Anton V.),
>
> I reviewed the PR. My comments are in the ticket.
>
> Anton V. there is a question regarding optimized-classnames.properties.
> Can you please respond in ticket?
>
>
> --Yakov
>
> 2016-02-29 16:00 GMT+06:00 Yakov Zhdanov :
>
>> Vlad, that's great! I will take a look this week. Reassigning ticket to
>> myself.
>>
>> --Yakov
>>
>> 2016-02-26 18:37 GMT+03:00 Vladisav Jelisavcic :
>>
>>> Hi,
>>>
>>> i recently implemented distributed ReentrantLock - IGNITE-642,
>>> i made a pull request, so hopefully this could be added to the next
>>> release.
>>>
>>> Best regards,
>>> Vladisav
>>>
>>> On Thu, Feb 18, 2016 at 10:49 AM, Alexey Goncharuk <
>>> alexey.goncha...@gmail.com> wrote:
>>>
>>> > Folks,
>>> >
>>> > The current implementation of IgniteCache.lock(key).lock() has the same
>>> > semantics as the transactional locks - cache topology cannot be changed
>>> > while there exists an ongoing transaction or an explicit lock is held.
>>> The
>>> > restriction for transactions is quite fundamental, the lock() issue
>>> can be
>>> > fixed if we re-implement locking the same way IgniteSemaphore currently
>>> > works.
>>> >
>>> > As for the "Failed to find semaphore with the given name" message, my
>>> first
>>> > guess is that DataStructures were configured with 1 backups which led
>>> to
>>> > the data loss when two nodes were stopped. Mario, can you please
>>> re-test
>>> > your semaphore scenario with 2 backups configured for data structures?
>>> > From my side, I can also take a look at the semaphore issue when I'm
>>> done
>>> > with IGNITE-2610.
>>> >
>>>
>>
>>
>

Re: Contributions that are waiting for review

[Anton Vinogradov]

Done,

https://cwiki.apache.org/confluence/display/IGNITE/Issues+waiting+for+review

On Thu, Mar 17, 2016 at 3:46 PM, Denis Magda <dma...@gridgain.com> wrote:

> Pavel, Anton,
>
> Can we simply create a page on Apache wiki that will show a result of the
> specific JIRA filter execution? This can be the first improvement we can do
> in this direction.
>
> --
> Denis
>
>
> On 3/4/2016 4:14 PM, Anton Vinogradov wrote:
>
>> Pavel,
>> I think that script should be stored inside TeamCity task.
>>
>>
>>
>> On Fri, Mar 4, 2016 at 3:56 PM, Pavel Tupitsyn <ptupit...@gridgain.com>
>> wrote:
>>
>> Anton, good idea, the script can be stored in git this way. Dmitriy, what
>>> do you think?
>>>
>>> Another question is the email account to send from. Do we have something
>>> suitable already?
>>>
>>>
>>>
>>> On Fri, Mar 4, 2016 at 3:34 PM, Anton Vinogradov <
>>> avinogra...@gridgain.com
>>> wrote:
>>>
>>> Folks,
>>>>
>>>> we can create TeamCity task with special trigger (eg. once a day).
>>>> This task can contains any script.
>>>>
>>>> On Fri, Mar 4, 2016 at 3:18 PM, Pavel Tupitsyn <ptupit...@gridgain.com>
>>>> wrote:
>>>>
>>>> Raul, I'm not good with shell scripts. As a .net person I was thinking
>>>>> about a scheduled C# script on one of our TeamCity win machines, but
>>>>>
>>>> Dmitry
>>>>
>>>>> prefers Jenkins.
>>>>>
>>>>>
>>>>> On Fri, Mar 4, 2016 at 2:52 PM, Raul Kripalani <ra...@apache.org>
>>>>>
>>>> wrote:
>>>
>>>> I believe all we need is a shell script in our source tree that
>>>>>>
>>>>> queries
>>>
>>>> the
>>>>>
>>>>>> JIRA API and produces an output on stdout.
>>>>>>
>>>>>> We can then schedule an overnight job with, e.g. a 0 23 * * * cron
>>>>>> expression, and configure the output to be sent to the ML, as
>>>>>>
>>>>> indicated
>>>
>>>> here: https://wiki.apache.org/general/Jenkins.
>>>>>>
>>>>>> @Pavel, would you like to work on the shell script? I can help you
>>>>>> configure the JKS job.
>>>>>>
>>>>>> @Dmitriy, can you add both Pavel and me as job admins?
>>>>>>
>>>>>>
>>>>>>
>>> https://wiki.apache.org/general/Jenkins?action=show=Hudson#How_do_I_get_an_account
>>>
>>>> Cheers,
>>>>>>
>>>>>>
>

Re: IGNITE-1071 IgniteCache.metrics() method returns local metrics

[Anton Vinogradov]

Do we need local metrics at IgniteCache?

On Thu, Mar 24, 2016 at 3:02 PM, Vladimir Ozerov <voze...@gridgain.com>
wrote:

> + 1 to Anton and Alexey suggestions. Having both local and global MBeans
> should do the trick.
>
> On Thu, Mar 24, 2016 at 2:47 PM, Alexey Kuznetsov <akuznet...@gridgain.com
> >
> wrote:
>
> > Could we have local and global MBeans?
> > Or local and global metrics inside same MBean?
> >
> > On Thu, Mar 24, 2016 at 6:26 PM, Anton Vinogradov <
> > avinogra...@gridgain.com>
> > wrote:
> >
> > > Hello,
> > >
> > > I'd like to discuss
> > > IGNITE-1071 IgniteCache.metrics() method returns local metrics
> > > <https://issues.apache.org/jira/browse/IGNITE-1071>
> > >
> > > I agree to make IgniteCache.metrics() global but want to keep MBeans
> > local.
> > >
> > > According to specification:
> > > An MBean can represent a device, an application, or any resource that
> > needs
> > > to be managed.
> > > So, I think it's a good point that MBean represents node instead of
> > > cluster.
> > >
> > > I case we will make MBeans global (representing whole cluster) we have
> no
> > > chances to see metrics of specific node which can be interesting for
> some
> > > reasons.
> > > For example - per node cachePuts metric can show is there any problems
> > with
> > > affinity function or hashCode collisions.
> > >
> > > Val, Semen, could you please explain reasons of MBeans refactoring?
> > > We will loose api to gain per node metrics in this case.
> > >
> > > Thoughts?
> > >
> >
> >
> >
> > --
> > Alexey Kuznetsov
> > GridGain Systems
> > www.gridgain.com
> >
>

IGNITE-1071 IgniteCache.metrics() method returns local metrics

[Anton Vinogradov]

Hello,

I'd like to discuss
IGNITE-1071 IgniteCache.metrics() method returns local metrics


I agree to make IgniteCache.metrics() global but want to keep MBeans local.

According to specification:
An MBean can represent a device, an application, or any resource that needs
to be managed.
So, I think it's a good point that MBean represents node instead of cluster.

I case we will make MBeans global (representing whole cluster) we have no
chances to see metrics of specific node which can be interesting for some
reasons.
For example - per node cachePuts metric can show is there any problems with
affinity function or hashCode collisions.

Val, Semen, could you please explain reasons of MBeans refactoring?
We will loose api to gain per node metrics in this case.

Thoughts?

Re: github replication of Ignite

[Anton Vinogradov]

Roman,

thanks for pointing this, I've created infra issue

https://issues.apache.org/jira/browse/INFRA-11534

On Thu, Mar 24, 2016 at 8:53 AM, Roman Shtykh 
wrote:

> Hi Anton,
>
> I have pushed two changes to the master this morning and see no
> replication to github. Is it normal?
>
> It seems you take care of CI of the project, so I decided to ask you
> directly.
>
> Best regards,
> Roman
>
>

Re: github replication of Ignite

[Anton Vinogradov]

Replication fixed.

On Thu, Mar 24, 2016 at 11:04 AM, Anton Vinogradov <a...@apache.org> wrote:

> Roman,
>
> thanks for pointing this, I've created infra issue
>
> https://issues.apache.org/jira/browse/INFRA-11534
>
> On Thu, Mar 24, 2016 at 8:53 AM, Roman Shtykh <roman.sht...@gmail.com>
> wrote:
>
>> Hi Anton,
>>
>> I have pushed two changes to the master this morning and see no
>> replication to github. Is it normal?
>>
>> It seems you take care of CI of the project, so I decided to ask you
>> directly.
>>
>> Best regards,
>> Roman
>>
>>
>

Re: Contributions that are waiting for review

[Anton Vinogradov]

Folks,

we can create TeamCity task with special trigger (eg. once a day).
This task can contains any script.

On Fri, Mar 4, 2016 at 3:18 PM, Pavel Tupitsyn 
wrote:

> Raul, I'm not good with shell scripts. As a .net person I was thinking
> about a scheduled C# script on one of our TeamCity win machines, but Dmitry
> prefers Jenkins.
>
>
> On Fri, Mar 4, 2016 at 2:52 PM, Raul Kripalani  wrote:
>
> > I believe all we need is a shell script in our source tree that queries
> the
> > JIRA API and produces an output on stdout.
> >
> > We can then schedule an overnight job with, e.g. a 0 23 * * * cron
> > expression, and configure the output to be sent to the ML, as indicated
> > here: https://wiki.apache.org/general/Jenkins.
> >
> > @Pavel, would you like to work on the shell script? I can help you
> > configure the JKS job.
> >
> > @Dmitriy, can you add both Pavel and me as job admins?
> >
> >
> https://wiki.apache.org/general/Jenkins?action=show=Hudson#How_do_I_get_an_account
> >
> > Cheers,
> >
>

Re: Contributions that are waiting for review

[Anton Vinogradov]

Pavel,
I think that script should be stored inside TeamCity task.



On Fri, Mar 4, 2016 at 3:56 PM, Pavel Tupitsyn <ptupit...@gridgain.com>
wrote:

> Anton, good idea, the script can be stored in git this way. Dmitriy, what
> do you think?
>
> Another question is the email account to send from. Do we have something
> suitable already?
>
>
>
> On Fri, Mar 4, 2016 at 3:34 PM, Anton Vinogradov <avinogra...@gridgain.com
> >
> wrote:
>
> > Folks,
> >
> > we can create TeamCity task with special trigger (eg. once a day).
> > This task can contains any script.
> >
> > On Fri, Mar 4, 2016 at 3:18 PM, Pavel Tupitsyn <ptupit...@gridgain.com>
> > wrote:
> >
> > > Raul, I'm not good with shell scripts. As a .net person I was thinking
> > > about a scheduled C# script on one of our TeamCity win machines, but
> > Dmitry
> > > prefers Jenkins.
> > >
> > >
> > > On Fri, Mar 4, 2016 at 2:52 PM, Raul Kripalani <ra...@apache.org>
> wrote:
> > >
> > > > I believe all we need is a shell script in our source tree that
> queries
> > > the
> > > > JIRA API and produces an output on stdout.
> > > >
> > > > We can then schedule an overnight job with, e.g. a 0 23 * * * cron
> > > > expression, and configure the output to be sent to the ML, as
> indicated
> > > > here: https://wiki.apache.org/general/Jenkins.
> > > >
> > > > @Pavel, would you like to work on the shell script? I can help you
> > > > configure the JKS job.
> > > >
> > > > @Dmitriy, can you add both Pavel and me as job admins?
> > > >
> > > >
> > >
> >
> https://wiki.apache.org/general/Jenkins?action=show=Hudson#How_do_I_get_an_account
> > > >
> > > > Cheers,
> > > >
> > >
> >
>

Re: IGNITE-2693 - could someone take a look and help me with a quick review

[Anton Vinogradov]

Hello,

commented at issue

On Thu, Mar 3, 2016 at 5:28 PM, Dood@ODDO  wrote:

> Hello,
>
> This is my second Ignite ticket and if I understand correctly, it is a
> simple fix - I submitted a patch recently, it is only a few lines. Can
> someone take a look and see if I am on the right track or did I completely
> misunderstand it... :-)
>
> Thanks!
>

Re: Switching back to review-then-commit process

[Anton Vinogradov]

+1 (but I hope it's still up to a committer to decide whether a change
should need a review or not.)

On Thu, Mar 3, 2016 at 8:09 PM, Dmitriy Setrakyan 
wrote:

> I hate to be religious about anything, but do think that for most of the
> functionality, RTC makes sense.
>
> On Thu, Mar 3, 2016 at 7:20 AM, Raul Kripalani  wrote:
>
> > I thought we were already on RTC process.
> >
> > What do you mean with contributors following this process?
> >
> > Raúl.
> > On 3 Mar 2016 11:54, "Denis Magda"  wrote:
> >
> > > Igniters,
> > >
> > > I would propose to switch back to review-then-commit process. This
> > process
> > > has to be followed by both contributors and committers.
> > >
> > > There is a reason for this I have in mind. Ignite is a complex platform
> > > with several big modules. Some of the people may be experts in module A
> > > while others in module B etc.
> > > If a committer, who is good in module A, makes changes in module B
> > merging
> > > the changes without a review this can break module's B internal
> > > functionality that the committer didn't take into account.
> > >
> > > My proposal is to introduce a list of maintainers for every Ignite
> module
> > > like it's done in Spark [1] and a rule that will require a committer to
> > get
> > > an approval from a module maintainer before merging changes.
> > >
> > > Thoughts?
> > >
> > > --
> > > Denis
> > >
> > > [1]
> > >
> >
> https://cwiki.apache.org/confluence/display/SPARK/Committers#Committers-ReviewProcessandMaintainers
> > >
> > >
> > >
> >
>

Re: Contributions that are waiting for review

[Anton Vinogradov]

Denis,

We have a special status at Ignite JIRA - PATCH AVAILABLE which means that
issue ready to be reviewed.
Currently 59 issues has such status according to
https://issues.apache.org/jira/issues/?filter=-2=project%20%3D%20Ignite%20and%20status%20%3D%20%22Patch%20Available%22

I think we have to add notes that this status can be used only during
waiting of review and we will have no problems with actual "required
review" list in future.


On Wed, Mar 2, 2016 at 4:08 PM, Roman Shtykh 
wrote:

> I have also asked for review of the following tickets but failed to get a
> feedback.
> They are not complicated, but I would appreciate a quick review. Thank you!
>
> [IGNITE-2563] Queries: ArrayIndexOutOfBoundsException when using BOOL_AND
>
> https://issues.apache.org/jira/browse/IGNITE-2563
>
> IGNITE-2416 TcpDiscoverySharedFsIpFinder doesn't work with IPv6 addresses
> https://issues.apache.org/jira/browse/IGNITE-2416
>
> and a new one
>
> IGNITE-2710 Session not unbind from current request after invoking
> request.getSession().invalidate()
> https://issues.apache.org/jira/browse/IGNITE-2710
>
> -Roman
>
>
> On Wednesday, March 2, 2016 6:38 PM, Denis Magda 
> wrote:
>
>
>
> Ignite committers,
>
> There is a number of contributions that have to be reviewed.
>
> Please pick them up basing on your experience and provide your review
> notes.
>
> Ignite 2718: Missing ZookeeperIpFinder dependencies
> 
> IGNITE-2693: withKeepBinary and non-binary marshallers
> 
> IGNITE-2735: Fixes distributed semaphore local node stopping issue.
> 
> *IGNITE-642: Implements cache distributed reentrant lock
> 
>
>
> *Regards,
> Denis
>

Re: [VOTE] Apache Ignite 1.6.0 RC1

[Anton Vinogradov]

+1 (binding)

On Fri, May 20, 2016 at 12:16 AM, Vladimir Ozerov <voze...@gridgain.com>
wrote:

> Looks good to me.
>
> +1 (binding)
>
> On Thu, May 19, 2016 at 10:11 PM, Denis Magda <dma...@gridgain.com> wrote:
>
> > +1
> >
> > > On Wed, May 18, 2016 at 5:24 PM, Anton Vinogradov <a...@apache.org>
> wrote:
> > >
> > >> Dear Sirs!
> > >>
> > >> We have uploaded release candidate to
> > >> https://dist.apache.org/repos/dist/dev/ignite/1.6.0-rc1/
> > >>
> > >> This is very important release containing huge amount of fixes and
> > >> improvements.
> > >> Over 600 issues were closed since previous release.
> > >> 8 new modules were added to the project.
> > >>
> > >> Tag name is
> > >> 1.6.0-rc1
> > >>
> > >> 1.6.0 changes:
> > >> Ignite .NET:
> > >> * Added ability to use Java-based remote filters in continuous
> queries.
> > >> * Added AtomicSequence and AtomicReference data structures
> > >> * Added automatic Java detection: no need for JAVA_HOME
> > >> * Added java-based continuous query filters
> > >> * Added LINQ Provider for cache SQL queries
> > >> * Added native configuration mechanism (C#, app.config, web.config -
> > >> instead of Spring XML)
> > >> * Added NuGet distribution
> > >> * Binaries are now AnyCPU (instead of separate x64/x86)
> > >> * Java-based services can be called the same way as .NET service are
> > called
> > >>
> > >> Ignite C++:
> > >> * Added Transactions API for C++ client.
> > >> * Added Date and Timestamp types implementation for C++ client.
> > >> * Simplified Autotools build process for C++ client.
> > >>
> > >> Ignite:
> > >> * Added ability to get partition 'updateCntr' with continuous query
> > public
> > >> API.
> > >> * Added asynchronous execution of ContinuousQuery's remote filter and
> > local
> > >> listener.
> > >> * Added backup partitions storing to local store default behavior.
> > >> * Added cache deadlock detection.
> > >> * Added Cache Store implementation backed by Cassandra DB.
> > >> * Added method to get versioned cache entry.
> > >> * Added ODBC driver for Ignite.
> > >> * Added support for join timeout while registering local addresses
> with
> > IP
> > >> finder in TcpDiscoverySpi.
> > >> * Added support for JTA transactions via synchronization callback.
> > >> * Added Web Console for Ignite.
> > >> * Fixed a bug causing object deserialization when local store is
> > configured
> > >> for cache.
> > >> * Fixed a problem with incorrect classloader picked in OSGI
> environment.
> > >> * Fixed a race condition when evicted offheap data was not delivered
> to
> > >> query engine leading to query timeout.
> > >> * Fixed an issue in ContinuousQueries that caused missing of
> > 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 marsh

Re: [RESULT] [VOTE] Apache Ignite 1.6.0 Release (RC1)

[Anton Vinogradov]

Ignite 1.6.0 successfuly released to
https://dist.apache.org/repos/dist/release/ignite/1.6.0/
Maven repository and site also updated.

On Sat, May 21, 2016 at 6:47 PM, Anton Vinogradov <a...@apache.org> wrote:

> Hello!
>
> Apache Ignite 1.6.0 release (RC1) has been accepted.
>
> 9 "+1" votes received.
>
> Here are the votes received:
>
> - Sergi Vladykin (binding)
> - Semyon Boikov (binding)
> - Denis Magda (binding)
> - Vladimir Ozerov (binding)
> - Anton Vinogradov (binding)
> - Nikolay Tikhonov (binding)
> - Valentin Kulichenko (binding)
> - Gianfranco Murador (binding)
> - Alexey Kuznetsov
>
> Here is the link to vote thread -
>
> http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-1-6-0-RC1-td8992.html
>
> Ignite 1.6.0 will be released soon.
>
> Thanks!
>

[RESULT] [VOTE] Apache Ignite 1.6.0 Release (RC1)

[Anton Vinogradov]

Hello!

Apache Ignite 1.6.0 release (RC1) has been accepted.

9 "+1" votes received.

Here are the votes received:

- Sergi Vladykin (binding)
- Semyon Boikov (binding)
- Denis Magda (binding)
- Vladimir Ozerov (binding)
- Anton Vinogradov (binding)
- Nikolay Tikhonov (binding)
- Valentin Kulichenko (binding)
- Gianfranco Murador (binding)
- Alexey Kuznetsov

Here is the link to vote thread -
http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-1-6-0-RC1-td8992.html

Ignite 1.6.0 will be released soon.

Thanks!

Re: Halfway to Ignite 1.6

[Anton Vinogradov]

Thanks everyone for checking!

Only 8 tickets left!

Seems contributors still need 1-2 days to pass codereview and merge final
changes.
We postponed code freeze till Wednesday UTC 19-00. Hope, this will be the
last time.

On Mon, May 16, 2016 at 3:56 PM, Anton Vinogradov <avinogra...@gridgain.com>
wrote:

> Igniters,
>
> We still have 32 issues with status "In Progress" or "Patch Available" and
> fixVersion = 1.6.
> Full list
> <https://issues.apache.org/jira/issues/?filter=-1=(status%20%3D%20%22In%20Progress%22%20or%20status%20%3D%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%201.6%20and%20project%20%3D%20Ignite>
>  can
> be found here.
>
> Please change fixVersion for issues can't be resolved at 1.6 to 1.7, and
> close other issues before code freeze.
>
> On Mon, May 16, 2016 at 12:57 AM, Andrey Gura <ag...@gridgain.com> wrote:
>
>> Guys,
>>
>> I've finished with improvements for JDBC drivers [1]. I hope somebody will
>> review and merge it before code freeze.
>> Also I created issue related with query execution from client nodes [2].
>> It
>> affects system behaviour that related with [1] and [3]. I don't think that
>> it is critical because walk around exists.
>>
>> [1] https://issues.apache.org/jira/browse/IGNITE-2382
>> [2] https://issues.apache.org/jira/browse/IGNITE-3136
>> [3] https://issues.apache.org/jira/browse/IGNITE-2455
>>
>> On Fri, May 13, 2016 at 6:24 PM, Anton Vinogradov <a...@apache.org> wrote:
>>
>> > Igniters,
>> >
>> > We postponed code freeze till monday UTC 19-00.
>> >
>> > On Thu, May 12, 2016 at 1:48 PM, Anton Vinogradov <a...@apache.org>
>> wrote:
>> >
>> > > Typo fix:
>> > > Pushes to ignite-1.6 are allowed till Friday (*May *13) 19:00 UTC.
>> > >
>> > >
>> > >
>> > > On Thu, May 12, 2016 at 1:41 PM, Anton Vinogradov <a...@apache.org>
>> wrote:
>> > >
>> > >> Igniters,
>> > >>
>> > >> Ignite 1.6 almost ready to be finally tested.
>> > >>
>> > >> Branch ignite-1.6 now contains all changes scheduled for 1.6.
>> > >>
>> > >> In case you want to add something else to this release, please note
>> that
>> > >> pushes to ignite-1.6 allowed till Friday (Aug 13) 19:00 UTC.
>> > >> After that date only fixes will allowed.
>> > >>
>> > >> On Fri, May 6, 2016 at 4:18 PM, Anton Vinogradov <a...@apache.org>
>> wrote:
>> > >>
>> > >>> Igniters,
>> > >>>
>> > >>> We're going to release Ignite 1.6 in the nearest future.
>> > >>> Branch ignite-1.6 was created and already contains changes scheduled
>> > for
>> > >>> 1.6.
>> > >>>
>> > >>> And from now on, I propose to start testing and fixing ignite-1.6
>> > source
>> > >>> code to provide stable release.
>> > >>>
>> > >>> As you know we have a huge amount of tests and some of them now
>> failing
>> > >>> at release branch.
>> > >>> Fails can be found here:
>> > >>>
>> > >>>
>> >
>> http://149.202.210.143:8111/project.html?projectId=IgniteTests=projectOverview_IgniteTests=ignite-1.6
>> > >>>
>> > >>> So, feel free to start investigations and fix issues :)
>> > >>>
>> > >>
>> > >>
>> > >
>> >
>>
>>
>>
>> --
>> Andrey Gura
>> GridGain Systems, Inc.
>> www.gridgain.com
>>
>
>

Re: Code merge in 1.6 branch at 16-th

[Anton Vinogradov]

Seems we postpone code freeze till monday UTC 19-00.
So, feel free to merge changes on Monday

On Fri, May 13, 2016 at 6:19 PM, Alexey Kuznetsov 
wrote:

> I also have whole feature (web-console) not merged yet to ignite-1.6. Also
> need some review before merge.
>
>
>
> On Fri, May 13, 2016 at 10:13 PM, Dmitry Karachentsev <
> dkarachent...@gridgain.com> wrote:
>
> > Anton V., is it still be possible to merge changes to 1.6 branch at
> Monday
> > 16-th? I have a fix that waiting for review and it would be nice to add
> it
> > in that release (IGNITE-3087 <
> > https://issues.apache.org/jira/browse/IGNITE-3087>).
> >
> > Thanks!
> > Dmitry.
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>

Re: Halfway to Ignite 1.6

[Anton Vinogradov]

Igniters,

We postponed code freeze till monday UTC 19-00.

On Thu, May 12, 2016 at 1:48 PM, Anton Vinogradov <a...@apache.org> wrote:

> Typo fix:
> Pushes to ignite-1.6 are allowed till Friday (*May *13) 19:00 UTC.
>
>
>
> On Thu, May 12, 2016 at 1:41 PM, Anton Vinogradov <a...@apache.org> wrote:
>
>> Igniters,
>>
>> Ignite 1.6 almost ready to be finally tested.
>>
>> Branch ignite-1.6 now contains all changes scheduled for 1.6.
>>
>> In case you want to add something else to this release, please note that
>> pushes to ignite-1.6 allowed till Friday (Aug 13) 19:00 UTC.
>> After that date only fixes will allowed.
>>
>> On Fri, May 6, 2016 at 4:18 PM, Anton Vinogradov <a...@apache.org> wrote:
>>
>>> Igniters,
>>>
>>> We're going to release Ignite 1.6 in the nearest future.
>>> Branch ignite-1.6 was created and already contains changes scheduled for
>>> 1.6.
>>>
>>> And from now on, I propose to start testing and fixing ignite-1.6 source
>>> code to provide stable release.
>>>
>>> As you know we have a huge amount of tests and some of them now failing
>>> at release branch.
>>> Fails can be found here:
>>>
>>> http://149.202.210.143:8111/project.html?projectId=IgniteTests=projectOverview_IgniteTests=ignite-1.6
>>>
>>> So, feel free to start investigations and fix issues :)
>>>
>>
>>
>