Release branch v1.4 is created.

2015-09-02 Thread Vladimir Ozerov
Igniters, I created "ignite-1.4" branch from which the nearest release will be created.

Re: SVN changes

2015-09-02 Thread Dmitriy Setrakyan
On Tue, Sep 1, 2015 at 8:01 PM, Branko Čibej wrote: > On 02.09.2015 03:26, Dmitriy Setrakyan wrote: > > Brane, > > > > Since recently I am constantly asked to confirm an SVN certificate before > > updating or committing. This is really hurting my productivity :) > > Yeah,

Documenting Cache Expirations

2015-09-02 Thread Dmitriy Setrakyan
Igniters, I just noticed that Cache Expirations are not documented (probably because they are part of the JCache spec). Nevertheless, we have documentation for Eviction Policies [1], and I think that not having time-based expiration policies (ExpiryPolicy) there creates an impression that we

IGNITE-1195

2015-09-02 Thread Sergey Kozlov
Hi Igniters I suppose that issue below won't be fixed in nearest release 1.4. IGNITE-1195 Released Ignite version 1.3.0 does not build with -Dhadoop.version=2.6.0 Thus I think we need to update DEVNOTES.txt and add workaround for building

Queries failures on CI

2015-09-02 Thread Alexey Goncharuk
Folks, Did we make any changes to Indexing lately? I see that queries suite is failing in 1.4/master branch with the following assertion. If this is a known issue, can we at least properly mute the test so that it does not overtime? Test is

Re: Portable objects

2015-09-02 Thread Denis Magda
Val, Yes, the portable API and its implementation is already a part of both master and 1.4 branches. -- Denis On 9/2/2015 11:54 PM, Valentin Kulichenko wrote: Igniters, Are portable objects already migrated and will be released as a part of 1.4 (I see that APIs and configuration changes

Re: IGNITE-1195

2015-09-02 Thread Sergey Kozlov
It's not for 2.6.0 only. Same issue are for 2.5.2 and 2.7.1 On Wed, Sep 2, 2015 at 10:28 PM, Dmitriy Setrakyan wrote: > Is there any reason why support for the Hadoop 2.6 version is not going to > work? Can someone describe what needs to be done for us to fix this? > > On

Portable objects

2015-09-02 Thread Valentin Kulichenko
Igniters, Are portable objects already migrated and will be released as a part of 1.4 (I see that APIs and configuration changes are already in master)? I just thought it's a pretty big change and we were going to include it only in 1.5, correct me if I'm wrong. -Val

Re: IGNITE-1195

2015-09-02 Thread Dmitriy Setrakyan
On Wed, Sep 2, 2015 at 12:31 PM, Sergey Kozlov wrote: > It's not for 2.6.0 only. Same issue are for 2.5.2 and 2.7.1 > I think the same question stands - what is the main challenge here? > > On Wed, Sep 2, 2015 at 10:28 PM, Dmitriy Setrakyan >

Re: SVN changes

2015-09-02 Thread Dmitriy Setrakyan
On Wed, Sep 2, 2015 at 2:53 AM, Branko Čibej wrote: > > Also, any info about the platform you're using, and what kind of > authentication store you're using (KWallet? Gnome Keyring? OSX > Keychain?) would be useful here. > I am running on Mac. To my knowledge I am not using any

Re: Coding style changed!

2015-09-02 Thread Anton Vinogradov
Because we should have no mistakes at Ignite Java. Checking that build logs contains no "Javadoc Warnings" helps to guarantee that. On Wed, Sep 2, 2015 at 2:02 PM, Sergi Vladykin wrote: > I think these warnings are valid, since we are really using proprietary > APIs

Re: Coding style changed!

2015-09-02 Thread Sergi Vladykin
Can we ignore this this type of warning in JavaDoc checker? I don't like the idea of having some special imports because of that. Sergi 2015-09-02 14:32 GMT+03:00 Anton Vinogradov : > .. I mean at Ignite Javadoc > > On Wed, Sep 2, 2015 at 2:31 PM, Anton Vinogradov

[GitHub] ignite pull request: ignite-1351: move portable API examples

2015-09-02 Thread dmagda
GitHub user dmagda opened a pull request: https://github.com/apache/ignite/pull/57 ignite-1351: move portable API examples Refer to https://issues.apache.org/jira/browse/IGNITE-1351 for more info You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request: IGNITE-1354 Platform: AFTER_GRID_STOP lifecyc...

2015-09-02 Thread ptupitsyn
GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/58 IGNITE-1354 Platform: AFTER_GRID_STOP lifecycle events do not work Filter AfterStop events on Java side. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request: IGNITE-1354 Platform: AFTER_GRID_STOP lifecyc...

2015-09-02 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/58 --- 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

[jira] [Created] (IGNITE-1355) Potential NPE in CacheAffinityProxy

2015-09-02 Thread Semen Boikov (JIRA)
Semen Boikov created IGNITE-1355: Summary: Potential NPE in CacheAffinityProxy Key: IGNITE-1355 URL: https://issues.apache.org/jira/browse/IGNITE-1355 Project: Ignite Issue Type: Bug

Re: Coding style changed!

2015-09-02 Thread Sergi Vladykin
I think these warnings are valid, since we are really using proprietary APIs like Unsafe. Why should we hide them? Sergi 2015-09-01 16:29 GMT+03:00 Anton Vinogradov : > Hello, > > Since codestyle was changed javadoc starts to warn about using of > proprietary API. > >

[GitHub] ignite pull request: ignite-1353: fixed type resolving conflicts i...

2015-09-02 Thread dmagda
GitHub user dmagda opened a pull request: https://github.com/apache/ignite/pull/59 ignite-1353: fixed type resolving conflicts in portable context Refer to https://issues.apache.org/jira/browse/IGNITE-1353 for more details. You can merge this pull request into a Git repository by

[jira] [Created] (IGNITE-1360) Extend platform processor lifecycle.

2015-09-02 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-1360: --- Summary: Extend platform processor lifecycle. Key: IGNITE-1360 URL: https://issues.apache.org/jira/browse/IGNITE-1360 Project: Ignite Issue Type:

Re: Coding style changed!

2015-09-02 Thread Anton Vinogradov
Problem fixed using top secret -XDenableSunApiLintControl param. Thanks for stopping me :) On Wed, Sep 2, 2015 at 3:30 PM, Anton Vinogradov wrote: > I did not found how to do that, will try to search again. > > > On Wed, Sep 2, 2015 at 3:01 PM, Sergi Vladykin

