Re: Ignite 1.6 release timelines

2016-05-10 Thread Yakov Zhdanov
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
> > > > > > >> about mid or second half of May.
> > > > > > >>
> > > > > > >> --Yakov
> > > > > > >>
> > > > > > >> 2016-04-27 11:13 GMT+03:00 sssow :
> > > > > > >>
> > > > 

Re: Ignite 1.6 release timelines

2016-05-10 Thread 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 
> wrote:
>
> > Thanks Pavel, do any of these features require new documentation?
> >
> > On Tue, May 10, 2016 at 5:16 AM, Pavel Tupitsyn 
> > 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
> > > > > >> about mid or second half of May.
> > > > > >>
> > > > > >> --Yakov
> > > > > >>
> > > > > >> 2016-04-27 11:13 GMT+03:00 sssow :
> > > > > >>
> > > > > >> > Hi,
> > > > > >> > When will you release 1.6?
> > > > > >> > Thank you,
> > > > > >> >
> > > > > >> >
> > > > > >> >
> > > > > >> >
> > > > > >> > --
> > > > > >> > View this message in context:
> > > > > >> >
> > > > > >>
> > > > >
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-1-6-release-timelines-tp7388p8618.html
> > > > > >> > Sent from the Apache Ignite Developers mailing list archive at
> > > > > >> Nabble.com.
> > > > > >> >
> > > > > >>
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>


[GitHub] ignite pull request: IGNITE-3096: .NET Solution fixed.

2016-05-10 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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-3094: Default host now is empty.

2016-05-10 Thread asfgit
Github user asfgit closed the pull request at:

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


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

2016-05-10 Thread ascherbakoff
GitHub user ascherbakoff opened a pull request:

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

ignite-3098

Support any string in BinaryMarshaller

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

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

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

https://github.com/apache/ignite/pull/699.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 #699


commit 0ba23df485fa3456b682c3fd5064d37a07c979b4
Author: Aleksei Scherbakov 
Date:   2016-05-10T16:12:50Z

IGNITE-3098 Support any string in BinaryMarshaller

commit bc255d6025ab25ab4e85f8ed9905d04eb4a9bf62
Author: Aleksei Scherbakov 
Date:   2016-05-10T16:13:39Z

IGNITE-3098 Support any string in BinaryMarshaller




---
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-3105) .NET: ContinuousQueryAbstractTest.TestCallback fails sporadically

2016-05-10 Thread Pavel Tupitsyn (JIRA)
Pavel Tupitsyn created IGNITE-3105:
--

 Summary: .NET: ContinuousQueryAbstractTest.TestCallback fails 
sporadically
 Key: IGNITE-3105
 URL: https://issues.apache.org/jira/browse/IGNITE-3105
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 1.6
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.7


Failure rate is quite low, but there is certainly a problem. Try to run in a 
loop.

{code}
Test(s) failed.   Expected: 

  But was:  null

   at NUnit.Framework.Assert.That(Object actual, IResolveConstraint expression, 
String message, Object[] args)
   at 
Apache.Ignite.Core.Tests.Cache.Query.Continuous.ContinuousQueryAbstractTest.CheckCallbackSingle(Int32
 expKey, BinarizableEntry expOldVal, BinarizableEntry expVal, Int32 timeout) in 
c:\BuildAgent\work\c6bd605b1bad5b0f\modules\platforms\dotnet\Apache.Ignite.Core.Tests\Cache\Query\Continuous\ContinuousQueryAbstractTest.cs:line
 945
   at 
Apache.Ignite.Core.Tests.Cache.Query.Continuous.ContinuousQueryAbstractTest.CheckCallbackSingle(Int32
 expKey, BinarizableEntry expOldVal, BinarizableEntry expVal) in 
c:\BuildAgent\work\c6bd605b1bad5b0f\modules\platforms\dotnet\Apache.Ignite.Core.Tests\Cache\Query\Continuous\ContinuousQueryAbstractTest.cs:line
 926
   at 
Apache.Ignite.Core.Tests.Cache.Query.Continuous.ContinuousQueryAbstractTest.CheckCallback(Boolean
 loc) in 
c:\BuildAgent\work\c6bd605b1bad5b0f\modules\platforms\dotnet\Apache.Ignite.Core.Tests\Cache\Query\Continuous\ContinuousQueryAbstractTest.cs:line
 240
   at 
Apache.Ignite.Core.Tests.Cache.Query.Continuous.ContinuousQueryAbstractTest.TestCallback()
 in 
