Re: Ignite Release Schedules - a suggestion

2016-05-17 Thread Dmitriy Setrakyan 
I actually think that the structure can be simpler and we should just
create a branch per release. Most likely, everything that is currently in
master should be released anyway, as we all work very hard on making sure
that master branch is always stable.

I think it does make sense to have a release at least once a quarter or
even more often. It looks like we are all in agreement here, no?

D.


On Tue, May 17, 2016 at 5:21 PM, Konstantin Boudnik  wrote:

> On Tue, May 17, 2016 at 01:09AM, endianignite wrote:
> > With regard to branch structure, I took some time to think and have a
> > suggestion.  Feel free to pick holes in it.
> >
> > Major feature releases would continue to have major version numbers:
> e.g.,
> > 1.7, 1.8, 2.x and so on.  Bug-fix releases would be minor releases: e.g.,
> > 1.7.1, 1.7.2, 1.7.x, etc.  Major releases get their own branch, although
> it
> > will probably be sensible to keep major features on their own JIRA branch
> > before being merged on to the release branch.  Once a major release "goes
> > gold", bug fixes would be continued on that release branch, and the next
> > major release would go to a new branch.  Bug fixes on the current "gold"
> > branch would be merged regularly in to the new major release branch,
> until
> > that new major release branch is ready to "go gold", at which point the
> > cycle would repeat, and new bug fixes would go on to the newly released
> > major release branch.
>
> How would you propagate bug fixed among releases in this case?
>
> > In the above scheme, master becomes deprecated, but there is still only
> one
> > major release branch that is "gold" at any one time.  We would not be in
> a
> > situation where 1.7.x was still being developed on once 1.8.x has been
> > released.
> >
> > <
> http://apache-ignite-developers.2346864.n4.nabble.com/file/n8939/Ignite_Source_Control.jpg
> >
> >
> >
> >
> > --
> > View this message in context:
> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Release-Schedules-a-suggestion-tp8867p8939.html
> > Sent from the Apache Ignite Developers mailing list archive at
> Nabble.com.
>

Re: Halfway to Ignite 1.6

2016-05-17 Thread Dmitriy Setrakyan 
Cos, I agree that it would be nice to merge IGNITE-1371
. However, if there are
more fixes and review comments, I would schedule it for the next release. I
guess Alexey, Anton, and Igor and better judges on it. Guys, can you please
comment?

As it was noted in another thread, we are way overdue for this release and
it already has plenty of new features and bug fixes. Let’s hope that we can
close out everything in PATCH_AVAILABLE status soon and send it out for a
vote.

D.

On Tue, May 17, 2016 at 5:20 PM, Konstantin Boudnik  wrote:

> You can still talk about the release even if it is in the final stages.
> What
> would be unfortunate is to miss some of the good features (like
> IGNITE-1371)
> just because of an arbitrary date of an even of some kind, which has no
> relevance to the project itself.
>
> For what it worth, rushing releases (ie a product company way of
> satisfying a
> time-boxed effort, aka PM-lust for scheduling) tends to end up in a
> substantially lower quality of the releases.
>
> Cos
>
> On Mon, May 16, 2016 at 05:09PM, Dmitriy Setrakyan wrote:
> > I will be presenting at IMC Summit next week in Bay Area, and it sure
> would
> > be nice to talk about 1.6 release and the new features. Would be great if
> > we could send it for vote on Wednesday morning. This would give a chance
> > for the vote to pass by EOD on Friday, if everything is OK.
> >
> > D.
> >
> > On Mon, May 16, 2016 at 7:50 AM, Sergey Kozlov 
> wrote:
> >
> > > Guys
> > >
> > > I'm concerned that we postpone once again the date of code freeze. It
> > > shifts dates of testing and release and it seems we won't be able to
> send
> > > to voting this week
> > >
> > > On Mon, May 16, 2016 at 5:43 PM, Anton Vinogradov <
> > > avinogra...@gridgain.com>
> > > wrote:
> > >
> > > > Thanks everyone for checking!
> > > >
> > > > Only 8 tickets left!
> > > >
> > > > Seems contributors still need 1-2 days to pass codereview and merge
> final
> > > > changes.
> > > > We postponed code freeze till Wednesday UTC 19-00. Hope, this will
> be the
> > > > last time.
> > > >
> > > > On Mon, May 16, 2016 at 3:56 PM, Anton Vinogradov <
> > > > avinogra...@gridgain.com>
> > > > wrote:
> > > >
> > > > > Igniters,
> > > > >
> > > > > We still have 32 issues with status "In Progress" or "Patch
> Available"
> > > > and
> > > > > fixVersion = 1.6.
> > > > > Full list
> > > > > <
> > > >
> > >
> https://issues.apache.org/jira/issues/?filter=-1=(status%20%3D%20%22In%20Progress%22%20or%20status%20%3D%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%201.6%20and%20project%20%3D%20Ignite
> > > >
> > > > can
> > > > > be found here.
> > > > >
> > > > > Please change fixVersion for issues can't be resolved at 1.6 to
> 1.7,
> > > and
> > > > > close other issues before code freeze.
> > > > >
> > > > > On Mon, May 16, 2016 at 12:57 AM, Andrey Gura 
> > > > wrote:
> > > > >
> > > > >> Guys,
> > > > >>
> > > > >> I've finished with improvements for JDBC drivers [1]. I hope
> somebody
> > > > will
> > > > >> review and merge it before code freeze.
> > > > >> Also I created issue related with query execution from client
> nodes
> > > [2].
> > > > >> It
> > > > >> affects system behaviour that related with [1] and [3]. I don't
> think
> > > > that
> > > > >> it is critical because walk around exists.
> > > > >>
> > > > >> [1] https://issues.apache.org/jira/browse/IGNITE-2382
> > > > >> [2] https://issues.apache.org/jira/browse/IGNITE-3136
> > > > >> [3] https://issues.apache.org/jira/browse/IGNITE-2455
> > > > >>
> > > > >> On Fri, May 13, 2016 at 6:24 PM, Anton Vinogradov 
> > > > wrote:
> > > > >>
> > > > >> > Igniters,
> > > > >> >
> > > > >> > We postponed code freeze till monday UTC 19-00.
> > > > >> >
> > > > >> > On Thu, May 12, 2016 at 1:48 PM, Anton Vinogradov <
> a...@apache.org>
> > > > >> wrote:
> > > > >> >
> > > > >> > > Typo fix:
> > > > >> > > Pushes to ignite-1.6 are allowed till Friday (*May *13) 19:00
> UTC.
> > > > >> > >
> > > > >> > >
> > > > >> > >
> > > > >> > > On Thu, May 12, 2016 at 1:41 PM, Anton Vinogradov <
> a...@apache.org>
> > > > >> wrote:
> > > > >> > >
> > > > >> > >> Igniters,
> > > > >> > >>
> > > > >> > >> Ignite 1.6 almost ready to be finally tested.
> > > > >> > >>
> > > > >> > >> Branch ignite-1.6 now contains all changes scheduled for 1.6.
> > > > >> > >>
> > > > >> > >> In case you want to add something else to this release,
> please
> > > note
> > > > >> that
> > > > >> > >> pushes to ignite-1.6 allowed till Friday (Aug 13) 19:00 UTC.
> > > > >> > >> After that date only fixes will allowed.
> > > > >> > >>
> > > > >> > >> On Fri, May 6, 2016 at 4:18 PM, Anton Vinogradov <
> a...@apache.org>
> > > > >> wrote:
> > > > >> > >>
> > > > >> > >>> Igniters,
> > > > >> > >>>
> > > > >> > >>> We're going to release Ignite 1.6 in the nearest future.
> > > > >> > >>> Branch ignite-1.6 was created and

