[GitHub] ignite pull request: IGNITE-2954 - Added tests for various read-th...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/634


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Integration with Apache Apex

[Thomas Weise]

Dear Ignite community,

Apache Apex is a data in-motion processing platform. It was developed since
2012 and recently became an ASF top level project:

http://apex.apache.org/docs.html

The Apex engine can process large scale, high throughput streams with very
low latency. It is a stateful system with strong processing guarantees. A
unique feature of Apex is the ability to recover from failures without
resetting the entire topology and also the ability to scale or change the
application dynamically. Apex also has a large library of connectors,
supporting integration with many well known projects in the wider big data
ecosystem out of the box.

It would be great to add Ignite to the list. I think Apex as processing
engine and Ignite as storage layer would be a very powerful combination.
Here are some use cases for such integration:

   - Connectors to read from Ignite or land data in Ignite (
   https://issues.apache.org/jira/browse/IGNITE-3131)
   - Checkpointing backend (alternative implementation for Apex
   StorageAgent)
   - Backend for operator specific state management

It would be great if someone in Ignite community wants to take this up and
collaborate. There is also a ticket in the Apex JIRA to track this:
https://issues.apache.org/jira/browse/APEXMALHAR-2091

Thanks,
Thomas

[jira] [Created] (IGNITE-3131) Connectors for Apache Apex

[Dmitriy Setrakyan (JIRA)]

Dmitriy Setrakyan created IGNITE-3131:
-

 Summary: Connectors for Apache Apex
 Key: IGNITE-3131
 URL: https://issues.apache.org/jira/browse/IGNITE-3131
 Project: Ignite
  Issue Type: Improvement
Reporter: Dmitriy Setrakyan


Apache Apex is a unified stream and batch processing platform: 

http://apex.apache.org/
http://apex.apache.org/docs.html

Apex has a large library of connectors for integration with many other 
ecosystem projects. It would be great to have support for Ignite. Here are some 
examples:

https://github.com/apache/incubator-apex-malhar/tree/master/contrib/src/main/java/com/datatorrent/contrib/geode
https://github.com/apache/incubator-apex-malhar/tree/master/contrib/src/main/java/com/datatorrent/contrib/cassandra
https://github.com/apache/incubator-apex-malhar/tree/master/contrib/src/main/java/com/datatorrent/contrib/nifi

The logical place for the implementation would the the Malhar repository, but 
approach and development should be driven by the Ignite community. 




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Introduction and Contribution Help

[Dmitriy Setrakyan]

Hi Myles,

Welcome to the Ignite community!

How about this ticket? Looks like it could be a good entry point one:
https://issues.apache.org/jira/browse/IGNITE-1794

D.

On Wed, May 11, 2016 at 6:58 AM, Myles Baker 
wrote:

> Hi all,
>
> I just wanted to introduce myself - I am interested in Ignite and have
> been lurking for a while. I’ve been working in high performance computing
> for my entire career, starting at NASA followed by working at software
> companies and providing consulting services. I deal with data problems
> daily and appreciate data grids for scalability and performance challenges.
>
> So, the next step for my interest in Ignite is to start contributing to
> the project and understanding it at a deeper level technically. I’ve been
> following the   https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Workflow>instructions
> for contributing  https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Workflow>,
> but I'm having trouble finding a good entry point for me to start
> contributing. I found a few newbie tickets that might be a good place to
> start: IGNITE-2049 
> and IGNITE-2895 .
> However, these either use specific systems that I can’t test or reference
> the EA process, which I’m unfamiliar with.
>
> Any opinions? Other tickets that might be a better entry point for someone
> who has programmed in the JVM before?
>
> Thanks,
> Myles
>
>

Re: visorcmd alerts: improvements and fixes

[Dmitriy Setrakyan]

Thanks Vasily! The custom alert logic is a great addition. Do we need to
add documentation for it?

On Thu, May 12, 2016 at 2:30 AM, Vasiliy Sisko  wrote:

> Hello Igniters.
>
> I implement execution of custom script on alert for visorcmd:
> https://issues.apache.org/jira/browse/IGNITE-2919. Now some logic can be
> defined in case of specific grid conditions in format sh/bat file.
>
> Also fixed reaction on alert condition switch:
> https://issues.apache.org/jira/browse/IGNITE-2930.
>
>
> --
> Vasiliy Sisko
> GridGain Systems
> www.gridgain.com
>

Re: IGNITE-1192 in progress

[Juan Carlos Fiorenzano]

don't worry I'm going to share every advance with the community

On Thu, May 12, 2016 at 10:51 PM, Dmitriy Setrakyan 
wrote:

> Thanks Juan.
>
> I am not a Spring Data expert, but would be curious to see what you can dig
> out, if you don’t mind sharing your findings here.
>
> D.
>
> On Thu, May 12, 2016 at 7:48 PM, Juan Carlos Fiorenzano <
> jcfiorenzan...@gmail.com> wrote:
>
> > Hello everybody, I have assigned to me the issue IGNITE-1192, this issues
> > is about the integration about Ignite and Spring Data, I am going to
> begin
> > to research how do that, so any advice or idea will be welcome. Thanks in
> > advance
> >
>

Re: IGNITE-1192 in progress

[Dmitriy Setrakyan]

Thanks Juan.

I am not a Spring Data expert, but would be curious to see what you can dig
out, if you don’t mind sharing your findings here.

D.

On Thu, May 12, 2016 at 7:48 PM, Juan Carlos Fiorenzano <
jcfiorenzan...@gmail.com> wrote:

> Hello everybody, I have assigned to me the issue IGNITE-1192, this issues
> is about the integration about Ignite and Spring Data, I am going to begin
> to research how do that, so any advice or idea will be welcome. Thanks in
> advance
>

IGNITE-1192 in progress

[Juan Carlos Fiorenzano]

Hello everybody, I have assigned to me the issue IGNITE-1192, this issues
is about the integration about Ignite and Spring Data, I am going to begin
to research how do that, so any advice or idea will be welcome. Thanks in
advance

Re: Ignite 1.6 release timelines

[Dmitriy Setrakyan]

On Thu, May 12, 2016 at 9:08 AM, Alexey Kuznetsov 
wrote:

> Also I already implemented "CacheJdbcPojoStoreFactory.dataSource property
> should be replaced with Factory"
> https://issues.apache.org/jira/browse/IGNITE-2832
>
> And I think it will be cool to merge into ignite-1.6
> But I need a review.
>
> Val, could you take a look? You may compare branch ignite-2832 with master.
>

To my knowledge, Val is traveling this weekend, so it would be nice if
someone else could pick it up.


>
> On Thu, May 12, 2016 at 10:26 PM, Alexey Kuznetsov <
> akuznet...@gridgain.com>
> wrote:
>
> > I'm going to merge Ignite Web Console into ignite-1.6
> >
> > https://issues.apache.org/jira/browse/IGNITE-843
> >
> > On Thu, May 12, 2016 at 9:30 PM, Igor Sapego 
> wrote:
> >
> >> There is one more C++ ticket I'd like to be included in 1.6 -
> IGNITE-3113
> >> [1].
> >>
> >> [1] - https://issues.apache.org/jira/browse/IGNITE-3113
> >>
> >> Best Regards,
> >> Igor
> >>
> >> On Thu, May 12, 2016 at 3:44 PM, Pavel Tupitsyn  >
> >> wrote:
> >>
> >> > And one more .NET ticket: IGNITE-3118 .NET:
> >> > CacheConfiguration.EvictionPolicy
> >> >
> >> > On Thu, May 12, 2016 at 12:20 PM, Denis Magda 
> >> wrote:
> >> >
> >> > > Yakov,
> >> > >
> >> > > Processed all the tickets mentioned in 1. The only one is left is
> the
> >> > > following
> >> > > https://issues.apache.org/jira/browse/IGNITE-2954 <
> >> > > https://issues.apache.org/jira/browse/IGNITE-2954>
> >> > >
> >> > > Alex G. I do remember you’ve fixed IGNITE-2954 before. Have you
> >> merged it
> >> > > into the master? Is the fix in ignite-1.6 already?
> >> > >
> >> > > —
> >> > > Denis
> >> > >
> >> > > > On May 11, 2016, at 8:56 AM, Yakov Zhdanov 
> >> > wrote:
> >> > > >
> >> > > > Guys,
> >> > > >
> >> > > > I moved most of the tickets to 1.7 version.
> >> > > >
> >> > > > I had to leave the following tickets untouched (~80 tickets):
> >> > > > 1. labeled with - community important performance customer -
> Denis,
> >> > > > Vladimir and Val can you please review these tickets and move
> >> > non-urgent
> >> > > > ones. You can use query below
> >> > > > 2. with status "in progress". Please everyone having such tickets
> >> move
> >> > it
> >> > > > yourself or finish it in 1.6
> >> > > > 3. with status "patch available". Committers, please split the
> >> reviews
> >> > > and
> >> > > > let's include checked/tested fixes to 1.6. Others should be moved.
> >> > > >
> >> > > > Sam, can you please review and merge -
> >> > > > https://issues.apache.org/jira/browse/IGNITE-2744 - Optimize
> >> > > "unwindEvict"
> >> > > > call in GridCacheIoManager.processMessage().
> >> > > > 
> >> > > >
> >> > > > Query for p1:
> >> > > >
> >> > > > project = IGNITE AND fixVersion = 1.6 AND resolution = Unresolved
> >> AND
> >> > > > status not in ("Patch Available", "in progress") AND (labels in
> >> > > (community,
> >> > > > important, performance, perfomance, customer)) ORDER BY status
> DESC,
> >> > due
> >> > > > ASC, priority DESC, created ASC
> >> > > >
> >> > > > Thanks!
> >> > > >
> >> > > > --Yakov
> >> > > >
> >> > > > 2016-05-11 9:47 GMT+06:00 Dmitriy Setrakyan <
> dsetrak...@apache.org
> >> >:
> >> > > >
> >> > > >> Igniters,
> >> > > >>
> >> > > >> I just did a search on 1.6 issues and looks like we have 293
> >> > unresolved
> >> > > >> issues for 1.6. Obviously we are not going to be fixing all of
> them
> >> > and
> >> > > >> most of them will have to be moved to 1.7.
> >> > > >>
> >> > > >> Yakov, given that you have most experience with Jira and have
> been
> >> > > managing
> >> > > >> it before, do you mind moving the tickets? Here is the link to
> the
> >> > > filter:
> >> > > >>
> >> > > >> http://bit.ly/24Mrddg
> >> > > >>
> >> > > >> Also, if anything needs to be addressed in 1.6, please list these
> >> > > tickets
> >> > > >> here, in this thread.
> >> > > >>
> >> > > >> Thanks,
> >> > > >> D.
> >> > > >>
> >> > > >> On Tue, May 10, 2016 at 6:00 AM, Pavel Tupitsyn <
> >> > ptupit...@gridgain.com
> >> > > >
> >> > > >> wrote:
> >> > > >>
> >> > > >>> Dmitriy, yes, many of them do. I'll create 1.6 version on
> >> > > >>> apacheignite-net.readme.io and document them this week (task:
> >> > > >>> IGNITE-3101).
> >> > > >>>
> >> > > >>> Pavel.
> >> > > >>>
> >> > > >>> On Tue, May 10, 2016 at 3:52 PM, Dmitriy Setrakyan <
> >> > > >> dsetrak...@apache.org>
> >> > > >>> wrote:
> >> > > >>>
> >> > >  Thanks Pavel, do any of these features require new
> documentation?
> >> > > 
> >> > >  On Tue, May 10, 2016 at 5:16 AM, Pavel Tupitsyn <
> >> > > >> ptupit...@gridgain.com>
> >> > >  wrote:
> >> > > 
> >> > > > Hi, here is a list of major .NET features included in 1.6 (all
> >> > closed
> >> > > >>> and
> >> > > > merged):
> >> > > >
> >> > > > * LINQ Provider for SQL queries (IGNITE-1630)
> >> > > > * NuGet distribution (IGNITE-1626)
> >> > > > * C#, app.config and web.config configu

[GitHub] ignite pull request: IGNITE-3130 .NET: TcpDiscoverySpi missing pro...

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

https://github.com/apache/ignite/pull/715

IGNITE-3130 .NET: TcpDiscoverySpi missing properties



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ptupitsyn/ignite ignite-3130

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/715.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #715


commit fd4a62bc44266061da918bf3bf3133787739c50f
Author: Pavel Tupitsyn 
Date:   2016-05-12T17:51:19Z

wip

commit 2453794223a1ab3d2cf9e23560f783456606619c
Author: Pavel Tupitsyn 
Date:   2016-05-12T18:01:24Z

all props and defaults added

commit d60c22be9b8ba19ab653e5e57e75c18be4e766e9
Author: Pavel Tupitsyn 
Date:   2016-05-12T18:11:19Z

Read/write done

commit 1da5935923c3df431f40fe80f2841273b6fddb8f
Author: Pavel Tupitsyn 
Date:   2016-05-12T18:18:54Z

java read-write

commit 2554fa531626a852e6678279b670b1b605a0d2d1
Author: Pavel Tupitsyn 
Date:   2016-05-12T18:37:56Z

tests

commit 062aa63954654f11d30d297fbf1ad8e8d6cd459f
Author: Pavel Tupitsyn 
Date:   2016-05-12T18:40:14Z

Fix tests

commit db7e70a14c830fb071ce8201460ceeb8dc323632
Author: Pavel Tupitsyn 
Date:   2016-05-12T18:48:00Z

Update schema

commit 6ec7909ba41a47a6632403c2c42ddea0d3e763d4
Author: Pavel Tupitsyn 
Date:   2016-05-12T18:48:29Z

fix schema

commit a1159229fb2ee8e01bb08c3e3b8059f745be8680
Author: Pavel Tupitsyn 
Date:   2016-05-12T18:51:14Z

Tests done




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-3115: ODBC-related minor fixes.

[isapego]

GitHub user isapego opened a pull request:

https://github.com/apache/ignite/pull/714

IGNITE-3115: ODBC-related minor fixes.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/isapego/ignite ignite-3115

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/714.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #714


commit 011a2383887781aafbbdde2de014e2191893fb66
Author: isapego 
Date:   2016-05-12T15:11:12Z

IGNITE-3115: Fixes for Win ODBC install scripts.

commit 823ecc374a0e5605bb293745b4c3c34f29b518d5
Author: isapego 
Date:   2016-05-12T16:08:14Z

IGNITE-3115: Fix for READMEs.

commit 6053035bd583e73f69a87251e1e1c612961af1ce
Author: Igor Sapego 
Date:   2016-05-12T16:10:14Z

IGNITE-3115: Fix for Makefile. Removed JNI from ODBC dependencies.

commit 06c76d9108759e45bf736a71b752a21dd9786d14
Author: isapego 
Date:   2016-05-12T16:26:03Z

IGNITE-3115: Fixed README for examples.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Ignite 1.6 release timelines

[Alexey Kuznetsov]

Also I already implemented "CacheJdbcPojoStoreFactory.dataSource property
should be replaced with Factory"
https://issues.apache.org/jira/browse/IGNITE-2832

And I think it will be cool to merge into ignite-1.6
But I need a review.

Val, could you take a look? You may compare branch ignite-2832 with master.

On Thu, May 12, 2016 at 10:26 PM, Alexey Kuznetsov 
wrote:

> I'm going to merge Ignite Web Console into ignite-1.6
>
> https://issues.apache.org/jira/browse/IGNITE-843
>
> On Thu, May 12, 2016 at 9:30 PM, Igor Sapego  wrote:
>
>> There is one more C++ ticket I'd like to be included in 1.6 - IGNITE-3113
>> [1].
>>
>> [1] - https://issues.apache.org/jira/browse/IGNITE-3113
>>
>> Best Regards,
>> Igor
>>
>> On Thu, May 12, 2016 at 3:44 PM, Pavel Tupitsyn 
>> wrote:
>>
>> > And one more .NET ticket: IGNITE-3118 .NET:
>> > CacheConfiguration.EvictionPolicy
>> >
>> > On Thu, May 12, 2016 at 12:20 PM, Denis Magda 
>> wrote:
>> >
>> > > Yakov,
>> > >
>> > > Processed all the tickets mentioned in 1. The only one is left is the
>> > > following
>> > > https://issues.apache.org/jira/browse/IGNITE-2954 <
>> > > https://issues.apache.org/jira/browse/IGNITE-2954>
>> > >
>> > > Alex G. I do remember you’ve fixed IGNITE-2954 before. Have you
>> merged it
>> > > into the master? Is the fix in ignite-1.6 already?
>> > >
>> > > —
>> > > Denis
>> > >
>> > > > On May 11, 2016, at 8:56 AM, Yakov Zhdanov 
>> > wrote:
>> > > >
>> > > > Guys,
>> > > >
>> > > > I moved most of the tickets to 1.7 version.
>> > > >
>> > > > I had to leave the following tickets untouched (~80 tickets):
>> > > > 1. labeled with - community important performance customer - Denis,
>> > > > Vladimir and Val can you please review these tickets and move
>> > non-urgent
>> > > > ones. You can use query below
>> > > > 2. with status "in progress". Please everyone having such tickets
>> move
>> > it
>> > > > yourself or finish it in 1.6
>> > > > 3. with status "patch available". Committers, please split the
>> reviews
>> > > and
>> > > > let's include checked/tested fixes to 1.6. Others should be moved.
>> > > >
>> > > > Sam, can you please review and merge -
>> > > > https://issues.apache.org/jira/browse/IGNITE-2744 - Optimize
>> > > "unwindEvict"
>> > > > call in GridCacheIoManager.processMessage().
>> > > > 
>> > > >
>> > > > Query for p1:
>> > > >
>> > > > project = IGNITE AND fixVersion = 1.6 AND resolution = Unresolved
>> AND
>> > > > status not in ("Patch Available", "in progress") AND (labels in
>> > > (community,
>> > > > important, performance, perfomance, customer)) ORDER BY status DESC,
>> > due
>> > > > ASC, priority DESC, created ASC
>> > > >
>> > > > Thanks!
>> > > >
>> > > > --Yakov
>> > > >
>> > > > 2016-05-11 9:47 GMT+06:00 Dmitriy Setrakyan > >:
>> > > >
>> > > >> Igniters,
>> > > >>
>> > > >> I just did a search on 1.6 issues and looks like we have 293
>> > unresolved
>> > > >> issues for 1.6. Obviously we are not going to be fixing all of them
>> > and
>> > > >> most of them will have to be moved to 1.7.
>> > > >>
>> > > >> Yakov, given that you have most experience with Jira and have been
>> > > managing
>> > > >> it before, do you mind moving the tickets? Here is the link to the
>> > > filter:
>> > > >>
>> > > >> http://bit.ly/24Mrddg
>> > > >>
>> > > >> Also, if anything needs to be addressed in 1.6, please list these
>> > > tickets
>> > > >> here, in this thread.
>> > > >>
>> > > >> Thanks,
>> > > >> D.
>> > > >>
>> > > >> On Tue, May 10, 2016 at 6:00 AM, Pavel Tupitsyn <
>> > ptupit...@gridgain.com
>> > > >
>> > > >> wrote:
>> > > >>
>> > > >>> Dmitriy, yes, many of them do. I'll create 1.6 version on
>> > > >>> apacheignite-net.readme.io and document them this week (task:
>> > > >>> IGNITE-3101).
>> > > >>>
>> > > >>> Pavel.
>> > > >>>
>> > > >>> On Tue, May 10, 2016 at 3:52 PM, Dmitriy Setrakyan <
>> > > >> dsetrak...@apache.org>
>> > > >>> wrote:
>> > > >>>
>> > >  Thanks Pavel, do any of these features require new documentation?
>> > > 
>> > >  On Tue, May 10, 2016 at 5:16 AM, Pavel Tupitsyn <
>> > > >> ptupit...@gridgain.com>
>> > >  wrote:
>> > > 
>> > > > Hi, here is a list of major .NET features included in 1.6 (all
>> > closed
>> > > >>> and
>> > > > merged):
>> > > >
>> > > > * LINQ Provider for SQL queries (IGNITE-1630)
>> > > > * NuGet distribution (IGNITE-1626)
>> > > > * C#, app.config and web.config configuration (instead of Spring
>> > XML)
>> > > > (IGNITE-1906, IGNITE-2380)
>> > > > * Atomic data structures (IGNITE-1563)
>> > > > * Universal AnyCPU binaries (instead of separate x64/x86)
>> > > >> (IGNITE-2694)
>> > > > * Call Java services (IGNITE-2686)
>> > > > * Java-based continuous query filters (IGNITE-2977)
>> > > > * Mixed-cluster Compute (IGNITE-2621)
>> > > > * Compute task cancellation (IGNITE-2228)
>> > > > * Binary format compact footers (IGNITE-2702)
>> > > > * Raw mode 