[jira] [Created] (IGNITE-1356) Move platforms Java public API to Ignite.

2015-09-02 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-1356: --- Summary: Move platforms Java public API to Ignite. Key: IGNITE-1356 URL: https://issues.apache.org/jira/browse/IGNITE-1356 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-1352) Platforms: move cpp and .Net examples to Ignite

2015-09-02 Thread Denis Magda (JIRA)
Denis Magda created IGNITE-1352: --- Summary: Platforms: move cpp and .Net examples to Ignite Key: IGNITE-1352 URL: https://issues.apache.org/jira/browse/IGNITE-1352 Project: Ignite Issue Type:

Re: SVN changes

2015-09-02 Thread Branko Čibej
On 02.09.2015 09:27, Dmitriy Setrakyan wrote: > On Tue, Sep 1, 2015 at 8:01 PM, Branko Čibej wrote: > >> On 02.09.2015 03:26, Dmitriy Setrakyan wrote: >>> Brane, >>> >>> Since recently I am constantly asked to confirm an SVN certificate before >>> updating or committing. This is

[jira] [Created] (IGNITE-1353) PortableContext.typeId() incorrectly resolves type ID for predefined system types.

2015-09-02 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-1353: --- Summary: PortableContext.typeId() incorrectly resolves type ID for predefined system types. Key: IGNITE-1353 URL: https://issues.apache.org/jira/browse/IGNITE-1353

Re: SVN changes

2015-09-02 Thread Branko Čibej
On 02.09.2015 11:29, Branko Čibej wrote: > On 02.09.2015 09:27, Dmitriy Setrakyan wrote: >> On Tue, Sep 1, 2015 at 8:01 PM, Branko Čibej wrote: >> >>> On 02.09.2015 03:26, Dmitriy Setrakyan wrote: Brane, Since recently I am constantly asked to confirm an SVN

Re: Ignite 1.4

2015-09-02 Thread Yakov Zhdanov
Yes, we will be moving almost all the issues to further versions. Branch has already been created. --Yakov 2015-09-01 22:14 GMT+03:00 Branko Čibej : > On 01.09.2015 20:46, Konstantin Boudnik wrote: > > On Tue, Sep 01, 2015 at 08:45PM, Sergey Kozlov wrote: > >> FYI: We've at

[jira] [Created] (IGNITE-1359) Inject platform processor into Ignite lifecycle.

2015-09-02 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-1359: --- Summary: Inject platform processor into Ignite lifecycle. Key: IGNITE-1359 URL: https://issues.apache.org/jira/browse/IGNITE-1359 Project: Ignite

[jira] [Created] (IGNITE-1357) Move Java bootstrap logic to Ignite.

2015-09-02 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-1357: --- Summary: Move Java bootstrap logic to Ignite. Key: IGNITE-1357 URL: https://issues.apache.org/jira/browse/IGNITE-1357 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-1358) PortableMarshaller: 'userType' flag is not written for objects of some types

2015-09-02 Thread Denis Magda (JIRA)
Denis Magda created IGNITE-1358: --- Summary: PortableMarshaller: 'userType' flag is not written for objects of some types Key: IGNITE-1358 URL: https://issues.apache.org/jira/browse/IGNITE-1358 Project:

Re: Coding style changed!

2015-09-02 Thread Anton Vinogradov
I did not found how to do that, will try to search again. On Wed, Sep 2, 2015 at 3:01 PM, Sergi Vladykin wrote: > Can we ignore this this type of warning in JavaDoc checker? > I don't like the idea of having some special imports because of that. > > Sergi > >