Re: Ignite Release Schedules - a suggestion

2016-05-17 Thread Konstantin Boudnik 
On Tue, May 17, 2016 at 01:09AM, endianignite wrote:
> With regard to branch structure, I took some time to think and have a
> suggestion.  Feel free to pick holes in it.
> 
> Major feature releases would continue to have major version numbers: e.g.,
> 1.7, 1.8, 2.x and so on.  Bug-fix releases would be minor releases: e.g.,
> 1.7.1, 1.7.2, 1.7.x, etc.  Major releases get their own branch, although it
> will probably be sensible to keep major features on their own JIRA branch
> before being merged on to the release branch.  Once a major release "goes
> gold", bug fixes would be continued on that release branch, and the next
> major release would go to a new branch.  Bug fixes on the current "gold"
> branch would be merged regularly in to the new major release branch, until
> that new major release branch is ready to "go gold", at which point the
> cycle would repeat, and new bug fixes would go on to the newly released
> major release branch.

How would you propagate bug fixed among releases in this case?

> In the above scheme, master becomes deprecated, but there is still only one
> major release branch that is "gold" at any one time.  We would not be in a
> situation where 1.7.x was still being developed on once 1.8.x has been
> released.
> 
> 
>  
> 
> 
> 
> --
> View this message in context: 
> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Release-Schedules-a-suggestion-tp8867p8939.html
> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.


signature.asc
Description: Digital signature

Re: Halfway to Ignite 1.6

2016-05-17 Thread Konstantin Boudnik 
You can still talk about the release even if it is in the final stages. What
would be unfortunate is to miss some of the good features (like IGNITE-1371)
just because of an arbitrary date of an even of some kind, which has no
relevance to the project itself.

For what it worth, rushing releases (ie a product company way of satisfying a
time-boxed effort, aka PM-lust for scheduling) tends to end up in a
substantially lower quality of the releases.

Cos

On Mon, May 16, 2016 at 05:09PM, Dmitriy Setrakyan wrote:
> I will be presenting at IMC Summit next week in Bay Area, and it sure would
> be nice to talk about 1.6 release and the new features. Would be great if
> we could send it for vote on Wednesday morning. This would give a chance
> for the vote to pass by EOD on Friday, if everything is OK.
> 
> D.
> 
> On Mon, May 16, 2016 at 7:50 AM, Sergey Kozlov  wrote:
> 
> > Guys
> >
> > I'm concerned that we postpone once again the date of code freeze. It
> > shifts dates of testing and release and it seems we won't be able to send
> > to voting this week
> >
> > On Mon, May 16, 2016 at 5:43 PM, Anton Vinogradov <
> > avinogra...@gridgain.com>
> > wrote:
> >
> > > Thanks everyone for checking!
> > >
> > > Only 8 tickets left!
> > >
> > > Seems contributors still need 1-2 days to pass codereview and merge final
> > > changes.
> > > We postponed code freeze till Wednesday UTC 19-00. Hope, this will be the
> > > last time.
> > >
> > > On Mon, May 16, 2016 at 3:56 PM, Anton Vinogradov <
> > > avinogra...@gridgain.com>
> > > wrote:
> > >
> > > > Igniters,
> > > >
> > > > We still have 32 issues with status "In Progress" or "Patch Available"
> > > and
> > > > fixVersion = 1.6.
> > > > Full list
> > > > <
> > >
> > https://issues.apache.org/jira/issues/?filter=-1=(status%20%3D%20%22In%20Progress%22%20or%20status%20%3D%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%201.6%20and%20project%20%3D%20Ignite
> > >
> > > can
> > > > be found here.
> > > >
> > > > Please change fixVersion for issues can't be resolved at 1.6 to 1.7,
> > and
> > > > close other issues before code freeze.
> > > >
> > > > On Mon, May 16, 2016 at 12:57 AM, Andrey Gura 
> > > wrote:
> > > >
> > > >> Guys,
> > > >>
> > > >> I've finished with improvements for JDBC drivers [1]. I hope somebody
> > > will
> > > >> review and merge it before code freeze.
> > > >> Also I created issue related with query execution from client nodes
> > [2].
> > > >> It
> > > >> affects system behaviour that related with [1] and [3]. I don't think
> > > that
> > > >> it is critical because walk around exists.
> > > >>
> > > >> [1] https://issues.apache.org/jira/browse/IGNITE-2382
> > > >> [2] https://issues.apache.org/jira/browse/IGNITE-3136
> > > >> [3] https://issues.apache.org/jira/browse/IGNITE-2455
> > > >>
> > > >> On Fri, May 13, 2016 at 6:24 PM, Anton Vinogradov 
> > > wrote:
> > > >>
> > > >> > Igniters,
> > > >> >
> > > >> > We postponed code freeze till monday UTC 19-00.
> > > >> >
> > > >> > On Thu, May 12, 2016 at 1:48 PM, Anton Vinogradov 
> > > >> wrote:
> > > >> >
> > > >> > > Typo fix:
> > > >> > > Pushes to ignite-1.6 are allowed till Friday (*May *13) 19:00 UTC.
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > > On Thu, May 12, 2016 at 1:41 PM, Anton Vinogradov 
> > > >> 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=projectOverview_IgniteTests=ignite-1.6
> > > >> > >>>
> > > >> > >>> So, feel free to start investigations and fix issues :)
> > > >> > >>>
> > > >> > >>
> > > >> > >>
> > > >> > >
> > > >> >
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> Andrey Gura
> > > >> GridGain Systems, Inc.
> > > >> www.gridgain.com
> > > >>
> > > >
> >