Re: Ignite 1.6 release timelines

[Alexey Kuznetsov]

I'm going to merge Ignite Web Console into ignite-1.6

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

On Thu, May 12, 2016 at 9:30 PM, Igor Sapego  wrote:

> There is one more C++ ticket I'd like to be included in 1.6 - IGNITE-3113
> [1].
>
> [1] - https://issues.apache.org/jira/browse/IGNITE-3113
>
> Best Regards,
> Igor
>
> On Thu, May 12, 2016 at 3:44 PM, Pavel Tupitsyn 
> wrote:
>
> > And one more .NET ticket: IGNITE-3118 .NET:
> > CacheConfiguration.EvictionPolicy
> >
> > On Thu, May 12, 2016 at 12:20 PM, Denis Magda 
> wrote:
> >
> > > Yakov,
> > >
> > > Processed all the tickets mentioned in 1. The only one is left is the
> > > following
> > > https://issues.apache.org/jira/browse/IGNITE-2954 <
> > > https://issues.apache.org/jira/browse/IGNITE-2954>
> > >
> > > Alex G. I do remember you’ve fixed IGNITE-2954 before. Have you merged
> it
> > > into the master? Is the fix in ignite-1.6 already?
> > >
> > > —
> > > Denis
> > >
> > > > On May 11, 2016, at 8:56 AM, Yakov Zhdanov 
> > wrote:
> > > >
> > > > Guys,
> > > >
> > > > I moved most of the tickets to 1.7 version.
> > > >
> > > > I had to leave the following tickets untouched (~80 tickets):
> > > > 1. labeled with - community important performance customer - Denis,
> > > > Vladimir and Val can you please review these tickets and move
> > non-urgent
> > > > ones. You can use query below
> > > > 2. with status "in progress". Please everyone having such tickets
> move
> > it
> > > > yourself or finish it in 1.6
> > > > 3. with status "patch available". Committers, please split the
> reviews
> > > and
> > > > let's include checked/tested fixes to 1.6. Others should be moved.
> > > >
> > > > Sam, can you please review and merge -
> > > > https://issues.apache.org/jira/browse/IGNITE-2744 - Optimize
> > > "unwindEvict"
> > > > call in GridCacheIoManager.processMessage().
> > > > 
> > > >
> > > > Query for p1:
> > > >
> > > > project = IGNITE AND fixVersion = 1.6 AND resolution = Unresolved AND
> > > > status not in ("Patch Available", "in progress") AND (labels in
> > > (community,
> > > > important, performance, perfomance, customer)) ORDER BY status DESC,
> > due
> > > > ASC, priority DESC, created ASC
> > > >
> > > > Thanks!
> > > >
> > > > --Yakov
> > > >
> > > > 2016-05-11 9:47 GMT+06:00 Dmitriy Setrakyan :
> > > >
> > > >> Igniters,
> > > >>
> > > >> I just did a search on 1.6 issues and looks like we have 293
> > unresolved
> > > >> issues for 1.6. Obviously we are not going to be fixing all of them
> > and
> > > >> most of them will have to be moved to 1.7.
> > > >>
> > > >> Yakov, given that you have most experience with Jira and have been
> > > managing
> > > >> it before, do you mind moving the tickets? Here is the link to the
> > > filter:
> > > >>
> > > >> http://bit.ly/24Mrddg
> > > >>
> > > >> Also, if anything needs to be addressed in 1.6, please list these
> > > tickets
> > > >> here, in this thread.
> > > >>
> > > >> Thanks,
> > > >> D.
> > > >>
> > > >> On Tue, May 10, 2016 at 6:00 AM, Pavel Tupitsyn <
> > ptupit...@gridgain.com
> > > >
> > > >> wrote:
> > > >>
> > > >>> Dmitriy, yes, many of them do. I'll create 1.6 version on
> > > >>> apacheignite-net.readme.io and document them this week (task:
> > > >>> IGNITE-3101).
> > > >>>
> > > >>> Pavel.
> > > >>>
> > > >>> On Tue, May 10, 2016 at 3:52 PM, Dmitriy Setrakyan <
> > > >> dsetrak...@apache.org>
> > > >>> wrote:
> > > >>>
> > >  Thanks Pavel, do any of these features require new documentation?
> > > 
> > >  On Tue, May 10, 2016 at 5:16 AM, Pavel Tupitsyn <
> > > >> ptupit...@gridgain.com>
> > >  wrote:
> > > 
> > > > Hi, here is a list of major .NET features included in 1.6 (all
> > closed
> > > >>> and
> > > > merged):
> > > >
> > > > * LINQ Provider for SQL queries (IGNITE-1630)
> > > > * NuGet distribution (IGNITE-1626)
> > > > * C#, app.config and web.config configuration (instead of Spring
> > XML)
> > > > (IGNITE-1906, IGNITE-2380)
> > > > * Atomic data structures (IGNITE-1563)
> > > > * Universal AnyCPU binaries (instead of separate x64/x86)
> > > >> (IGNITE-2694)
> > > > * Call Java services (IGNITE-2686)
> > > > * Java-based continuous query filters (IGNITE-2977)
> > > > * Mixed-cluster Compute (IGNITE-2621)
> > > > * Compute task cancellation (IGNITE-2228)
> > > > * Binary format compact footers (IGNITE-2702)
> > > > * Raw mode reflective serialization (IGNITE-1419)
> > > > * Automatic Java detection: no need for JAVA_HOME (IGNITE-2866)
> > > >
> > > > Thanks,
> > > > Pavel.
> > > >
> > > >
> > > > On Thu, May 5, 2016 at 5:01 PM, Igor Sapego <
> isap...@gridgain.com>
> > >  wrote:
> > > >
> > > >> Hello,
> > > >>
> > > >> IGNITE-1786 is fully merged to master.
> > > >>
> > > >> Best Regards,
> > > >> Igor
> > > >>
> > > >> On Wed, May 4, 2016 at 6:59 PM, Dmitriy Setrakyan