c:\BuildAgent\work\c6bd605b1bad5b0f\modules\platforms\dotnet\Apache.Ignite.Core.Tests\Cache\Query\Continuous\ContinuousQueryAbstractTest.cs:line
 199
--- Stderr: ---
Test started: ContinuousQueryAbstractTest.TestCallback
{code}



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


[jira] [Created] (IGNITE-3104) Add documentation for pluggable affinity functions

2016-05-10 Thread Denis Magda (JIRA)
Denis Magda created IGNITE-3104:
---

 Summary: Add documentation for pluggable affinity functions
 Key: IGNITE-3104
 URL: https://issues.apache.org/jira/browse/IGNITE-3104
 Project: Ignite
  Issue Type: Bug
Reporter: Denis Magda


Documentation must contain information at least on the following:
- puggability;
- Rendezvous affinity function and its parameters;
- Fair affinity function and its parameters.




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


[jira] [Created] (IGNITE-3103) No description in javadoc (kafka module)

2016-05-10 Thread Ilya Suntsov (JIRA)
Ilya Suntsov created IGNITE-3103:


 Summary: No description in javadoc (kafka module)
 Key: IGNITE-3103
 URL: https://issues.apache.org/jira/browse/IGNITE-3103
 Project: Ignite
  Issue Type: Bug
  Components: documentation
Affects Versions: 1.6
Reporter: Ilya Suntsov
Priority: Minor
 Fix For: 1.6


No description in javadoc for classes:
* org.apache.ignite.stream.kafka.connect
 * org.apache.ignite.stream.kafka.connect.serialization



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


[jira] [Created] (IGNITE-3102) .NET: Call user-defined constructor for IBinarizable objects

2016-05-10 Thread Pavel Tupitsyn (JIRA)
Pavel Tupitsyn created IGNITE-3102:
--

 Summary: .NET: Call user-defined constructor for IBinarizable 
objects
 Key: IGNITE-3102
 URL: https://issues.apache.org/jira/browse/IGNITE-3102
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn
 Fix For: 1.7


Currently we create user objects with FormatterServices.GetUninitializedObject 
and then call user-defined IBinarizable.ReadBinary method.

This is not convenient both for us and the user:
* FormatterServices.GetUninitializedObject is not a clean way of constructing 
objects
* User-defined constructor does not get called
* User types can't have readonly fields

For example, ISerializable mechanism does not have Read method; it calls 
user-defined constructor instead. We should provide similar mechanism.

To maintain compatibility, we may have to introduce a new interface with a 
single Write method, and call user-defined ctor on read.



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


Re: Ignite 1.6 release timelines

2016-05-10 Thread Pavel Tupitsyn
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 
wrote:

> Thanks Pavel, do any of these features require new documentation?
>
> On Tue, May 10, 2016 at 5:16 AM, Pavel Tupitsyn 
> 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
> > > > >> about mid or second half of May.
> > > > >>
> > > > >> --Yakov
> > > > >>
> > > > >> 2016-04-27 11:13 GMT+03:00 sssow :
> > > > >>
> > > > >> > Hi,
> > > > >> > When will you release 1.6?
> > > > >> > Thank you,
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> > --
> > > > >> > View this message in context:
> > > > >> >
> > > > >>
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-1-6-release-timelines-tp7388p8618.html
> > > > >> > Sent from the Apache Ignite Developers mailing list archive at
> > > > >> Nabble.com.
> > > > >> >
> > > > >>
> > > > >
> > > > >
> > > >
> > >
> >
>


[jira] [Created] (IGNITE-3101) .NET: Add 1.6 documentation on readme.io

2016-05-10 Thread Pavel Tupitsyn (JIRA)
Pavel Tupitsyn created IGNITE-3101:
--

 Summary: .NET: Add 1.6 documentation on readme.io
 Key: IGNITE-3101
 URL: https://issues.apache.org/jira/browse/IGNITE-3101
 Project: Ignite
  Issue Type: Task
  Components: documentation, platforms
Affects Versions: 1.6
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.6


All new features and changes should be documented:
{code}
project = IGNITE AND fixVersion = 1.6 AND status = closed AND summary ~ .net
{code}



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


Re: Ignite 1.6 release timelines

2016-05-10 Thread Dmitriy Setrakyan
Thanks Pavel, do any of these features require new documentation?