Re: 1.5.0.final is breaking packaging: osgi dependency is non-existent

2016-05-17 Thread Konstantin Boudnik 
On Mon, May 16, 2016 at 04:09AM, Andrey Kornev wrote:
> I'd love to elaborate, Konstantin, but I can't. I have no experience with
> the package management tools, neither yum nor rpm.

Understood, and that's ok. I am rather trying to understand where these could
possible be coming from.

> BTW, those Spring dependencies are optional, as far as I know. They are only
> required if Spring framework is used by the application (Spring XML
> configuration, for example).

Well, in case of HDFS and Spark accelerators Spring is used and packed all
along. Are you saying I would need to pick up some OSGI libs as well? If so,
where they could be found after the build is done? I wasn't able to spot them,
unfortunately.

Thanks!
  Cos

> > Date: Sun, 15 May 2016 10:20:57 -0400
> > From: c...@apache.org
> > To: dev@ignite.apache.org
> > Subject: Re: 1.5.0.final is breaking packaging: osgi dependency is 
> > non-existent
> > 
> > Thanks for checking out Andrey. Do you mind to elaborate on 'something'? The
> > way I see it, is that rpmbuilder performs certain checks to declare the
> > package dependencies, and the osgi once are popping up from somewhere. Which
> > wasn't the case before OSGI was added. Which lead me to believe that the 
> > issue
> > might be rooting from missing jars or something similar. Hence, my this 
> > email
> > thread.
> > 
> > Were my assumptions incorrect.
> > Thanks
> >   Cos
> > 
> > On Thu, May 05, 2016 at 04:39AM, Andrey Kornev wrote:
> > > Anton,
> > > 
> > > My first impression after having taken a look at bigtop's JIRA ticket is
> > > that the issue is not so much with OSGi per se, but rather it has 
> > > something
> > > to do with Ignite's HDFS accelerator yum packaging.
> > > 
> > > Regards
> > > Andrey
> > > 
> > > > Date: Thu, 5 May 2016 13:55:26 +0300
> > > > Subject: Re: 1.5.0.final is breaking packaging: osgi dependency is 
> > > > non-existent
> > > > From: avinogra...@gridgain.com
> > > > To: dev@ignite.apache.org
> > > > 
> > > > Igniters,
> > > > 
> > > > Issue is critical for Bigtop project.
> > > > In case someone familiar with OSGI please have a look.
> > > > 
> > > > On Wed, May 4, 2016 at 11:15 AM, Anton Vinogradov 
> > > > 
> > > > wrote:
> > > > 
> > > > > Roman, Raul,
> > > > >
> > > > > As far as I remember you're familiar with OSGI. Could you please have 
> > > > > a
> > > > > look at this?
> > > > >
> > > > > On Wed, May 4, 2016 at 6:09 AM, Konstantin Boudnik 
> > > > > wrote:
> > > > >
> > > > >> Hey guys
> > > > >>
> > > > >> For your information: adding osgi into the product is breaking the
> > > > >> dependency matrix of the bigtop packages. For more info see
> > > > >> https://issues.apache.org/jira/browse/BIGTOP-2421
> > > > >>
> > > > >> --
> > > > >> Take care,
> > > > >> Cos
> > > > >> 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
> > > > >> Cos' pubkey: http://people.apache.org/~cos/cos.asc
> > > > >>
> > > > >>   Wisdom of the hour 
> > > > >>
> > > > >>
> > > > >
> > > 
> 


signature.asc
Description: Digital signature

[jira] [Created] (IGNITE-3155) visorcmd: "open -d" doesn't work

2016-05-17 Thread Vasilisa Sidorova (JIRA) 
Vasilisa  Sidorova created IGNITE-3155:
--

 Summary: visorcmd: "open -d" doesn't work 
 Key: IGNITE-3155
 URL: https://issues.apache.org/jira/browse/IGNITE-3155
 Project: Ignite
  Issue Type: Bug
  Components: visor
Affects Versions: 1.6
 Environment: Ubuntu 14.04, Apache Ignite 1.6.0
Reporter: Vasilisa  Sidorova