[GitHub] ignite pull request: ignite-2382 JDBC drivers improvements

[agura]

GitHub user agura opened a pull request:

https://github.com/apache/ignite/pull/713

ignite-2382 JDBC drivers improvements



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/agura/incubator-ignite ignite-2382

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/713.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #713


commit fe283a4c40e6d9ee4859acc4f0e7b96d9adfa055
Author: agura 
Date:   2016-05-12T15:01:47Z

ignite-2382 JDBC drivers improvements




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-3090 Memory leak in IgniteH2Indexing p...

[tledkov-gridgain]

GitHub user tledkov-gridgain opened a pull request:

https://github.com/apache/ignite/pull/712

IGNITE-3090 Memory leak in IgniteH2Indexing prepared statements cache…

Add cleanupStmtCache method that is called periodically by the 
GridTimeoutProcessor.
Add memory leaks unit test for specified cases.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-3090

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/712.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #712


commit 001788808b75b3c1790b32dde5daa10a897f9530
Author: tledkov-gridgain 
Date:   2016-05-12T14:40:30Z

IGNITE-3090 Memory leak in IgniteH2Indexing prepared statements cache. Add 
cleanupStmtCache method that is called periodically by the GridTimeoutProcessor.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Ignite 1.6 release timelines

[Igor Sapego]

There is one more C++ ticket I'd like to be included in 1.6 - IGNITE-3113
[1].

[1] - https://issues.apache.org/jira/browse/IGNITE-3113

Best Regards,
Igor

On Thu, May 12, 2016 at 3:44 PM, Pavel Tupitsyn 
wrote:

> And one more .NET ticket: IGNITE-3118 .NET:
> CacheConfiguration.EvictionPolicy
>
> On Thu, May 12, 2016 at 12:20 PM, Denis Magda  wrote:
>
> > Yakov,
> >
> > Processed all the tickets mentioned in 1. The only one is left is the
> > following
> > https://issues.apache.org/jira/browse/IGNITE-2954 <
> > https://issues.apache.org/jira/browse/IGNITE-2954>
> >
> > Alex G. I do remember you’ve fixed IGNITE-2954 before. Have you merged it
> > into the master? Is the fix in ignite-1.6 already?
> >
> > —
> > Denis
> >
> > > On May 11, 2016, at 8:56 AM, Yakov Zhdanov 
> wrote:
> > >
> > > Guys,
> > >
> > > I moved most of the tickets to 1.7 version.
> > >
> > > I had to leave the following tickets untouched (~80 tickets):
> > > 1. labeled with - community important performance customer - Denis,
> > > Vladimir and Val can you please review these tickets and move
> non-urgent
> > > ones. You can use query below
> > > 2. with status "in progress". Please everyone having such tickets move
> it
> > > yourself or finish it in 1.6
> > > 3. with status "patch available". Committers, please split the reviews
> > and
> > > let's include checked/tested fixes to 1.6. Others should be moved.
> > >
> > > Sam, can you please review and merge -
> > > https://issues.apache.org/jira/browse/IGNITE-2744 - Optimize
> > "unwindEvict"
> > > call in GridCacheIoManager.processMessage().
> > > 
> > >
> > > Query for p1:
> > >
> > > project = IGNITE AND fixVersion = 1.6 AND resolution = Unresolved AND
> > > status not in ("Patch Available", "in progress") AND (labels in
> > (community,
> > > important, performance, perfomance, customer)) ORDER BY status DESC,
> due
> > > ASC, priority DESC, created ASC
> > >
> > > Thanks!
> > >
> > > --Yakov
> > >
> > > 2016-05-11 9:47 GMT+06:00 Dmitriy Setrakyan :
> > >
> > >> Igniters,
> > >>
> > >> I just did a search on 1.6 issues and looks like we have 293
> unresolved
> > >> issues for 1.6. Obviously we are not going to be fixing all of them
> and
> > >> most of them will have to be moved to 1.7.
> > >>
> > >> Yakov, given that you have most experience with Jira and have been
> > managing
> > >> it before, do you mind moving the tickets? Here is the link to the
> > filter:
> > >>
> > >> http://bit.ly/24Mrddg
> > >>
> > >> Also, if anything needs to be addressed in 1.6, please list these
> > tickets
> > >> here, in this thread.
> > >>
> > >> Thanks,
> > >> D.
> > >>
> > >> On Tue, May 10, 2016 at 6:00 AM, Pavel Tupitsyn <
> ptupit...@gridgain.com
> > >
> > >> wrote:
> > >>
> > >>> Dmitriy, yes, many of them do. I'll create 1.6 version on
> > >>> apacheignite-net.readme.io and document them this week (task:
> > >>> IGNITE-3101).
> > >>>
> > >>> Pavel.
> > >>>
> > >>> On Tue, May 10, 2016 at 3:52 PM, Dmitriy Setrakyan <
> > >> dsetrak...@apache.org>
> > >>> wrote:
> > >>>
> >  Thanks Pavel, do any of these features require new documentation?
> > 
> >  On Tue, May 10, 2016 at 5:16 AM, Pavel Tupitsyn <
> > >> ptupit...@gridgain.com>
> >  wrote:
> > 
> > > Hi, here is a list of major .NET features included in 1.6 (all
> closed
> > >>> and
> > > merged):
> > >
> > > * LINQ Provider for SQL queries (IGNITE-1630)
> > > * NuGet distribution (IGNITE-1626)
> > > * C#, app.config and web.config configuration (instead of Spring
> XML)
> > > (IGNITE-1906, IGNITE-2380)
> > > * Atomic data structures (IGNITE-1563)
> > > * Universal AnyCPU binaries (instead of separate x64/x86)
> > >> (IGNITE-2694)
> > > * Call Java services (IGNITE-2686)
> > > * Java-based continuous query filters (IGNITE-2977)
> > > * Mixed-cluster Compute (IGNITE-2621)
> > > * Compute task cancellation (IGNITE-2228)
> > > * Binary format compact footers (IGNITE-2702)
> > > * Raw mode reflective serialization (IGNITE-1419)
> > > * Automatic Java detection: no need for JAVA_HOME (IGNITE-2866)
> > >
> > > Thanks,
> > > Pavel.
> > >
> > >
> > > On Thu, May 5, 2016 at 5:01 PM, Igor Sapego 
> >  wrote:
> > >
> > >> Hello,
> > >>
> > >> IGNITE-1786 is fully merged to master.
> > >>
> > >> Best Regards,
> > >> Igor
> > >>
> > >> On Wed, May 4, 2016 at 6:59 PM, Dmitriy Setrakyan <
> >  dsetrak...@apache.org
> > >>
> > >> wrote:
> > >>
> > >>> Resending (fixed links)
> > >>>
> > >>> On Wed, May 4, 2016 at 8:46 AM, Dmitriy Setrakyan <
> > > dsetrak...@apache.org
> > >>>
> > >>> wrote:
> > >>>
> >  Igniters,
> > 
> >  Looks like we are almost done with the outstanding issues,
> > >> mainly
> > > ODBC
> >  support and cache concurrent map changes. As far as the
> > >>> concurren