On Tue, May 10, 2016 at 5:16 AM, Pavel Tupitsyn 
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  >
> > 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 
> > > > wrote:
> > > >
> > > >> I think we are almost done with odbc support and I hope that we can
> > > >> release
> > > >> about mid or second half of May.
> > > >>
> > > >> --Yakov
> > > >>
> > > >> 2016-04-27 11:13 GMT+03:00 sssow :
> > > >>
> > > >> > Hi,
> > > >> > When will you release 1.6?
> > > >> > Thank you,
> > > >> >
> > > >> >
> > > >> >
> > > >> >
> > > >> > --
> > > >> > View this message in context:
> > > >> >
> > > >>
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-1-6-release-timelines-tp7388p8618.html
> > > >> > Sent from the Apache Ignite Developers mailing list archive at
> > > >> Nabble.com.
> > > >> >
> > > >>
> > > >
> > > >
> > >
> >
>


Re: Ignite 1.6 release timelines

2016-05-10 Thread Pavel Tupitsyn
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 
> wrote:
>
> > Resending (fixed links)
> >
> > On Wed, May 4, 2016 at 8:46 AM, Dmitriy Setrakyan  >
> > 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 
> > > wrote:
> > >
> > >> I think we are almost done with odbc support and I hope that we can
> > >> release
> > >> about mid or second half of May.
> > >>
> > >> --Yakov
> > >>
> > >> 2016-04-27 11:13 GMT+03:00 sssow :
> > >>
> > >> > Hi,
> > >> > When will you release 1.6?
> > >> > Thank you,
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > --
> > >> > View this message in context:
> > >> >
> > >>
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-1-6-release-timelines-tp7388p8618.html
> > >> > Sent from the Apache Ignite Developers mailing list archive at
> > >> Nabble.com.
> > >> >
> > >>
> > >
> > >
> >
>


[jira] [Created] (IGNITE-3099) Race condition on the order of events

2016-05-10 Thread Taras Ledkov (JIRA)
Taras Ledkov created IGNITE-3099:


 Summary: Race condition on the order of events
 Key: IGNITE-3099
 URL: https://issues.apache.org/jira/browse/IGNITE-3099
 Project: Ignite
  Issue Type: Bug
  Components: compute
Affects Versions: 1.6
Reporter: Taras Ledkov
Priority: Minor


The test org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest 
detects the irregular order of the JOB_FINISHED  & EVT_JOB_RESULTED events. 
In case async execution and  when the job worker is launched on separate thread 
the JOB_FINISHED event is recorded before EVT_JOB_RESULTED.
In this case a response is added to delayed queue.
See more: [GridTaskWorker.java
|https://github.com/apache/ignite/blob/01f12a238e075ae82232e4fa5e80ba109130e14c/modules/core/src/main/java/org/apache/ignite/internal/processors/task/GridTaskWorker.java#L732]







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


[GitHub] ignite pull request: Fix race condition on dynamic cache creation

2016-05-10 Thread tledkov-gridgain
GitHub user tledkov-gridgain opened a pull request:

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

Fix race condition on dynamic cache creation



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

$ git pull https://github.com/gridgain/apache-ignite 
ignite-tledkov-test-stabilization

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

https://github.com/apache/ignite/pull/697.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 #697


commit b7788ba23876ba270abfe553b02c1145b73fcd43
Author: tledkov-gridgain 
Date:   2016-05-05T08:43:40Z

stabilization: GridUnsafeDataOutputArraySizingSelfTest

commit 95bcf6c270cfcb00efcc9c13bfe7687e78b00eb3
Author: tledkov-gridgain 
Date:   2016-05-05T10:28:29Z

fix:GridMessageListenSelfTest

commit 5ce19e3ea87f2e8e2dcfa646dbee4236771f5200
Author: sboikov 
Date:   2016-05-05T13:45:29Z

Merge remote-tracking branch 'remotes/origin/master' into 
ignite-tledkov-test-stabilization

commit 098405dfe5315fff65ff3e056fc1ce9ea98aac60
Author: sboikov 
Date:   2016-05-05T13:49:45Z

Minor.

commit ffb68ee3beb5bb539b03b62d18cc321fcf04c9bc
Author: tledkov-gridgain 
Date:   2016-05-05T14:18:04Z

fix:GridTaskExecutionSelfTest

commit f3e0699f42bbb0b65781b686197a4c596ca9b422
Author: tledkov-gridgain 
Date:   2016-05-05T14:24:35Z

Merge branch 'ignite-tledkov-test-stabilization' of 
https://github.com/gridgain/apache-ignite into ignite-tledkov-test-stabilization

commit ad3ffebc222847ae2ea941c2fb8231d7e49e4f9c
Author: tledkov-gridgain 
Date:   2016-05-06T11:39:31Z

fix racing that is detected by GridCacheStoreManagerDeserializationTest




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