-
DESCRIPTION
-
When user try to connect to the grid with default config by command "open -d" 
nothing happens
-
STEPS FOR REPRODUCE
-
# Run node from IGNITE_HOME with default config (./config/default-config.xml) 
by command "./bin/ignite.sh -v"
# Run ignitevisorcmd.sh
# Connect visor to the grid by the command "open -d" 
# Type "node"
-
ACTUAL RESULT
-
# Topology is empty
-
EXPECTED RESULT
-
# Message "Detailed statistics (y/n) [n]:" is presented
-
ADDITIONAL INFO
-
# Reproducible if visorcmd is started before node
# If the next step for presented scenario will be run node by command 
{noformat}
./bin/ignite.sh -v ./examples/config/example-ignite.xml
{noformat}
Then topology will not be empty yet. But if scenario is:
** run node by command "./bin/ignite.sh -v ./examples/config/example-ignite.xml"
** run ignitevisorcmd.sh
** connect to the grid by the command "open -d" 
** type "node"
the result will be the same - topology is empty.




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

Re: Multiple failover SPI

2016-05-17 Thread Valentin Kulichenko 
Vasiliy,

You can specify failover SPI to use for a particular task via
@ComputeTaskSpis annotation. If there is no annotation, the first SPI in
the list will be used.

-Val

On Tue, May 17, 2016 at 12:02 AM, Vasiliy Sisko  wrote:

> Hello Igniters.
>
>
> I noticed that a grid configuration contain an array of failover SPIs, but
> using of several failover SPIs is not described in a documentation.
>
>
> Can anyone provide an example how to configure several falover SPI in one
> grid?
>
> --
> Vasiliy Sisko
> GridGain Systems
> www.gridgain.com
>

Re: Ignite 1.6 release timelines

2016-05-17 Thread Alexey Kuznetsov 
First version of Web Console merged to ignite-1.6.

On Tue, May 17, 2016 at 9:31 PM, Pavel Tupitsyn 
wrote:

> All done from .NET side as well.
>
> On Tue, May 17, 2016 at 5:28 PM, Denis Magda  wrote:
>
> > Hi,
> >
> > Reviewed and merged IGNITE-2394 (Cache loading from storage is called on
> > client nodes).
> > Finalized and merged IGNITE-3098 (UTF-16 surrogate pairs are not properly
> > serialized by BinaryMarshaller).
> >
> > These are last things from my side for 1.6.
> >
> > —
> > Denis
> >
> > > On May 17, 2016, at 11:09 AM, Pavel Tupitsyn 
> > wrote:
> > >
> > > Hi,
> > >
> > > Please note that documentation tickets do not hold the release
> > (IGNITE-3101
> > > and subtasks).
> > > Other than that, in .NET, recently emerged 'IGNITE-3139 UTF surrogates'
> > is
> > > expected to be merged today.
> > >
> > > Pavel.
> > >
> > >
> > > On Tue, May 17, 2016 at 10:20 AM, Semyon Boikov 
> > > wrote:
> > >
> > >> In 1.6 we implemented 'late affinity assignment' mode (see
> > >> https://issues.apache.org/jira/browse/IGNITE-324 and
> > >> IgniteConfiguration.isLateAffinityAssignment)
> > >>
> > >> On Mon, May 16, 2016 at 7:03 PM, Alexey Kuznetsov <
> > akuznet...@gridgain.com
> > >>>
> > >> wrote:
> > >>
> > >>> https://issues.apache.org/jira/browse/IGNITE-2832
> > >>> "CacheJdbcPojoStoreFactory.dataSource property should be replaced
> with
> > >>> Factory"
> > >>> Reviewed by Semen and merged into ignite-1.6
> > >>>
> > >>>
> > >>> On Mon, May 16, 2016 at 10:56 PM, Igor Sapego 
> > >>> wrote:
> > >>>
> >  Hi, here is a list of major C++ features included in 1.6:
> > 
> >  * ODBC driver for Ignite (IGNITE-1786)
> >  * Transactions API for CPP client (IGNITE-2805)
> >  * Simplified Autotools build process (IGNITE-2823)
> >  * Date and Timestamp types implementation (IGNITE-)
> > 
> >  Best Regards,
> >  Igor
> > 
> >  On Fri, May 13, 2016 at 4:10 PM, Artem Shutak  >
> >  wrote:
> > 
> > > I've finished with IGNITE-2959 Ignite JTA and WebSphere Application
> >  Server
> > > 8.5.5  and has
> > >> been
> > > merged to 1.6.
> > >
> > > Also, I'm going to finish the following issues before 1.6 relase
> > >> (they
> >  all
> > > almost done/under review/waiting for TC):
> > > [1] IGNITE-3056 Service implementation class is required even if
> it's
> > >>> not
> > > expected to be deployed on current node
> > > 
> > > [2] IGNITE-2921 ScanQueries over local partitions are not optimal
> > > 
> > > [3] IGNITE-2899 BinaryObject is deserialized before getting passed
> to
> > > CacheInterceptor <
> https://issues.apache.org/jira/browse/IGNITE-2899>
> > >
> > > Thanks,
> > > -- Artem --
> > >
> > > On Fri, May 13, 2016 at 5:26 AM, Dmitriy Setrakyan <
> >  dsetrak...@apache.org>
> > > wrote:
> > >
> > >> On Thu, May 12, 2016 at 9:08 AM, Alexey Kuznetsov <
> > > akuznet...@gridgain.com
> > >>>
> > >> 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 <
> > >>> isap...@gridgain.com
> > >
> > >>> 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 <
> > >> ptupit...@gridgain.com
> > 
> > > wrote:
> > >
> > >> And one more .NET ticket: IGNITE-3118 .NET:
> > >> CacheConfiguration.EvictionPolicy
> > >>
> > >> On Thu, May 12, 2016 at 12:20 PM, Denis Magda <
> > > dma...@gridgain.com>
> > >