[jira] [Created] (IGNITE-3130) .NET: TcpDiscoverySpi missing properties

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-3130:
--

 Summary: .NET: TcpDiscoverySpi missing properties
 Key: IGNITE-3130
 URL: https://issues.apache.org/jira/browse/IGNITE-3130
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Affects Versions: 1.6
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.6


localPort, localAddress, etc



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] ignite pull request: IGNITE-3113: C++ documentation improvements.

[isapego]

GitHub user isapego opened a pull request:

https://github.com/apache/ignite/pull/711

IGNITE-3113: C++ documentation improvements.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/isapego/ignite ignite-3113

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/711.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #711


commit 5bbe06be8f46526019a68de9d04ae1784749fc94
Author: isapego 
Date:   2016-05-11T16:57:47Z

IGNITE-3113: Binary containers documentation.

commit 17fdfed41c6fdf643130088319fdd2d4a6a868bd
Author: isapego 
Date:   2016-05-11T16:59:46Z

Merge remote-tracking branch 'upstream/ignite-1.6' into ignite-3113

commit 12e4e285d82f572a0d850dd51b4db01b15434850
Author: isapego 
Date:   2016-05-11T18:18:41Z

IGNITE-3113: Some fixes for documentation.

commit ebd4202caa22f8a277d5c029231de5894f3c1f2e
Author: isapego 
Date:   2016-05-12T13:17:32Z

IGNITE-3113: Further documentation fixes.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-3129) All config samples should contain C#, app.config and Spring XML tabs

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-3129:
--

 Summary: All config samples should contain C#, app.config and 
Spring XML tabs
 Key: IGNITE-3129
 URL: https://issues.apache.org/jira/browse/IGNITE-3129
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Tupitsyn






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-3128) Expiry Policy Configuration

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-3128:
--

 Summary: Expiry Policy Configuration
 Key: IGNITE-3128
 URL: https://issues.apache.org/jira/browse/IGNITE-3128
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Tupitsyn






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-3126) Transaction Configuration

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-3126:
--

 Summary: Transaction Configuration
 Key: IGNITE-3126
 URL: https://issues.apache.org/jira/browse/IGNITE-3126
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Tupitsyn






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-3127) Store Configuration

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-3127:
--

 Summary: Store Configuration
 Key: IGNITE-3127
 URL: https://issues.apache.org/jira/browse/IGNITE-3127
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Tupitsyn






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-3125) Query Configuration

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-3125:
--

 Summary: Query Configuration
 Key: IGNITE-3125
 URL: https://issues.apache.org/jira/browse/IGNITE-3125
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Tupitsyn


* QueryEntity in Spring, app.config and C#
* Attribute-based



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-3123) Network Configuration

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-3123:
--

 Summary: Network Configuration
 Key: IGNITE-3123
 URL: https://issues.apache.org/jira/browse/IGNITE-3123
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Tupitsyn






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-3124) Cache Modes

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-3124:
--

 Summary: Cache Modes
 Key: IGNITE-3124
 URL: https://issues.apache.org/jira/browse/IGNITE-3124
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Tupitsyn






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-3122) Cluster Configuration

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-3122:
--

 Summary: Cluster Configuration
 Key: IGNITE-3122
 URL: https://issues.apache.org/jira/browse/IGNITE-3122
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Tupitsyn






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-3121) Atomics

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-3121:
--

 Summary: Atomics
 Key: IGNITE-3121
 URL: https://issues.apache.org/jira/browse/IGNITE-3121
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Tupitsyn






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-3120) LINQ Provider

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-3120:
--

 Summary: LINQ Provider
 Key: IGNITE-3120
 URL: https://issues.apache.org/jira/browse/IGNITE-3120
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Tupitsyn






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-3119) NuGet

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-3119:
--

 Summary: NuGet
 Key: IGNITE-3119
 URL: https://issues.apache.org/jira/browse/IGNITE-3119
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Tupitsyn






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Ignite 1.6 release timelines

[Pavel Tupitsyn]

And one more .NET ticket: IGNITE-3118 .NET:
CacheConfiguration.EvictionPolicy

On Thu, May 12, 2016 at 12:20 PM, Denis Magda  wrote:

> Yakov,
>
> Processed all the tickets mentioned in 1. The only one is left is the
> following
> https://issues.apache.org/jira/browse/IGNITE-2954 <
> https://issues.apache.org/jira/browse/IGNITE-2954>
>
> Alex G. I do remember you’ve fixed IGNITE-2954 before. Have you merged it
> into the master? Is the fix in ignite-1.6 already?
>
> —
> Denis
>
> > On May 11, 2016, at 8:56 AM, Yakov Zhdanov  wrote:
> >
> > Guys,
> >
> > I moved most of the tickets to 1.7 version.
> >
> > I had to leave the following tickets untouched (~80 tickets):
> > 1. labeled with - community important performance customer - Denis,
> > Vladimir and Val can you please review these tickets and move non-urgent
> > ones. You can use query below
> > 2. with status "in progress". Please everyone having such tickets move it
> > yourself or finish it in 1.6
> > 3. with status "patch available". Committers, please split the reviews
> and
> > let's include checked/tested fixes to 1.6. Others should be moved.
> >
> > Sam, can you please review and merge -
> > https://issues.apache.org/jira/browse/IGNITE-2744 - Optimize
> "unwindEvict"
> > call in GridCacheIoManager.processMessage().
> > 
> >
> > Query for p1:
> >
> > project = IGNITE AND fixVersion = 1.6 AND resolution = Unresolved AND
> > status not in ("Patch Available", "in progress") AND (labels in
> (community,
> > important, performance, perfomance, customer)) ORDER BY status DESC, due
> > ASC, priority DESC, created ASC
> >
> > Thanks!
> >
> > --Yakov
> >
> > 2016-05-11 9:47 GMT+06:00 Dmitriy Setrakyan :
> >
> >> Igniters,
> >>
> >> I just did a search on 1.6 issues and looks like we have 293 unresolved
> >> issues for 1.6. Obviously we are not going to be fixing all of them and
> >> most of them will have to be moved to 1.7.
> >>
> >> Yakov, given that you have most experience with Jira and have been
> managing
> >> it before, do you mind moving the tickets? Here is the link to the
> filter:
> >>
> >> http://bit.ly/24Mrddg
> >>
> >> Also, if anything needs to be addressed in 1.6, please list these
> tickets
> >> here, in this thread.
> >>
> >> Thanks,
> >> D.
> >>
> >> On Tue, May 10, 2016 at 6:00 AM, Pavel Tupitsyn  >
> >> wrote:
> >>
> >>> Dmitriy, yes, many of them do. I'll create 1.6 version on
> >>> apacheignite-net.readme.io and document them this week (task:
> >>> IGNITE-3101).
> >>>
> >>> Pavel.
> >>>
> >>> On Tue, May 10, 2016 at 3:52 PM, Dmitriy Setrakyan <
> >> dsetrak...@apache.org>
> >>> wrote:
> >>>
>  Thanks Pavel, do any of these features require new documentation?
> 
>  On Tue, May 10, 2016 at 5:16 AM, Pavel Tupitsyn <
> >> ptupit...@gridgain.com>
>  wrote:
> 
> > Hi, here is a list of major .NET features included in 1.6 (all closed
> >>> and
> > merged):
> >
> > * LINQ Provider for SQL queries (IGNITE-1630)
> > * NuGet distribution (IGNITE-1626)
> > * C#, app.config and web.config configuration (instead of Spring XML)
> > (IGNITE-1906, IGNITE-2380)
> > * Atomic data structures (IGNITE-1563)
> > * Universal AnyCPU binaries (instead of separate x64/x86)
> >> (IGNITE-2694)
> > * Call Java services (IGNITE-2686)
> > * Java-based continuous query filters (IGNITE-2977)
> > * Mixed-cluster Compute (IGNITE-2621)
> > * Compute task cancellation (IGNITE-2228)
> > * Binary format compact footers (IGNITE-2702)
> > * Raw mode reflective serialization (IGNITE-1419)
> > * Automatic Java detection: no need for JAVA_HOME (IGNITE-2866)
> >
> > Thanks,
> > Pavel.
> >
> >
> > On Thu, May 5, 2016 at 5:01 PM, Igor Sapego 
>  wrote:
> >
> >> Hello,
> >>
> >> IGNITE-1786 is fully merged to master.
> >>
> >> Best Regards,
> >> Igor
> >>
> >> On Wed, May 4, 2016 at 6:59 PM, Dmitriy Setrakyan <
>  dsetrak...@apache.org
> >>
> >> wrote:
> >>
> >>> Resending (fixed links)
> >>>
> >>> On Wed, May 4, 2016 at 8:46 AM, Dmitriy Setrakyan <
> > dsetrak...@apache.org
> >>>
> >>> wrote:
> >>>
>  Igniters,
> 
>  Looks like we are almost done with the outstanding issues,
> >> mainly
> > ODBC
>  support and cache concurrent map changes. As far as the
> >>> concurrent
> > map,
> >>> we
>  had a performance drop, and I think it is pretty important that
> >>> we
> >>> address
>  it prior to the release.
> 
>  Can we please get an update for these tickets?
> 
>  IGNITE-2948  >>>
> >>> -
>  Optimize usage of GridCacheConcurrentMap
>  IGNITE-1786  >>>
> >>> -
> > Need
> >>> to
>  implement ODBC driver for Ignite
> >>

Re: Halfway to Ignite 1.6

[Anton Vinogradov]

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  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  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&tab=projectOverview&branch_IgniteTests=ignite-1.6
>>
>> So, feel free to start investigations and fix issues :)
>>
>
>

Re: Halfway to Ignite 1.6

[Anton Vinogradov]

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  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&tab=projectOverview&branch_IgniteTests=ignite-1.6
>
> So, feel free to start investigations and fix issues :)
>

[GitHub] ignite pull request: IGNITE-3118 .NET: CacheConfiguration.Eviction...

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

https://github.com/apache/ignite/pull/710

IGNITE-3118 .NET: CacheConfiguration.EvictionPolicy



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ptupitsyn/ignite ignite-3118

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/710.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #710


commit babc6fc1f3eedf468c8ba63b7274cce0835df647
Author: Pavel Tupitsyn 
Date:   2016-05-12T09:51:30Z

IGNITE-3118 .NET: CacheConfiguration.EvictionPolicy

commit dfe559ad9dc8414b322bf5fb56cc8e1d1be5fe8c
Author: Pavel Tupitsyn 
Date:   2016-05-12T10:12:09Z

Update xml schema

commit 1c760341ef69a93f0cb430773711c6f316a57d7c
Author: Pavel Tupitsyn 
Date:   2016-05-12T10:17:42Z

wip tests

commit 9d0d87468cd8b1c90b4f5748b1078a9d07d9e3ce
Author: Pavel Tupitsyn 
Date:   2016-05-12T10:24:50Z

Fix xml test

commit cb3f61896c0659967438deb845ac90750dc44d44
Author: Pavel Tupitsyn 
Date:   2016-05-12T10:29:33Z

tests done




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: 7.5.20

[devozerov]

GitHub user devozerov opened a pull request:

https://github.com/apache/ignite/pull/709

7.5.20



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite gridgain-7.5.20

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/709.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #709


commit 2e64d0d7cc51552fffc231cbc850cd615076fb85
Author: vozerov-gridgain 
Date:   2015-12-29T06:31:58Z

IGNITE-2258: IGFS: now default path modes could be optionally disabled 
using FileSystemConfiguration.isInitializeDefaultPathModes() property.

commit 4cd3b3dc2f1fa0f1a9cceb6bf544dd8fb505d7f5
Author: vozerov-gridgain 
Date:   2015-12-29T09:52:00Z

IGNITE-2258: Fixed type on getter/setter.

commit 5d58fcbf40fdb9114e4cbb32b72dd9bce7fa38ca
Author: iveselovskiy 
Date:   2016-01-04T06:47:28Z

IGNITE-2308: Fixed HadoopClassLoader dependency resolution. This closes 
#391.

commit 83a19179cee2bb15adc36c2265dd0a3c794b60bb
Author: vozerov-gridgain 
Date:   2016-01-04T08:14:58Z

IGNITE-2218: Fixed a problem with native Hadoop libraries load. This closes 
#378.

commit 1d7fb5702fa33cf395e797161f3a86a9600921a7
Author: vozerov-gridgain 
Date:   2016-01-05T06:59:31Z

IGNITE-2206: Hadoop file system creation is now abstracted out using 
factory interface.

commit a12ec7d08573d5396654a5ba05bb7d873e4c2677
Author: Ignite Teamcity 
Date:   2016-01-06T10:50:48Z

1.5.2

commit 090a5de6a930c10a3a57a6e28c486fe5c87e028d
Author: vozerov-gridgain 
Date:   2015-12-29T12:50:39Z

Minor fix.

commit c786820dda7f7cd1849c5593ac24ca9072945887
Author: vozerov-gridgain 
Date:   2016-01-07T13:48:14Z

IgniteHadoopIgfsSecondaryFileSystem.usrName field is renamed to "userName" 
to preserve backward compatibility.

commit 6ab4ce246316442fa4295f9941c372fea70c24ef
Author: vozerov-gridgain 
Date:   2016-01-08T06:23:55Z

IGNITE-2342: Set correct classlader before calling FileSystem.get().

commit 077ab1b3a77fdb1c2c2fd6360fc5b60fda6c50c3
Author: vozerov-gridgain 
Date:   2016-01-08T07:17:45Z

IGNITE-2341: Improved warning message when BinaryMarshaller cannot be used. 
Also it is not shown when "org.apache.ignite" classes is in described situation.

commit 86c4816edfd0e983014f136ffc92cde28ec56cca
Author: vozerov-gridgain 
Date:   2016-01-08T07:26:03Z

IGNITE-2340: Improved error thrown when PROXY mode exists, but secondary 
file system is not IgniteHadoopIgfsSecondaryFileSystem.

commit fc48a8429a84ef6c87ed3225a218d7d3ae617e14
Author: vozerov-gridgain 
Date:   2016-01-08T07:48:42Z

Merge branch 'ignite-1.5.2' into ignite-1.5.3

commit 86740cefe212ed0f506d81056dd8e76de9a31e4f
Author: Ignite Teamcity 
Date:   2016-01-08T09:32:11Z

1.5.3-SNAPSHOT

commit 92229d2a6c6ef86772a62cb52b3aa07a55c99d89
Author: sboikov 
Date:   2016-01-13T05:56:34Z

ignite-2359 Added locking for files used by MarshallerContextImpl. (cherry 
picked from commit 1d8c4e2)

commit 2e4ce585d5f54502c6511d3425b1cd5fbf0a7f4f
Author: Ignite Teamcity 
Date:   2016-01-13T10:37:33Z

1.5.4-SNAPSHOT

commit 6e5f9f0c7d4c86773b1f0cd5c5a673acb58c86c2
Author: Denis Magda 
Date:   2016-01-13T11:42:27Z

Changed year to 2016 in Copyrights

commit 02dbcfd8ed2701a4f415c8871d0b8fd08bfa0583
Author: Alexey Goncharuk 
Date:   2016-01-13T13:47:32Z

IGNITE-2365 - Notify policy if swap or offheap is enabled and rebalanced 
entry was not preloaded.
IGNITE-2099 - Fixing custom collections.
This closes #396

commit 86c2ba2a601e82b824cf17422683e5398a4d8c7d
Author: sboikov 
Date:   2016-01-13T15:40:08Z

ignite-2350 Pass update notifier flag in discovery data (all cluster nodes 
will have the same notifier status as first cluster node)
(cherry picked from commit 7175a42)

commit e1a494df400fc37ca04e8d88d1cf20bca02607b4
Author: sboikov 
Date:   2016-01-14T11:16:33Z

Renamed fields to change fields write order (to preserve backward 
compatibility).
(cherry picked from commit 2a4adf5)

commit 09f978234b6062afa1e1658d5a6439365a856aca
Author: sboikov 
Date:   2016-01-14T11:42:44Z

Merge remote-tracking branch 'origin/ignite-1.5.4' into ignite-1.5.4

commit 30043e7892d0b52dc851ce5ec79c7eb3b7cc44fb
Author: Denis Magda 
Date:   2016-01-14T13:02:50Z

Added release notes

commit cc3db35925698f1670a8bf1c6a1830c0c9b51290
Author: vershov 
Date:   2016-01-14T14:21:56Z

IGNITE-2032 Unwind undeploys in preloader - Fixes #369.

Signed-off-by: Alexey Goncharuk 

commit a5c85ca7749ae90af2e4a29e2162713b480e40fa
Author: Valentin Kulichenko 
Date:   2016-01-15T06:58:41Z

Update notifier fixes

commit 8f32a29c5a7b28b7e1173582f4c7cef5b6d73b27
Author: Ignite Teamcity 
Date:   2016-01-15T11:00:29Z

1.5.4-SNAPSHOT

commit 6482dc80bf9cdf7aa4f592d9266c6745211b1c4c
Author: sboikov 
Date:   2016-01-15T12:15

[GitHub] ignite pull request: 7.5.20

[devozerov]

Github user devozerov closed the pull request at:

https://github.com/apache/ignite/pull/708


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-3118) .NET: CacheConfiguration.EvictionPolicy

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-3118:
--

 Summary: .NET: CacheConfiguration.EvictionPolicy
 Key: IGNITE-3118
 URL: https://issues.apache.org/jira/browse/IGNITE-3118
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Affects Versions: 1.6
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.6


Propagate CacheConfiguration.EvictionPolicy.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

visorcmd alerts: improvements and fixes

[Vasiliy Sisko]

Hello Igniters.

I implement execution of custom script on alert for visorcmd:
https://issues.apache.org/jira/browse/IGNITE-2919. Now some logic can be
defined in case of specific grid conditions in format sh/bat file.

Also fixed reaction on alert condition switch:
https://issues.apache.org/jira/browse/IGNITE-2930.


-- 
Vasiliy Sisko
GridGain Systems
www.gridgain.com

Re: Ignite 1.6 release timelines

[Denis Magda]

Yakov,

Processed all the tickets mentioned in 1. The only one is left is the following
https://issues.apache.org/jira/browse/IGNITE-2954 


Alex G. I do remember you’ve fixed IGNITE-2954 before. Have you merged it into 
the master? Is the fix in ignite-1.6 already?

—
Denis