Re: Contribution merged: IGNITE-2394 Cache loading from storage is called on client nodes

2016-05-17 Thread Alper Tekinalp 
Hi Denis,

I want to thank you and all devs for your support.

Will try to contribute more.

Best regards.

2016-05-17 17:26 GMT+03:00 Denis Magda :
> Alper, let me thank you from the community side for the contribution you’ve 
> done.
>
> The contribution fixed an unpleasant issue when loading from a cache store 
> was triggered on a client side (for non local caches) causing useless 
> transferring of data from a storage to the client side.
>
> Waiting for more contributions from your side.
>
> Regards,
> Denis



-- 
Alper Tekinalp
atekinalp.blogspot.com

[GitHub] ignite pull request: IGNITE-3139 .Net: UTF-16 surrogate symbols ar...

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

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


---
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-3140: Added test for UTF-8 string form...

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

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


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

2016-05-17 Thread Pavel Tupitsyn 
All done from .NET side as well.

On Tue, May 17, 2016 at 5:28 PM, Denis Magda  wrote:

> Hi,
>
> Reviewed and merged IGNITE-2394 (Cache loading from storage is called on
> client nodes).
> Finalized and merged IGNITE-3098 (UTF-16 surrogate pairs are not properly
> serialized by BinaryMarshaller).
>
> These are last things from my side for 1.6.
>
> —
> Denis
>
> > On May 17, 2016, at 11:09 AM, Pavel Tupitsyn 
> wrote:
> >
> > Hi,
> >
> > Please note that documentation tickets do not hold the release
> (IGNITE-3101
> > and subtasks).
> > Other than that, in .NET, recently emerged 'IGNITE-3139 UTF surrogates'
> is
> > expected to be merged today.
> >
> > Pavel.
> >
> >
> > On Tue, May 17, 2016 at 10:20 AM, Semyon Boikov 
> > wrote:
> >
> >> In 1.6 we implemented 'late affinity assignment' mode (see
> >> https://issues.apache.org/jira/browse/IGNITE-324 and
> >> IgniteConfiguration.isLateAffinityAssignment)
> >>
> >> On Mon, May 16, 2016 at 7:03 PM, Alexey Kuznetsov <
> akuznet...@gridgain.com
> >>>
> >> wrote:
> >>
> >>> https://issues.apache.org/jira/browse/IGNITE-2832
> >>> "CacheJdbcPojoStoreFactory.dataSource property should be replaced with
> >>> Factory"
> >>> Reviewed by Semen and merged into ignite-1.6
> >>>
> >>>
> >>> On Mon, May 16, 2016 at 10:56 PM, Igor Sapego 
> >>> wrote:
> >>>
>  Hi, here is a list of major C++ features included in 1.6:
> 
>  * ODBC driver for Ignite (IGNITE-1786)
>  * Transactions API for CPP client (IGNITE-2805)
>  * Simplified Autotools build process (IGNITE-2823)
>  * Date and Timestamp types implementation (IGNITE-)
> 
>  Best Regards,
>  Igor
> 
>  On Fri, May 13, 2016 at 4:10 PM, Artem Shutak 
>  wrote:
> 
> > I've finished with IGNITE-2959 Ignite JTA and WebSphere Application
>  Server
> > 8.5.5  and has
> >> been
> > merged to 1.6.
> >
> > Also, I'm going to finish the following issues before 1.6 relase
> >> (they
>  all
> > almost done/under review/waiting for TC):
> > [1] IGNITE-3056 Service implementation class is required even if it's
> >>> not
> > expected to be deployed on current node
> > 
> > [2] IGNITE-2921 ScanQueries over local partitions are not optimal
> > 
> > [3] IGNITE-2899 BinaryObject is deserialized before getting passed to
> > CacheInterceptor 
> >
> > Thanks,
> > -- Artem --
> >
> > On Fri, May 13, 2016 at 5:26 AM, Dmitriy Setrakyan <
>  dsetrak...@apache.org>
> > wrote:
> >
> >> On Thu, May 12, 2016 at 9:08 AM, Alexey Kuznetsov <
> > akuznet...@gridgain.com
> >>>
> >> 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 <
> >>> isap...@gridgain.com
> >
> >>> 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 <
> >> ptupit...@gridgain.com
> 
> > wrote:
> >
> >> And one more .NET ticket: IGNITE-3118 .NET:
> >> CacheConfiguration.EvictionPolicy
> >>
> >> On Thu, May 12, 2016 at 12:20 PM, Denis Magda <
> > dma...@gridgain.com>
> > 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

Re: Ignite 1.6 release timelines

2016-05-17 Thread Denis Magda 
Hi,

Reviewed and merged IGNITE-2394 (Cache loading from storage is called on client 
nodes).
Finalized and merged IGNITE-3098 (UTF-16 surrogate pairs are not properly 
serialized by BinaryMarshaller).

These are last things from my side for 1.6.

—
Denis