> On May 11, 2016, at 8:56 AM, Yakov Zhdanov  wrote:
> 
> Guys,
> 
> I moved most of the tickets to 1.7 version.
> 
> I had to leave the following tickets untouched (~80 tickets):
> 1. labeled with - community important performance customer - Denis,
> Vladimir and Val can you please review these tickets and move non-urgent
> ones. You can use query below
> 2. with status "in progress". Please everyone having such tickets move it
> yourself or finish it in 1.6
> 3. with status "patch available". Committers, please split the reviews and
> let's include checked/tested fixes to 1.6. Others should be moved.
> 
> Sam, can you please review and merge -
> https://issues.apache.org/jira/browse/IGNITE-2744 - Optimize "unwindEvict"
> call in GridCacheIoManager.processMessage().
> 
> 
> Query for p1:
> 
> project = IGNITE AND fixVersion = 1.6 AND resolution = Unresolved AND
> status not in ("Patch Available", "in progress") AND (labels in (community,
> important, performance, perfomance, customer)) ORDER BY status DESC, due
> ASC, priority DESC, created ASC
> 
> Thanks!
> 
> --Yakov
> 
> 2016-05-11 9:47 GMT+06:00 Dmitriy Setrakyan :
> 
>> Igniters,
>> 
>> I just did a search on 1.6 issues and looks like we have 293 unresolved
>> issues for 1.6. Obviously we are not going to be fixing all of them and
>> most of them will have to be moved to 1.7.
>> 
>> Yakov, given that you have most experience with Jira and have been managing
>> it before, do you mind moving the tickets? Here is the link to the filter:
>> 
>> http://bit.ly/24Mrddg
>> 
>> Also, if anything needs to be addressed in 1.6, please list these tickets
>> here, in this thread.
>> 
>> Thanks,
>> D.
>> 
>> On Tue, May 10, 2016 at 6:00 AM, Pavel Tupitsyn 
>> wrote:
>> 
>>> Dmitriy, yes, many of them do. I'll create 1.6 version on
>>> apacheignite-net.readme.io and document them this week (task:
>>> IGNITE-3101).
>>> 
>>> Pavel.
>>> 
>>> On Tue, May 10, 2016 at 3:52 PM, Dmitriy Setrakyan <
>> dsetrak...@apache.org>
>>> wrote:
>>> 
 Thanks Pavel, do any of these features require new documentation?
 
 On Tue, May 10, 2016 at 5:16 AM, Pavel Tupitsyn <
>> ptupit...@gridgain.com>
 wrote:
 
> Hi, here is a list of major .NET features included in 1.6 (all closed
>>> and
> merged):
> 
> * LINQ Provider for SQL queries (IGNITE-1630)
> * NuGet distribution (IGNITE-1626)
> * C#, app.config and web.config configuration (instead of Spring XML)
> (IGNITE-1906, IGNITE-2380)
> * Atomic data structures (IGNITE-1563)
> * Universal AnyCPU binaries (instead of separate x64/x86)
>> (IGNITE-2694)
> * Call Java services (IGNITE-2686)
> * Java-based continuous query filters (IGNITE-2977)
> * Mixed-cluster Compute (IGNITE-2621)
> * Compute task cancellation (IGNITE-2228)
> * Binary format compact footers (IGNITE-2702)
> * Raw mode reflective serialization (IGNITE-1419)
> * Automatic Java detection: no need for JAVA_HOME (IGNITE-2866)
> 
> Thanks,
> Pavel.
> 
> 
> On Thu, May 5, 2016 at 5:01 PM, Igor Sapego 
 wrote:
> 
>> Hello,
>> 
>> IGNITE-1786 is fully merged to master.
>> 
>> Best Regards,
>> Igor
>> 
>> On Wed, May 4, 2016 at 6:59 PM, Dmitriy Setrakyan <
 dsetrak...@apache.org
>> 
>> wrote:
>> 
>>> Resending (fixed links)
>>> 
>>> On Wed, May 4, 2016 at 8:46 AM, Dmitriy Setrakyan <
> dsetrak...@apache.org
>>> 
>>> wrote:
>>> 
 Igniters,
 
 Looks like we are almost done with the outstanding issues,
>> mainly
> ODBC
 support and cache concurrent map changes. As far as the
>>> concurrent
> map,
>>> we
 had a performance drop, and I think it is pretty important that
>>> we
>>> address
 it prior to the release.
 
 Can we please get an update for these tickets?
 
 IGNITE-2948 >> 
>>> -
 Optimize usage of GridCacheConcurrentMap
 IGNITE-1786 >> 
>>> -
> Need
>>> to
 implement ODBC driver for Ignite
 
 Once these issues are resolved, we can move to the testing
>> phase
>>> (probably
 a week), and then send it for the vote.
 
 D.
 
 On Fri, Apr 29, 2016 at 3:12 AM, Yakov Zhdanov <
 yzhda...@apache.org>
 wrote:
 
> I think we are almost done with odbc support and I hope that
>> we
 can
> release
> abo

[jira] [Created] (IGNITE-3117) Weblogic manual tests for HttpSession caching.

[Dmitry Karachentsev (JIRA)]

Dmitry Karachentsev created IGNITE-3117:
---

 Summary: Weblogic manual tests for HttpSession caching.
 Key: IGNITE-3117
 URL: https://issues.apache.org/jira/browse/IGNITE-3117
 Project: Ignite
  Issue Type: Test
  Components: websession
Affects Versions: 1.6
Reporter: Dmitry Karachentsev
Assignee: Dmitry Karachentsev
 Fix For: 1.7


Simple tests that allow deploy and check that HttpSession is cached properly in 
grid.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

ignite-3023 merged

[Yakov Zhdanov]

jcfiorenzano, thank you for contributing fix for ignite-3023 Rename
keyBackups to Backups for performance advices printed out on a node (
https://issues.apache.org/jira/browse/IGNITE-3023). I merged it to master.

Please close the PR.

--Yakov

Re: Ignite 1.6 release timelines

[Alexey Kuznetsov]

I merged into 1.6 one more ticket: IGNITE-2919 Implemented script execution
when alert triggered.
https://issues.apache.org/jira/browse/IGNITE-2919

On Thu, May 12, 2016 at 3:29 PM, Pavel Tupitsyn 
wrote:

> Hi, there is one more .NET ticket to be merged to 1.6:
> IGNITE-3112 .NET: Allow merging Spring XML config with .NET config
>
> Other two 1.6 .NET tickets are documentation-related and have no code
> changes: IGNITE-2963, IGNITE-3101
>
> Thanks,
> Pavel
>
> On Wed, May 11, 2016 at 10:03 PM, Andrey Gura  wrote:
>
> > Hi all,
> >
> > I think that JDBC driver improvements [1] should be included in 1.6
> > release. I'm working on it.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-2382
> >
> > On Wed, May 11, 2016 at 1:54 PM, Igor Sapego 
> wrote:
> >
> > > Hi,
> > >
> > > I have also finished transactions API for the C++ [1] and
> > > it is also going to be included to 1.6. It is already merged to
> > > release branch.
> > >
> > > [1] - https://issues.apache.org/jira/browse/IGNITE-2805.
> > >
> > > Best Regards,
> > > Igor
> > >
> > > On Wed, May 11, 2016 at 1:49 PM, Sergey Kozlov 
> > > wrote:
> > >
> > > > The following issues found for 1.6 recently:
> > > >
> > > > IGNITE-3109 IgfsMapReduceExample fails ClassNotFoundException
> > > > 
> > > >  - critical
> > > > IGNITE-3107 Help for tasks/events should be rephrased
> > > > 
> > > >  - trivial, doc issue
> > > >
> > > > On Wed, May 11, 2016 at 8:56 AM, Yakov Zhdanov 
> > > > wrote:
> > > >
> > > > > Guys,
> > > > >
> > > > > I moved most of the tickets to 1.7 version.
> > > > >
> > > > > I had to leave the following tickets untouched (~80 tickets):
> > > > > 1. labeled with - community important performance customer - Denis,
> > > > > Vladimir and Val can you please review these tickets and move
> > > non-urgent
> > > > > ones. You can use query below
> > > > > 2. with status "in progress". Please everyone having such tickets
> > move
> > > it
> > > > > yourself or finish it in 1.6
> > > > > 3. with status "patch available". Committers, please split the
> > reviews
> > > > and
> > > > > let's include checked/tested fixes to 1.6. Others should be moved.
> > > > >
> > > > > Sam, can you please review and merge -
> > > > > https://issues.apache.org/jira/browse/IGNITE-2744 - Optimize
> > > > "unwindEvict"
> > > > > call in GridCacheIoManager.processMessage().
> > > > > 
> > > > >
> > > > > Query for p1:
> > > > >
> > > > > project = IGNITE AND fixVersion = 1.6 AND resolution = Unresolved
> AND
> > > > > status not in ("Patch Available", "in progress") AND (labels in
> > > > (community,
> > > > > important, performance, perfomance, customer)) ORDER BY status
> DESC,
> > > due
> > > > > ASC, priority DESC, created ASC
> > > > >
> > > > > Thanks!
> > > > >
> > > > > --Yakov
> > > > >
> > > > > 2016-05-11 9:47 GMT+06:00 Dmitriy Setrakyan  >:
> > > > >
> > > > > > Igniters,
> > > > > >
> > > > > > I just did a search on 1.6 issues and looks like we have 293
> > > unresolved
> > > > > > issues for 1.6. Obviously we are not going to be fixing all of
> them
> > > and
> > > > > > most of them will have to be moved to 1.7.
> > > > > >
> > > > > > Yakov, given that you have most experience with Jira and have
> been
> > > > > managing
> > > > > > it before, do you mind moving the tickets? Here is the link to
> the
> > > > > filter:
> > > > > >
> > > > > > http://bit.ly/24Mrddg
> > > > > >
> > > > > > Also, if anything needs to be addressed in 1.6, please list these
> > > > tickets
> > > > > > here, in this thread.
> > > > > >
> > > > > > Thanks,
> > > > > > D.
> > > > > >
> > > > > > On Tue, May 10, 2016 at 6:00 AM, Pavel Tupitsyn <
> > > > ptupit...@gridgain.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Dmitriy, yes, many of them do. I'll create 1.6 version on
> > > > > > > apacheignite-net.readme.io and document them this week (task:
> > > > > > > IGNITE-3101).
> > > > > > >
> > > > > > > Pavel.
> > > > > > >
> > > > > > > On Tue, May 10, 2016 at 3:52 PM, Dmitriy Setrakyan <
> > > > > > dsetrak...@apache.org>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Thanks Pavel, do any of these features require new
> > documentation?
> > > > > > > >
> > > > > > > > On Tue, May 10, 2016 at 5:16 AM, Pavel Tupitsyn <
> > > > > > ptupit...@gridgain.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hi, here is a list of major .NET features included in 1.6
> > (all
> > > > > closed
> > > > > > > and
> > > > > > > > > merged):
> > > > > > > > >
> > > > > > > > > * LINQ Provider for SQL queries (IGNITE-1630)
> > > > > > > > > * NuGet distribution (IGNITE-1626)
> > > > > > > > > * C#, app.config and web.config configuration (instead of
> > > Spring
> > > > > XML)
> > > > > > > > > (IGNITE-1906, IGNITE-2380)
> > > > > > > > > * Atomic data structures (IGNITE-1563)
> > > > > > > > > * Universal AnyCPU binarie

[GitHub] ignite pull request: 7.5.20

[devozerov]

GitHub user devozerov opened a pull request:

https://github.com/apache/ignite/pull/708

7.5.20



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite gridgian-7.5.20

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/708.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #708


commit 2e64d0d7cc51552fffc231cbc850cd615076fb85
Author: vozerov-gridgain 
Date:   2015-12-29T06:31:58Z

IGNITE-2258: IGFS: now default path modes could be optionally disabled 
using FileSystemConfiguration.isInitializeDefaultPathModes() property.

commit 4cd3b3dc2f1fa0f1a9cceb6bf544dd8fb505d7f5
Author: vozerov-gridgain 
Date:   2015-12-29T09:52:00Z

IGNITE-2258: Fixed type on getter/setter.

commit 5d58fcbf40fdb9114e4cbb32b72dd9bce7fa38ca
Author: iveselovskiy 
Date:   2016-01-04T06:47:28Z

IGNITE-2308: Fixed HadoopClassLoader dependency resolution. This closes 
#391.

commit 83a19179cee2bb15adc36c2265dd0a3c794b60bb
Author: vozerov-gridgain 
Date:   2016-01-04T08:14:58Z

IGNITE-2218: Fixed a problem with native Hadoop libraries load. This closes 
#378.

commit 1d7fb5702fa33cf395e797161f3a86a9600921a7
Author: vozerov-gridgain 
Date:   2016-01-05T06:59:31Z

IGNITE-2206: Hadoop file system creation is now abstracted out using 
factory interface.

commit a12ec7d08573d5396654a5ba05bb7d873e4c2677
Author: Ignite Teamcity 
Date:   2016-01-06T10:50:48Z

1.5.2

commit 090a5de6a930c10a3a57a6e28c486fe5c87e028d
Author: vozerov-gridgain 
Date:   2015-12-29T12:50:39Z

Minor fix.

commit c786820dda7f7cd1849c5593ac24ca9072945887
Author: vozerov-gridgain 
Date:   2016-01-07T13:48:14Z

IgniteHadoopIgfsSecondaryFileSystem.usrName field is renamed to "userName" 
to preserve backward compatibility.

commit 6ab4ce246316442fa4295f9941c372fea70c24ef
Author: vozerov-gridgain 
Date:   2016-01-08T06:23:55Z

IGNITE-2342: Set correct classlader before calling FileSystem.get().

commit 077ab1b3a77fdb1c2c2fd6360fc5b60fda6c50c3
Author: vozerov-gridgain 
Date:   2016-01-08T07:17:45Z

IGNITE-2341: Improved warning message when BinaryMarshaller cannot be used. 
Also it is not shown when "org.apache.ignite" classes is in described situation.

commit 86c4816edfd0e983014f136ffc92cde28ec56cca
Author: vozerov-gridgain 
Date:   2016-01-08T07:26:03Z

IGNITE-2340: Improved error thrown when PROXY mode exists, but secondary 
file system is not IgniteHadoopIgfsSecondaryFileSystem.

commit fc48a8429a84ef6c87ed3225a218d7d3ae617e14
Author: vozerov-gridgain 
Date:   2016-01-08T07:48:42Z

Merge branch 'ignite-1.5.2' into ignite-1.5.3

commit 86740cefe212ed0f506d81056dd8e76de9a31e4f
Author: Ignite Teamcity 
Date:   2016-01-08T09:32:11Z

1.5.3-SNAPSHOT

commit 92229d2a6c6ef86772a62cb52b3aa07a55c99d89
Author: sboikov 
Date:   2016-01-13T05:56:34Z

ignite-2359 Added locking for files used by MarshallerContextImpl. (cherry 
picked from commit 1d8c4e2)

commit 2e4ce585d5f54502c6511d3425b1cd5fbf0a7f4f
Author: Ignite Teamcity 
Date:   2016-01-13T10:37:33Z

1.5.4-SNAPSHOT

commit 6e5f9f0c7d4c86773b1f0cd5c5a673acb58c86c2
Author: Denis Magda 
Date:   2016-01-13T11:42:27Z

Changed year to 2016 in Copyrights

commit 02dbcfd8ed2701a4f415c8871d0b8fd08bfa0583
Author: Alexey Goncharuk 
Date:   2016-01-13T13:47:32Z

IGNITE-2365 - Notify policy if swap or offheap is enabled and rebalanced 
entry was not preloaded.
IGNITE-2099 - Fixing custom collections.
This closes #396

commit 86c2ba2a601e82b824cf17422683e5398a4d8c7d
Author: sboikov 
Date:   2016-01-13T15:40:08Z

ignite-2350 Pass update notifier flag in discovery data (all cluster nodes 
will have the same notifier status as first cluster node)
(cherry picked from commit 7175a42)

commit e1a494df400fc37ca04e8d88d1cf20bca02607b4
Author: sboikov 
Date:   2016-01-14T11:16:33Z

Renamed fields to change fields write order (to preserve backward 
compatibility).
(cherry picked from commit 2a4adf5)

commit 09f978234b6062afa1e1658d5a6439365a856aca
Author: sboikov 
Date:   2016-01-14T11:42:44Z

Merge remote-tracking branch 'origin/ignite-1.5.4' into ignite-1.5.4

commit 30043e7892d0b52dc851ce5ec79c7eb3b7cc44fb
Author: Denis Magda 
Date:   2016-01-14T13:02:50Z

Added release notes

commit cc3db35925698f1670a8bf1c6a1830c0c9b51290
Author: vershov 
Date:   2016-01-14T14:21:56Z

IGNITE-2032 Unwind undeploys in preloader - Fixes #369.

Signed-off-by: Alexey Goncharuk 

commit a5c85ca7749ae90af2e4a29e2162713b480e40fa
Author: Valentin Kulichenko 
Date:   2016-01-15T06:58:41Z

Update notifier fixes

commit 8f32a29c5a7b28b7e1173582f4c7cef5b6d73b27
Author: Ignite Teamcity 
Date:   2016-01-15T11:00:29Z

1.5.4-SNAPSHOT

commit 6482dc80bf9cdf7aa4f592d9266c6745211b1c4c
Author: sboikov 
Date:   2016-01-15T12:15

[GitHub] ignite pull request: ignite-3116

[sboikov]

GitHub user sboikov opened a pull request:

https://github.com/apache/ignite/pull/707

ignite-3116



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-3116

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/707.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #707


commit 2e64d0d7cc51552fffc231cbc850cd615076fb85
Author: vozerov-gridgain 
Date:   2015-12-29T06:31:58Z

IGNITE-2258: IGFS: now default path modes could be optionally disabled 
using FileSystemConfiguration.isInitializeDefaultPathModes() property.

commit 4cd3b3dc2f1fa0f1a9cceb6bf544dd8fb505d7f5
Author: vozerov-gridgain 
Date:   2015-12-29T09:52:00Z

IGNITE-2258: Fixed type on getter/setter.

commit 5d58fcbf40fdb9114e4cbb32b72dd9bce7fa38ca
Author: iveselovskiy 
Date:   2016-01-04T06:47:28Z

IGNITE-2308: Fixed HadoopClassLoader dependency resolution. This closes 
#391.

commit 83a19179cee2bb15adc36c2265dd0a3c794b60bb
Author: vozerov-gridgain 
Date:   2016-01-04T08:14:58Z

IGNITE-2218: Fixed a problem with native Hadoop libraries load. This closes 
#378.

commit 1d7fb5702fa33cf395e797161f3a86a9600921a7
Author: vozerov-gridgain 
Date:   2016-01-05T06:59:31Z

IGNITE-2206: Hadoop file system creation is now abstracted out using 
factory interface.

commit a12ec7d08573d5396654a5ba05bb7d873e4c2677
Author: Ignite Teamcity 
Date:   2016-01-06T10:50:48Z

1.5.2

commit 090a5de6a930c10a3a57a6e28c486fe5c87e028d
Author: vozerov-gridgain 
Date:   2015-12-29T12:50:39Z

Minor fix.

commit c786820dda7f7cd1849c5593ac24ca9072945887
Author: vozerov-gridgain 
Date:   2016-01-07T13:48:14Z

IgniteHadoopIgfsSecondaryFileSystem.usrName field is renamed to "userName" 
to preserve backward compatibility.

commit 6ab4ce246316442fa4295f9941c372fea70c24ef
Author: vozerov-gridgain 
Date:   2016-01-08T06:23:55Z

IGNITE-2342: Set correct classlader before calling FileSystem.get().

commit 077ab1b3a77fdb1c2c2fd6360fc5b60fda6c50c3
Author: vozerov-gridgain 
Date:   2016-01-08T07:17:45Z

IGNITE-2341: Improved warning message when BinaryMarshaller cannot be used. 
Also it is not shown when "org.apache.ignite" classes is in described situation.

commit 86c4816edfd0e983014f136ffc92cde28ec56cca
Author: vozerov-gridgain 
Date:   2016-01-08T07:26:03Z

IGNITE-2340: Improved error thrown when PROXY mode exists, but secondary 
file system is not IgniteHadoopIgfsSecondaryFileSystem.

commit fc48a8429a84ef6c87ed3225a218d7d3ae617e14
Author: vozerov-gridgain 
Date:   2016-01-08T07:48:42Z

Merge branch 'ignite-1.5.2' into ignite-1.5.3

commit 86740cefe212ed0f506d81056dd8e76de9a31e4f
Author: Ignite Teamcity 
Date:   2016-01-08T09:32:11Z

1.5.3-SNAPSHOT

commit 92229d2a6c6ef86772a62cb52b3aa07a55c99d89
Author: sboikov 
Date:   2016-01-13T05:56:34Z

ignite-2359 Added locking for files used by MarshallerContextImpl. (cherry 
picked from commit 1d8c4e2)

commit 2e4ce585d5f54502c6511d3425b1cd5fbf0a7f4f
Author: Ignite Teamcity 
Date:   2016-01-13T10:37:33Z

1.5.4-SNAPSHOT

commit 6e5f9f0c7d4c86773b1f0cd5c5a673acb58c86c2
Author: Denis Magda 
Date:   2016-01-13T11:42:27Z