> On May 17, 2016, at 11:09 AM, Pavel Tupitsyn  wrote:
> 
> Hi,
> 
> Please note that documentation tickets do not hold the release (IGNITE-3101
> and subtasks).
> Other than that, in .NET, recently emerged 'IGNITE-3139 UTF surrogates' is
> expected to be merged today.
> 
> Pavel.
> 
> 
> On Tue, May 17, 2016 at 10:20 AM, Semyon Boikov 
> wrote:
> 
>> In 1.6 we implemented 'late affinity assignment' mode (see
>> https://issues.apache.org/jira/browse/IGNITE-324 and
>> IgniteConfiguration.isLateAffinityAssignment)
>> 
>> On Mon, May 16, 2016 at 7:03 PM, Alexey Kuznetsov >> 
>> wrote:
>> 
>>> https://issues.apache.org/jira/browse/IGNITE-2832
>>> "CacheJdbcPojoStoreFactory.dataSource property should be replaced with
>>> Factory"
>>> Reviewed by Semen and merged into ignite-1.6
>>> 
>>> 
>>> On Mon, May 16, 2016 at 10:56 PM, Igor Sapego 
>>> wrote:
>>> 
 Hi, here is a list of major C++ features included in 1.6:
 
 * ODBC driver for Ignite (IGNITE-1786)
 * Transactions API for CPP client (IGNITE-2805)
 * Simplified Autotools build process (IGNITE-2823)
 * Date and Timestamp types implementation (IGNITE-)
 
 Best Regards,
 Igor
 
 On Fri, May 13, 2016 at 4:10 PM, Artem Shutak 
 wrote:
 
> I've finished with IGNITE-2959 Ignite JTA and WebSphere Application
 Server
> 8.5.5  and has
>> been
> merged to 1.6.
> 
> Also, I'm going to finish the following issues before 1.6 relase
>> (they
 all
> almost done/under review/waiting for TC):
> [1] IGNITE-3056 Service implementation class is required even if it's
>>> not
> expected to be deployed on current node
> 
> [2] IGNITE-2921 ScanQueries over local partitions are not optimal
> 
> [3] IGNITE-2899 BinaryObject is deserialized before getting passed to
> CacheInterceptor 
> 
> Thanks,
> -- Artem --
> 
> On Fri, May 13, 2016 at 5:26 AM, Dmitriy Setrakyan <
 dsetrak...@apache.org>
> wrote:
> 
>> On Thu, May 12, 2016 at 9:08 AM, Alexey Kuznetsov <
> akuznet...@gridgain.com
>>> 
>> 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 <
>>> isap...@gridgain.com
> 
>>> 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 <
>> ptupit...@gridgain.com
 
> wrote:
> 
>> And one more .NET ticket: IGNITE-3118 .NET:
>> CacheConfiguration.EvictionPolicy
>> 
>> On Thu, May 12, 2016 at 12:20 PM, Denis Magda <
> dma...@gridgain.com>
> 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 <
> yzhda...@apache.org
>>> 
>> wrote:
 
 Guys,
 
 I moved most of the tickets to 1.7 version.
 
 I had to

[jira] [Created] (IGNITE-3154) More efficient field lookup in binary protocol.

2016-05-17 Thread Vladimir Ozerov (JIRA) 
Vladimir Ozerov created IGNITE-3154:
---

 Summary: More efficient field lookup in binary protocol.
 Key: IGNITE-3154
 URL: https://issues.apache.org/jira/browse/IGNITE-3154
 Project: Ignite
  Issue Type: Task
  Components: general
Affects Versions: 1.5.0.final
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
Priority: Critical
 Fix For: 1.7


*Problem*
Currently creation of binary field is performed as follows: 
{{BinaryObject.type().field(...)}}. Call to {{BinaryObject.type()}} is pretty 
expensive as it requires metadata lookup. Interesting thing is that subsequent 
call to {{BinaryType.field()}} doesn't require metadata at all. 

*Solution*
Implement lazy metadata load for this case.



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

[GitHub] ignite pull request: IGNITE-3004 Added variations tests.

2016-05-17 Thread ntikhonov 
GitHub user ntikhonov opened a pull request:

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

IGNITE-3004 Added variations tests.



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

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

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

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


commit aac85f1dee54a1eb0e3df570f0b515590076a4a0
Author: nikolay_tikhonov 
Date:   2016-05-17T12:46:21Z

IGNITE-3004 Added variations tests.




---
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-3153) TcpDiscoveryZookeeperIpFinder doesn't properly handle client reconnections

2016-05-17 Thread Valentin Kulichenko (JIRA) 
Valentin Kulichenko created IGNITE-3153:
---

 Summary: TcpDiscoveryZookeeperIpFinder doesn't properly handle 
client reconnections
 Key: IGNITE-3153
 URL: https://issues.apache.org/jira/browse/IGNITE-3153
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.5.0.final
Reporter: Valentin Kulichenko
 Fix For: 1.7


The exception below is possible when client reconnects and ZooKeeper IP finder 
is used. Most likely this is caused by the fact that {{initGuard}} is flipped 
back to {{false}} when the context is destroyed and new curator instance is not 
created during the reconnect.

This should be fixed and test coverage for this scenario should be improved.



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

[jira] [Created] (IGNITE-3152) Client node's addresses are registered in IP finder

2016-05-17 Thread Valentin Kulichenko (JIRA) 
Valentin Kulichenko created IGNITE-3152:
---

 Summary: Client node's addresses are registered in IP finder
 Key: IGNITE-3152
 URL: https://issues.apache.org/jira/browse/IGNITE-3152
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.5.0.final
Reporter: Valentin Kulichenko
 Fix For: 1.7
 Attachments: Test.java

Currently client node register its addresses in IP finder and never deregisters 
them. Also looks like coordinator address is also not removed.

The simple test that shows this behavior is attached.



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

[jira] [Created] (IGNITE-3150) Update C++ documentation on readme.io

2016-05-17 Thread Igor Sapego (JIRA) 
Igor Sapego created IGNITE-3150:
---

 Summary: Update C++ documentation on readme.io
 Key: IGNITE-3150
 URL: https://issues.apache.org/jira/browse/IGNITE-3150
 Project: Ignite
  Issue Type: Task
  Components: documentation, platforms
Affects Versions: 1.5.0.final
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 1.6


C++ documentation should be updated for 1.6. We need to add new version, update 
building information and add section with Transaction API.



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

[jira] [Created] (IGNITE-3149) IGFS: Simplify default configuration.

2016-05-17 Thread Vladimir Ozerov (JIRA) 
Vladimir Ozerov created IGNITE-3149:
---

 Summary: IGFS: Simplify default configuration.
 Key: IGNITE-3149
 URL: https://issues.apache.org/jira/browse/IGNITE-3149
 Project: Ignite
  Issue Type: Task
  Components: IGFS
Affects Versions: 1.5.0.final
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
Priority: Critical
 Fix For: 1.6


Currently default-config.xml shipped with Hadoop module is overly complex and 
use deprecated properties (secondary FS). 

We need to simplify it and make more "recent".



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

[GitHub] ignite pull request: Ignite tledkov test stabilization

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

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

Ignite tledkov test stabilization



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/725.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 #725


commit ef904c789e50ebab7d2a64b03a7ff29faee2d687
Author: tledkov-gridgain 
Date:   2016-05-17T08:42:49Z

add debug print

commit 5106bd5266b6d3eca45b6f07317f8ab5293916e8
Author: tledkov-gridgain 
Date:   2016-05-17T08:55:11Z

IgniteSourceTask stabilization




---
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 tledkov test stabilization

2016-05-17 Thread tledkov-gridgain 
Github user tledkov-gridgain closed the pull request at:

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


---
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 Release Schedules - a suggestion

2016-05-17 Thread endianignite 
With regard to branch structure, I took some time to think and have a
suggestion.  Feel free to pick holes in it.

Major feature releases would continue to have major version numbers: e.g.,
1.7, 1.8, 2.x and so on.  Bug-fix releases would be minor releases: e.g.,
1.7.1, 1.7.2, 1.7.x, etc.  Major releases get their own branch, although it
will probably be sensible to keep major features on their own JIRA branch
before being merged on to the release branch.  Once a major release "goes
gold", bug fixes would be continued on that release branch, and the next
major release would go to a new branch.  Bug fixes on the current "gold"
branch would be merged regularly in to the new major release branch, until
that new major release branch is ready to "go gold", at which point the
cycle would repeat, and new bug fixes would go on to the newly released
major release branch.

In the above scheme, master becomes deprecated, but there is still only one
major release branch that is "gold" at any one time.  We would not be in a
situation where 1.7.x was still being developed on once 1.8.x has been
released.


 



--
View this message in context: 
http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Release-Schedules-a-suggestion-tp8867p8939.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

[GitHub] ignite pull request: Ignite tledkov test stabilization

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

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

Ignite tledkov test stabilization



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/724.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 #724


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

commit 3cbdba352474f90ed21a5824ccc4a1d090395fae
Author: tledkov-gridgain 
Date:   2016-05-10T08:47:22Z

hotfix the test that depends on IGNITE-3099 Race condition on the order of 
events

commit 8ee40a8e8d11f7a68e56c003a3c98d213253fb22
Author: tledkov-gridgain 
Date:   2016-05-10T08:48:21Z

increase timeout and check the property settings

commit 9db4ae5d0517664f76bdc109684a363a482f7d1d
Author: tledkov-gridgain 
Date:   2016-05-10T11:43:12Z

Change the sequence of tests to  properly set up 
IGNITE_MARSHAL_BUFFERS_RECHECK property for test IGNITE_MARSHAL_BUFFERS_RECHECK

commit eb33bedc0e15412f02e164c01697e5dd0ce046f3
Author: tledkov-gridgain 
Date:   2016-05-10T14:59:35Z

Fix  test GridUnsafeDataOutputArraySizingSelfTest: add non-static field 
'checkFreq' to the  GridUnsafeDataOutput

commit f51f7ec4470feb4d4ab85445010a14c6198de319
Author: tledkov-gridgain 
Date:   2016-05-11T07:31:08Z

remove debug print

commit cff5a190c40c28982ac3197d2d6aef957619f7c1
Author: tledkov-gridgain 
Date:   2016-05-11T09:21:51Z

investigate TC behavior

commit c3fe718bc1f553bfa607da711bc232ee8552e2b5
Author: tledkov-gridgain 
Date:   2016-05-11T09:54:25Z

revert: investigate TC behavior

commit d1edd404d19de479c0565d980a3d932ff383b9ef
Author: tledkov-gridgain 
Date:   2016-05-16T13:34:25Z

IgniteSourceTask stabilization

commit 0e6d4f97b5cda51639019e906b4e153f9c7d834b
Author: tledkov-gridgain 
Date:   2016-05-17T08:42:49Z

add debug print




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

2016-05-17 Thread Pavel Tupitsyn 
Hi,

Please note that documentation tickets do not hold the release (IGNITE-3101
and subtasks).
Other than that, in .NET, recently emerged 'IGNITE-3139 UTF surrogates' is
expected to be merged today.

Pavel.


On Tue, May 17, 2016 at 10:20 AM, Semyon Boikov 
wrote:

> In 1.6 we implemented 'late affinity assignment' mode (see
> https://issues.apache.org/jira/browse/IGNITE-324 and
> IgniteConfiguration.isLateAffinityAssignment)
>
> On Mon, May 16, 2016 at 7:03 PM, Alexey Kuznetsov  >
> wrote:
>
> > https://issues.apache.org/jira/browse/IGNITE-2832
> > "CacheJdbcPojoStoreFactory.dataSource property should be replaced with
> > Factory"
> > Reviewed by Semen and merged into ignite-1.6
> >
> >
> > On Mon, May 16, 2016 at 10:56 PM, Igor Sapego 
> > wrote:
> >
> > > Hi, here is a list of major C++ features included in 1.6:
> > >
> > > * ODBC driver for Ignite (IGNITE-1786)
> > > * Transactions API for CPP client (IGNITE-2805)
> > > * Simplified Autotools build process (IGNITE-2823)
> > > * Date and Timestamp types implementation (IGNITE-)
> > >
> > > Best Regards,
> > > Igor
> > >
> > > On Fri, May 13, 2016 at 4:10 PM, Artem Shutak 
> > > wrote:
> > >
> > > > I've finished with IGNITE-2959 Ignite JTA and WebSphere Application
> > > Server
> > > > 8.5.5  and has
> been
> > > > merged to 1.6.
> > > >
> > > > Also, I'm going to finish the following issues before 1.6 relase
> (they
> > > all
> > > > almost done/under review/waiting for TC):
> > > > [1] IGNITE-3056 Service implementation class is required even if it's
> > not
> > > > expected to be deployed on current node
> > > > 
> > > > [2] IGNITE-2921 ScanQueries over local partitions are not optimal
> > > > 
> > > > [3] IGNITE-2899 BinaryObject is deserialized before getting passed to
> > > > CacheInterceptor 
> > > >
> > > > Thanks,
> > > > -- Artem --
> > > >
> > > > On Fri, May 13, 2016 at 5:26 AM, Dmitriy Setrakyan <
> > > dsetrak...@apache.org>
> > > > wrote:
> > > >
> > > > > On Thu, May 12, 2016 at 9:08 AM, Alexey Kuznetsov <
> > > > akuznet...@gridgain.com
> > > > > >
> > > > > 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 <
> > isap...@gridgain.com
> > > >
> > > > > > 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 <
> > > > > ptupit...@gridgain.com
> > > > > > >
> > > > > > >> wrote:
> > > > > > >>
> > > > > > >> > And one more .NET ticket: IGNITE-3118 .NET:
> > > > > > >> > CacheConfiguration.EvictionPolicy
> > > > > > >> >
> > > > > > >> > On Thu, May 12, 2016 at 12:20 PM, Denis Magda <
> > > > dma...@gridgain.com>
> > > > > > >> 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 <
> > > > yzhda...@apache.org
> > > > > >
> > > > > > >> > wrote:
> > > > > > >> > > >
> > > > > > >> > > > Guys,
> > > > > > >> > > >
> > > > > > >> > > > I moved most of the tickets to 1.7 version.
> > > > > > >> >

[jira] [Created] (IGNITE-3147) Add missing properties to configuration (CollisionSpi and FailoverSpi)

2016-05-17 Thread Vasiliy Sisko (JIRA) 
Vasiliy Sisko created IGNITE-3147:
-

 Summary: Add missing properties to configuration (CollisionSpi and 
FailoverSpi)
 Key: IGNITE-3147
 URL: https://issues.apache.org/jira/browse/IGNITE-3147
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Affects Versions: 1.7
Reporter: Vasiliy Sisko
Assignee: Vasiliy Sisko
 Fix For: 1.7






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

Re: Ignite 1.6 release timelines

2016-05-17 Thread Semyon Boikov 
In 1.6 we implemented 'late affinity assignment' mode (see
https://issues.apache.org/jira/browse/IGNITE-324 and
IgniteConfiguration.isLateAffinityAssignment)

On Mon, May 16, 2016 at 7:03 PM, Alexey Kuznetsov 
wrote:

> https://issues.apache.org/jira/browse/IGNITE-2832
> "CacheJdbcPojoStoreFactory.dataSource property should be replaced with
> Factory"
> Reviewed by Semen and merged into ignite-1.6
>
>
> On Mon, May 16, 2016 at 10:56 PM, Igor Sapego 
> wrote:
>
> > Hi, here is a list of major C++ features included in 1.6:
> >
> > * ODBC driver for Ignite (IGNITE-1786)
> > * Transactions API for CPP client (IGNITE-2805)
> > * Simplified Autotools build process (IGNITE-2823)
> > * Date and Timestamp types implementation (IGNITE-)
> >
> > Best Regards,
> > Igor
> >
> > On Fri, May 13, 2016 at 4:10 PM, Artem Shutak 
> > wrote:
> >
> > > I've finished with IGNITE-2959 Ignite JTA and WebSphere Application
> > Server
> > > 8.5.5  and has been
> > > merged to 1.6.
> > >
> > > Also, I'm going to finish the following issues before 1.6 relase (they
> > all
> > > almost done/under review/waiting for TC):
> > > [1] IGNITE-3056 Service implementation class is required even if it's
> not
> > > expected to be deployed on current node
> > > 
> > > [2] IGNITE-2921 ScanQueries over local partitions are not optimal
> > > 
> > > [3] IGNITE-2899 BinaryObject is deserialized before getting passed to
> > > CacheInterceptor 
> > >
> > > Thanks,
> > > -- Artem --
> > >
> > > On Fri, May 13, 2016 at 5:26 AM, Dmitriy Setrakyan <
> > dsetrak...@apache.org>
> > > wrote:
> > >
> > > > On Thu, May 12, 2016 at 9:08 AM, Alexey Kuznetsov <
> > > akuznet...@gridgain.com
> > > > >
> > > > 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 <
> isap...@gridgain.com
> > >
> > > > > 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 <
> > > > ptupit...@gridgain.com
> > > > > >
> > > > > >> wrote:
> > > > > >>
> > > > > >> > And one more .NET ticket: IGNITE-3118 .NET:
> > > > > >> > CacheConfiguration.EvictionPolicy
> > > > > >> >
> > > > > >> > On Thu, May 12, 2016 at 12:20 PM, Denis Magda <
> > > dma...@gridgain.com>
> > > > > >> 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 <
> > > yzhda...@apache.org
> > > > >
> > > > > >> > 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

Multiple failover SPI

2016-05-17 Thread Vasiliy Sisko 
Hello Igniters.


I noticed that a grid configuration contain an array of failover SPIs, but
using of several failover SPIs is not described in a documentation.


Can anyone provide an example how to configure several falover SPI in one
grid?

-- 
Vasiliy Sisko
GridGain Systems
www.gridgain.com