Changed year to 2016 in Copyrights

commit 02dbcfd8ed2701a4f415c8871d0b8fd08bfa0583
Author: Alexey Goncharuk 
Date:   2016-01-13T13:47:32Z

IGNITE-2365 - Notify policy if swap or offheap is enabled and rebalanced 
entry was not preloaded.
IGNITE-2099 - Fixing custom collections.
This closes #396

commit 86c2ba2a601e82b824cf17422683e5398a4d8c7d
Author: sboikov 
Date:   2016-01-13T15:40:08Z

ignite-2350 Pass update notifier flag in discovery data (all cluster nodes 
will have the same notifier status as first cluster node)
(cherry picked from commit 7175a42)

commit e1a494df400fc37ca04e8d88d1cf20bca02607b4
Author: sboikov 
Date:   2016-01-14T11:16:33Z

Renamed fields to change fields write order (to preserve backward 
compatibility).
(cherry picked from commit 2a4adf5)

commit 09f978234b6062afa1e1658d5a6439365a856aca
Author: sboikov 
Date:   2016-01-14T11:42:44Z

Merge remote-tracking branch 'origin/ignite-1.5.4' into ignite-1.5.4

commit 30043e7892d0b52dc851ce5ec79c7eb3b7cc44fb
Author: Denis Magda 
Date:   2016-01-14T13:02:50Z

Added release notes

commit cc3db35925698f1670a8bf1c6a1830c0c9b51290
Author: vershov 
Date:   2016-01-14T14:21:56Z

IGNITE-2032 Unwind undeploys in preloader - Fixes #369.

Signed-off-by: Alexey Goncharuk 

commit a5c85ca7749ae90af2e4a29e2162713b480e40fa
Author: Valentin Kulichenko 
Date:   2016-01-15T06:58:41Z

Update notifier fixes

commit 8f32a29c5a7b28b7e1173582f4c7cef5b6d73b27
Author: Ignite Teamcity 
Date:   2016-01-15T11:00:29Z

1.5.4-SNAPSHOT

commit 6482dc80bf9cdf7aa4f592d9266c6745211b1c4c
Author: sboikov 
Date:   2016-01-15T12:15:

Re: Ignite 1.6 release timelines

[Pavel Tupitsyn]

Hi, there is one more .NET ticket to be merged to 1.6:
IGNITE-3112 .NET: Allow merging Spring XML config with .NET config

Other two 1.6 .NET tickets are documentation-related and have no code
changes: IGNITE-2963, IGNITE-3101

Thanks,
Pavel

On Wed, May 11, 2016 at 10:03 PM, Andrey Gura  wrote:

> Hi all,
>
> I think that JDBC driver improvements [1] should be included in 1.6
> release. I'm working on it.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-2382
>
> On Wed, May 11, 2016 at 1:54 PM, Igor Sapego  wrote:
>
> > Hi,
> >
> > I have also finished transactions API for the C++ [1] and
> > it is also going to be included to 1.6. It is already merged to
> > release branch.
> >
> > [1] - https://issues.apache.org/jira/browse/IGNITE-2805.
> >
> > Best Regards,
> > Igor
> >
> > On Wed, May 11, 2016 at 1:49 PM, Sergey Kozlov 
> > wrote:
> >
> > > The following issues found for 1.6 recently:
> > >
> > > IGNITE-3109 IgfsMapReduceExample fails ClassNotFoundException
> > > 
> > >  - critical
> > > IGNITE-3107 Help for tasks/events should be rephrased
> > > 
> > >  - trivial, doc issue
> > >
> > > On Wed, May 11, 2016 at 8:56 AM, Yakov Zhdanov 
> > > wrote:
> > >
> > > > Guys,
> > > >
> > > > I moved most of the tickets to 1.7 version.
> > > >
> > > > I had to leave the following tickets untouched (~80 tickets):
> > > > 1. labeled with - community important performance customer - Denis,
> > > > Vladimir and Val can you please review these tickets and move
> > non-urgent
> > > > ones. You can use query below
> > > > 2. with status "in progress". Please everyone having such tickets
> move
> > it
> > > > yourself or finish it in 1.6
> > > > 3. with status "patch available". Committers, please split the
> reviews
> > > and
> > > > let's include checked/tested fixes to 1.6. Others should be moved.
> > > >
> > > > Sam, can you please review and merge -
> > > > https://issues.apache.org/jira/browse/IGNITE-2744 - Optimize
> > > "unwindEvict"
> > > > call in GridCacheIoManager.processMessage().
> > > > 
> > > >
> > > > Query for p1:
> > > >
> > > > project = IGNITE AND fixVersion = 1.6 AND resolution = Unresolved AND
> > > > status not in ("Patch Available", "in progress") AND (labels in
> > > (community,
> > > > important, performance, perfomance, customer)) ORDER BY status DESC,
> > due
> > > > ASC, priority DESC, created ASC
> > > >
> > > > Thanks!
> > > >
> > > > --Yakov
> > > >
> > > > 2016-05-11 9:47 GMT+06:00 Dmitriy Setrakyan :
> > > >
> > > > > Igniters,
> > > > >
> > > > > I just did a search on 1.6 issues and looks like we have 293
> > unresolved
> > > > > issues for 1.6. Obviously we are not going to be fixing all of them
> > and
> > > > > most of them will have to be moved to 1.7.
> > > > >
> > > > > Yakov, given that you have most experience with Jira and have been
> > > > managing
> > > > > it before, do you mind moving the tickets? Here is the link to the
> > > > filter:
> > > > >
> > > > > http://bit.ly/24Mrddg
> > > > >
> > > > > Also, if anything needs to be addressed in 1.6, please list these
> > > tickets
> > > > > here, in this thread.
> > > > >
> > > > > Thanks,
> > > > > D.
> > > > >
> > > > > On Tue, May 10, 2016 at 6:00 AM, Pavel Tupitsyn <
> > > ptupit...@gridgain.com>
> > > > > wrote:
> > > > >
> > > > > > Dmitriy, yes, many of them do. I'll create 1.6 version on
> > > > > > apacheignite-net.readme.io and document them this week (task:
> > > > > > IGNITE-3101).
> > > > > >
> > > > > > Pavel.
> > > > > >
> > > > > > On Tue, May 10, 2016 at 3:52 PM, Dmitriy Setrakyan <
> > > > > dsetrak...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > Thanks Pavel, do any of these features require new
> documentation?
> > > > > > >
> > > > > > > On Tue, May 10, 2016 at 5:16 AM, Pavel Tupitsyn <
> > > > > ptupit...@gridgain.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi, here is a list of major .NET features included in 1.6
> (all
> > > > closed
> > > > > > and
> > > > > > > > merged):
> > > > > > > >
> > > > > > > > * LINQ Provider for SQL queries (IGNITE-1630)
> > > > > > > > * NuGet distribution (IGNITE-1626)
> > > > > > > > * C#, app.config and web.config configuration (instead of
> > Spring
> > > > XML)
> > > > > > > > (IGNITE-1906, IGNITE-2380)
> > > > > > > > * Atomic data structures (IGNITE-1563)
> > > > > > > > * Universal AnyCPU binaries (instead of separate x64/x86)
> > > > > (IGNITE-2694)
> > > > > > > > * Call Java services (IGNITE-2686)
> > > > > > > > * Java-based continuous query filters (IGNITE-2977)
> > > > > > > > * Mixed-cluster Compute (IGNITE-2621)
> > > > > > > > * Compute task cancellation (IGNITE-2228)
> > > > > > > > * Binary format compact footers (IGNITE-2702)
> > > > > > > > * Raw mode reflective serialization (IGNITE-1419)
> > > > > > > > * Automatic Java detection: no need for JAVA_HOME
> (IGNITE-2866)
> >

[jira] [Created] (IGNITE-3116) Cancel force key futures when node stops

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-3116:


 Summary: Cancel force key futures when node stops
 Key: IGNITE-3116
 URL: https://issues.apache.org/jira/browse/IGNITE-3116
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Semen Boikov
Assignee: Semen Boikov
 Fix For: 1.6


When node stops need cancel GridDhtForceKeysFutures (like all others cache 
futures) to prevent potential hangs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] ignite pull request: IGNITE-3112 .NET: Allow merging Spring XML co...

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

https://github.com/apache/ignite/pull/706

IGNITE-3112 .NET: Allow merging Spring XML config with .NET config



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ptupitsyn/ignite ignite-3112

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/706.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #706


commit 02adbf2ebf31f16c587ee003f9093e93414d940f
Author: Pavel Tupitsyn 
Date:   2016-05-11T14:43:04Z

IGNITE-3112 .NET: Allow merging Spring XML config with .NET config

commit 19c818316d6228d95064362235109638abfd9b6f
Author: Pavel Tupitsyn 
Date:   2016-05-11T14:58:01Z

wip

commit 98615d06461d2c51fdfdb3d6a2622f937883c1b6
Author: Pavel Tupitsyn 
Date:   2016-05-11T15:10:35Z

wip

commit 98c22d163039cabcf272090c6b9fa3cbb7a8e081
Author: Pavel Tupitsyn 
Date:   2016-05-11T15:31:13Z

wip

commit 235dc1647cf5c3dd43dfd3c2cc71223f2397b334
Author: Pavel Tupitsyn 
Date:   2016-05-11T15:35:58Z

Fixing tests

commit 891460fa8742482f0b658ec760dc372a07670851
Author: Pavel Tupitsyn 
Date:   2016-05-11T15:48:47Z

Tests wip

commit 7f143585e7d2776e0cbb5953c5f89d19649cdfcc
Author: Pavel Tupitsyn 
Date:   2016-05-11T15:59:57Z

all tests work

commit bd80f22fe012f220280bf6220274b24021f24b12
Author: Pavel Tupitsyn 
Date:   2016-05-11T16:12:59Z

Updated docs

commit 912f5f700e5c4ca17c10abe13dd04d8957fd0b6c
Author: Pavel Tupitsyn 
Date:   2016-05-12T07:34:39Z

Merge remote-tracking branch 'remotes/upstream/master' into ignite-3112




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: Improved JDBC error handling by consistent us...

[krosenvold]

GitHub user krosenvold opened a pull request:

https://github.com/apache/ignite/pull/705

Improved JDBC error handling by consistent usage of jdk7 try-with res…

…ources

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/krosenvold/ignite jdbcErrorHandling

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/705.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #705


commit 65122029195948d9ee905939a79dcf7e0379
Author: Kristian Rosenvold 
Date:   2016-05-12T07:02:09Z

Improved JDBC error handling by consistent usage of jdk7 try-with resources




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---